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.
| Evidence field | Framelink MCP for FigmaMCP100 Selected | Playwright MCPMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | Community implementation io.github.GLips · Publisher source ↗ | First-party MCP Microsoft · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 7, 2026 Package: Jun 18, 2026 | Repo: Aug 12, 2026 Package: Jul 9, 2026 |
| Popularity evidence | ||
| GitHub stars | 15,658 GitHub stars · checked 2026-08-14T18:46:26.000Z | 36,125 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| 30-day package downloads | 350,316 30-day package downloads · checked 2026-08-14T18:46:26.000Z | 6,369,865 30-day package downloads · checked 2026-07-29T17:30:00.000Z |
| External adoption evidence |
|
|
| Client coverage | ||
| Client coverage details | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio | 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 | 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. | The server itself does not require a service account for local stdio use, but websites opened in the controlled browser may use cookies or other authenticated browser state. |
| Cost | The MIT-licensed server lists no MCP fee. Figma plan and API limits, client, and model costs are separate. | The first-party open-source package lists no MCP server usage fee. Normal internet, hosted-client, proxy, or third-party website costs can still apply. |
| Permissions | 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. | The exposed tools can navigate pages, interact with elements, enter text, upload files, inspect network activity, and optionally use additional browser capabilities. |
| Data handling | 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. | Page text, accessibility snapshots, console output, network details, uploaded paths, and browser state may be returned to the connected MCP client. Isolated mode keeps the temporary profile in memory; persistent mode stores browser state on disk. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | 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. | Playwright MCP is not a security boundary. Prefer an isolated browser profile, non-sensitive test accounts, narrow destinations, minimal optional permissions, and client-side approval controls. |
| Evidence date | ||
| Editorial review | 2026-08-11 | 2026-07-24 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →