Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Figma MCPFramelink MCP for Figma

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Azure MCP ServerMCP100 SelectedChrome DevTools MCPMCP100 SelectedContext7 MCPMCP100 SelectedFirecrawl MCPMCP100 SelectedGrafana Cloud MCPMCP100 SelectedGoogle MCP Toolbox for DatabasesMCP100 Selected

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Figma MCPMCP100 Selected	Framelink MCP for FigmaMCP100 Selected
Task fit
Best for	Turning selected Figma frames into implementation context Design-system teams using variables, components, and Code Connect Human-supervised creation or modification of native Figma content	Providing coding agents with Figma node structure, styles, variables, and design assets needed for implementation
Not ideal for	MCP clients outside Figma's supported catalog Teams expecting one-click pixel-perfect production code Headless automation that cannot complete user OAuth	Replacing designer review or guaranteeing pixel-perfect production code from arbitrary files
Avoid when	Proprietary design content cannot be exposed to the selected AI client or model Canvas writes cannot be reviewed before execution A stable long-term zero-cost commitment is required	The connected Figma account exposes confidential files that should not be sent to the AI client
Provenance
Provenance details	First-party MCP Figma · Publisher source ↗	Community implementation io.github.GLips · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Aug 7, 2026 Package: Jun 18, 2026
Popularity evidence
GitHub stars	Not documented	15,658 GitHub stars · checked 2026-08-14T18:46:26.000Z
30-day package downloads	No reliable download data	350,316 30-day package downloads · checked 2026-08-14T18:46:26.000Z
External adoption evidence	Not documented	github: repository stars: 15,658Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details	Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	The recommended remote server at https://mcp.figma.com/mcp uses user OAuth. Desktop mode relies on the signed-in Figma desktop application and its local endpoint.	Uses a personal access token through FIGMA_API_KEY or X-Figma-Token, or an OAuth bearer token. HTTP also supports per-request token headers.
Cost	Figma documents the MCP feature as free during its current beta and says it is expected to become usage-based paid. Underlying Figma plans and plan-specific features may also apply.	The MIT-licensed server lists no MCP fee. Figma plan and API limits, client, and model costs are separate.
Permissions	OAuth grants access to authorized Figma resources. Available tools can read design context and, in supported workflows, create or modify canvas content. Desktop mode can also serve or download image and SVG assets.	Reads Figma file and node data through the Figma API and downloads PNG, SVG, or GIF assets into a configured local image directory; no Figma write capability is documented.
Data handling	The remote service retrieves design nodes, components, variables, layouts, and potentially Make or Code Connect resources and returns them to the MCP client. Desktop mode can write downloaded assets into the local project.	Figma metadata and API responses are returned to the MCP client; raw tools write figma-raw.json locally and image tools save assets locally. Telemetry sends server, platform, session, and event metadata by default; retention is not documented.
Limitations
Tradeoffs	The hosted endpoint is easiest to connect and has the broadest feature set, but authorized design context passes through Figma and the connected AI workflow. The desktop server is locally reachable through the Figma app, but it is intended for narrower organization and enterprise use cases. Code Connect can improve component reuse but requires additional design-system setup.	Structured design context reduces screenshot guesswork, but output quality still depends on file organization and granting access to Figma data.
Risk context	Private designs can be disclosed through tool results, and write-enabled tools can change shared design files. Restrict accessible files, review OAuth consent, require confirmation for writes, and inspect downloaded assets before committing them.	Private design data and assets can reach the MCP client or model and local raw logs; telemetry adds metadata transmission. Protect tokens, restrict the image directory, and review downloaded and raw files.
Evidence date
Editorial review	2026-07-24	2026-08-11
Candidate evidence	2026-07-29T20:58:26.000Z	2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →