Ranked roundup · Figma
Best MCP Server for Figma
There is exactly one official MCP server for Figma, and it is the one to try first: Figma's own Dev Mode MCP server, reachable as a hosted remote endpoint at mcp.figma.com or as a local server inside the desktop app. It is still labeled beta, and Figma's docs say write-to-canvas is free only "during the beta period," so the community options still matter. The strongest of those is GLips's Framelink Figma-Context-MCP — 15,751 GitHub stars, MIT license, last pushed August 2026 — which trades the official server's breadth for a simple token-based, read-only design-context pipe that works with any MCP client. Grab's Talk-to-Figma server adds plugin-based write access, and Composio offers a managed hosted path with OAuth handled for you. We ranked all four on verifiable criteria: official status, maintenance recency, adoption, auth model, and documented capability coverage. No one paid for placement, and we do not invent benchmark scores.
Facts checked September 1, 2026 · ranked on verifiable criteria · placement is never for sale
Founder, Automation Squad ·
The ranking
- Official · Figma
Teams on supported clients who want the sanctioned design-to-code pipeline plus write-back to the canvas, with OAuth instead of hand-managed tokens.
Generate code from selected frames; extract variables, components, and layout data; Code Connect integration for design-system consistency; FigJam/Make file access; write native Figma content to canvas (frames, components, variables, auto layout) — remote server only.
Hosted remote endpoint (https://mcp.figma.com/mcp) or local server inside the Figma desktop app · Figma OAuth sign-in for the remote server; the desktop server runs under your logged-in Figma session
- Still in beta. Figma's help docs state write-to-canvas is free only during the beta period and will eventually become a paid feature.
- The remote server only works with clients in Figma's MCP catalog (Claude Code, Cursor, VS Code, Codex, Xcode 27 beta at time of checking); other client developers must join a waitlist.
- The desktop (local) server requires a Dev or Full seat on a paid plan; only the remote server is available on all seats and plans.
- Closed source — no public repo, so no stars, license, or commit history to audit.
- Figma for Government accounts are limited to the desktop server.
- Community
Developers on any MCP client who want the fastest path from a Figma URL to accurately generated code, with no seat or plan requirements beyond API access.
Read-only design context: paste a Figma file/frame/group URL and it fetches the design via the Figma REST API, then simplifies and compacts the layout and styling metadata specifically for code-generating agents.
Self-hosted, runs locally via npx (figma-developer-mcp on npm) · Figma personal access token, passed as an environment variable or CLI flag · MIT · 15,751★
- Unofficial community project — not affiliated with Figma.
- Read-only: it cannot create or modify anything on the canvas.
- Auth is a broad, long-lived personal access token that you create and manage yourself, sitting in an env var or config file in plain text.
- Community
Programmatic design manipulation — having an agent make bulk or scripted edits to a live Figma file rather than just reading it.
Two-way: reads designs and modifies them programmatically through its Figma plugin, per the project's own description — the main community option for agent-driven canvas editing.
Self-hosted: local MCP server plus a local WebSocket relay, bridged to a Figma plugin · No API token — a companion Figma plugin acts under your logged-in Figma session, connected to the agent over a local WebSocket channel · MIT · 6,987★
- Unofficial community project — not affiliated with Figma (maintained under ride-hailing company Grab's open-source org).
- Most setup friction of the group: a WebSocket relay and the Figma plugin must both be running before your agent can do anything.
- Less than half Framelink's adoption (6,987 stars vs 15,751).
- Originally published as sonnylazuardi/cursor-talk-to-figma-mcp; the repo moved to Grab's org, so older tutorials link to a redirecting address.
- Community
No-code and hosted setups automating Figma collaboration workflows — comments, webhooks, tokens — alongside many other apps, without running or updating anything yourself.
52 hosted Figma tools per Composio's docs: comments and replies, reactions, webhooks, variables management, and design-token extraction/conversion (including Tailwind config generation).
Fully managed — hosted MCP endpoint run by Composio, nothing to install locally · Managed OAuth with automatic token refresh and per-user credentials, handled by Composio
- Not a Figma product — a third party holds your OAuth grant, so you are trusting Composio's hosting and its security claims (SOC 2 Type 2, per Composio).
- Tools operate at the Figma REST API level (comments, webhooks, variables); this is not a design-to-code context server like the official server or Framelink.
- Free to start, but production usage moves onto paid tiers.
- Closed-source hosted service — no repo, stars, or commit history to verify independently.
Figma MCP servers compared
| Server | Maintained by | Runs | Auth | License |
|---|---|---|---|---|
| Figma Dev Mode MCP server (official) | Figma | Hosted remote endpoint (https://mcp.figma.com/mcp) or local server inside the Figma desktop app | Figma OAuth sign-in for the remote server; the desktop server runs under your logged-in Figma session | — |
| Framelink Figma-Context-MCP (GLips) | Community | Self-hosted, runs locally via npx (figma-developer-mcp on npm) | Figma personal access token, passed as an environment variable or CLI flag | MIT |
| Talk to Figma MCP (Grab) | Community | Self-hosted: local MCP server plus a local WebSocket relay, bridged to a Figma plugin | No API token — a companion Figma plugin acts under your logged-in Figma session, connected to the agent over a local WebSocket channel | MIT |
| Composio Figma MCP (managed) | Community | Fully managed — hosted MCP endpoint run by Composio, nothing to install locally | Managed OAuth with automatic token refresh and per-user credentials, handled by Composio | — |
How to choose
Pick Figma's official Dev Mode server if your client is in Figma's supported catalog (Claude Code, Cursor, VS Code, Codex, Xcode 27 beta) and you want OAuth sign-in plus write-to-canvas — accepting that it is beta. Pick Framelink (GLips) if you use a client outside that catalog, want the simplest setup (npx plus a personal access token), or only need read-only design context for code generation. Pick Grab's Talk-to-Figma if you need programmatic canvas edits and don't mind running a WebSocket relay and a Figma plugin. Pick Composio if you want hosted infrastructure and managed OAuth for REST-level automation — comments, webhooks, variables — rather than design-to-code.
How this ranking works
Every server here is real and was checked against its repository or vendor documentation on the date above — stars and licenses come from the GitHub API, not from memory. Order reflects verifiable criteria only: official support, maintenance recency, adoption, auth model, and documented capability coverage. We do not run paid placements, and we list every caveat we find, including the unflattering ones.
Common questions
- Is there an official Figma MCP server?
- Yes. Figma ships its own Dev Mode MCP server, available as a hosted remote endpoint (https://mcp.figma.com/mcp) on all seats and plans, or as a local server in the desktop app for Dev and Full seats on paid plans. It is still in beta, and write-to-canvas is free only while the beta lasts, per Figma's help docs.
- What does setup and auth actually look like for a Figma MCP server?
- The official remote server authenticates through Figma's OAuth flow — you sign in and never handle a token. Community servers like Framelink instead need a Figma personal access token you create yourself and pass as an environment variable, and Grab's server additionally requires a local WebSocket relay plus a Figma plugin running under your logged-in session. Composio handles OAuth for you on its hosted infrastructure.
- Can an MCP server edit my Figma designs, or only read them?
- Two of the four can write. Figma's official remote server writes native frames, components, and variables to the canvas, and Grab's Talk-to-Figma modifies designs through its plugin. Framelink is read-only by design, and Composio's tools work at the REST API level — comments, webhooks, variables — rather than drawing on the canvas.
- Which MCP clients work with the official Figma server?
- Figma restricts the remote server to clients in its MCP catalog — Claude Code, Cursor, VS Code, Codex, and Xcode 27 beta at the time of checking — and developers of other clients must join a waitlist. Community servers like Framelink have no such restriction; any MCP-capable client works.
MCP servers we build
Automation Squad publishes its own open-source MCP servers and agent skills, documented with the same rules this ranking uses.