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 | Figma MCPMCP100 Selected | Firecrawl MCPMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Figma · Publisher source ↗ | First-party MCP Firecrawl · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Aug 12, 2026 Package: Aug 12, 2026 |
| Popularity evidence | ||
| GitHub stars | Not documented | 7,234 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| 30-day package downloads | No reliable download data | 412,488 30-day package downloads · checked 2026-08-14T18:46:26.000Z |
| External adoption evidence | Not documented |
|
| 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. | Cloud and local-package configurations use FIRECRAWL_API_KEY. Official docs also show hosted MCP URLs containing the key; environment-variable or protected input handling is safer than embedding the key in a URL. |
| 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. | MCP calls consume the account's standard Firecrawl API credits and rate limits. Search, crawl, batch, and agent operations can consume more resources than single-page scraping; current plan pricing applies. |
| 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. | The MCP can initiate outbound requests to user- or model-selected URLs and invoke Firecrawl scrape, search, crawl, map, extraction, batch, and research capabilities according to enabled tools and account limits. |
| 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. | URLs, queries, extraction schemas, and retrieved page content are processed by the configured Firecrawl service. Cloud mode sends them to Firecrawl; self-hosted mode follows the operator's deployment and any configured model/provider dependencies. |
| Limitations | ||
| Tradeoffs |
|
|
| 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. | Main risks are prompt injection from untrusted pages, collection-policy violations, sensitive URL/query disclosure, API-key leakage, and agent-driven credit spend. Use URL allow-lists, low limits, human approval, and a dedicated low-budget key. |
| Evidence date | ||
| Editorial review | 2026-07-24 | 2026-07-24 |
| 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 →