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 MCPPlaywright MCP

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

Comparable alternatives

Azure MCP ServerMCP100 RecommendedChrome DevTools MCPMCP100 RecommendedContext7 MCPMCP100 RecommendedGrafana Cloud MCPMCP100 RecommendedGoogle MCP Toolbox for DatabasesMCP100 RecommendedGoogle Search Console MCP Server for SEOsMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Figma MCPMCP100 Recommended	Playwright MCPMCP100 Recommended
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	Inspecting and testing web interfaces through accessibility snapshots Reproducing browser journeys in a dedicated test profile
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	API-only testing that does not need a browser Unattended access to a personal browsing profile
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 workflow cannot permit an agent to navigate, type, click, upload files, or read page content You cannot isolate sensitive authenticated sessions from the agent-controlled browser
Provenance
Provenance details	First-party MCP Figma · Publisher source ↗	First-party MCP Microsoft · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Sep 18, 2026 Package: Sep 21, 2026
Popularity evidence
GitHub stars	Not documented	37,525 GitHub stars · checked 2026-09-24T04:14:16.452000Z
Package downloads / 30 days	No reliable download data	23,800,747 package downloads / 30 days · checked 2026-09-24T04:17:39.045000Z
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.	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	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 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	The connected user's Figma identity and existing file permissions govern access. The current remote MCP is not purely read-only: Write to Canvas can create or modify design content for users or seats with required edit authority, while read-only design-context workflows remain available without edit authority.	The exposed tools can navigate pages, interact with elements, enter text, upload files, inspect network activity, and optionally use additional browser capabilities.
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.	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	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.	A persistent profile is convenient but can retain cookies and authenticated state between sessions. Origin allow/block options reduce accidental access but the publisher explicitly says they are not a security boundary.
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.	Playwright MCP is not a security boundary. Secret replacement or masking is a convenience feature, 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-07-24	2026-07-24
Candidate evidence	2026-09-24T04:25:05.554391Z	2026-09-24T04:25:05.554391Z

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

Read the evidence method →