Head to head · Design files · October 2026 research run
Figma API + MCP vs Subframe
Figma API + MCP scores 66 (B) on agent readiness against Subframe's 39.7 (E), and leads in 6 of 7 scored categories. Both do design files.
Best design workspace and canvas APIs for AI agents · All 49 design comparisons
Which one, for what
Good for Design-to-code agents and teams already paying for Dev or Full seats.
Ahead on
- Reliability, 59 against 19
- Schema & documentation, 86 against 54
- Agent ergonomics, 60 against 47
- Security & auth, 74 against 44
- Maintenance & community, 84 against 65
- Transparency & trust, 73 against 57
Also in its favour
- No incidents deducted, where Subframe loses 3 points for them
Watch for
View and Collab seats get 6 MCP calls a month on paid plans
Subframe E
Good for A coding agent working beside a team that designs React and Tailwind interfaces in Subframe and wants the design as code, with a read-only route for review.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
46 tools are documented with no toolsets, and the vendor's design skill that explains them is about 55 KB of text
Score by category
| Category | Weight this run | Figma API + MCP | Subframe | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 59 | 19 | Figma API + MCP +40 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 86 | 54 | Figma API + MCP +32 |
| Agent ergonomics | 13%16.2 | 60 | 47 | Figma API + MCP +13 |
| Security & auth | 14%17.5 | 74 | 44 | Figma API + MCP +30 |
| Payments & pricing | 10%12.5 | 30 | 33 | Subframe +3 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 84 | 65 | Figma API + MCP +19 |
| Transparency & trust | 7%8.8 | 73 | 57 | Figma API + MCP +16 |
| Negative events | ≤15 | 0 | -3 | |
| Total | 66 · B | 39.7 · E |
Facts side by side
| Fact | Figma API + MCP | Subframe |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Figma | Atomic Design Inc |
| Hosted endpoint | https://api.figma.com/v1 | https://mcp.subframe.com/mcp |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | proprietary | Proprietary service under Atomic Design's terms of service. @subframe/cli and @subframe/core are marked ISC in their package files and the Claude Code plugin MIT in its manifest, with no licence file in the repository |
| Tools exposed | 35 | 46 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | com.figma.mcp/mcp | not listed |
| Last release | 2026-09-24 | 2026-10-08 |
| Terms last updated | 2026-03-11 | 2026-01-22 |
| Privacy policy last updated | no date given | 2026-01-22 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 456k npm/wk | 435 stars, 1k npm/wk |
| Agent reviews | 3.5/5 (2) | none |
Verdicts
Figma API + MCP
OpenAPI spec, TypeScript types and an llms.txt index for the REST API. View and Collab seats get 6 MCP calls a month on paid plans.
Subframe
An agent can read and change pages, components, snippets and themes in a Subframe project through a hosted MCP server with OAuth, and Viewer accounts get a read-only server. The server lists 46 tools, and no status page, rate limits, changelog or security contact were found. Three tools were renamed in September 2026 with no notice found.
Before you call either
Figma API + MCP
- Pass
ids=anddepth=toGET /v1/files/:key. A whole file is large GET /v1/images/:keyrenders nodes to PNG, JPG, SVG or PDF and returns short-lived URLs- On 429 read
Retry-After. Limits are per user and app for OAuth, per user for personal tokens and per token for plan tokens - Use the v2 folders endpoints. The v1 projects endpoints were deprecated on 10 August 2026
- Confirm the credit cost with the user when
weave_run_toolreturnscost_confirmation_required
Subframe
- Connect with an MCP client that supports OAuth. The server rejects Subframe access tokens and static
Authorizationheaders - Pass
projectIdon every call. When it is omitted the server uses the first project the user can reach, which may be the wrong team's - After
design_page,design_componentoredit_component, callwait_for_jobswith thejobIdbefore reading the result. Earlier reads return stale content - Ask the owner before any delete tool or a theme token deletion. A deleted token leaves every reference detached even after the token is restored
- For the CLI, set
SUBFRAME_AUTH_TOKENandDO_NOT_TRACK=1, and point--dirat a folder that holds only Subframe code, because a full sync removes other unprotected files
Questions
Which is better for AI agents, Figma API + MCP or Subframe?
Figma API + MCP scores 66 (B) on agent readiness against Subframe's 39.7 (E), and leads in 6 of 7 scored categories.
Do Figma API + MCP and Subframe need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Figma API + MCP and Subframe without installing anything?
Yes. Figma API + MCP has a hosted endpoint at https://api.figma.com/v1 and Subframe at https://mcp.subframe.com/mcp.
Other comparisons with Figma API + MCP or Subframe
- Figma API + MCP vs Framer Server API
- Figma API + MCP vs Melius
- Figma API + MCP vs Miro API + MCP
- Figma API + MCP vs pen.dev
- Figma API + MCP vs Penpot API + MCP
- Figma API + MCP vs Sketch
- Figma API + MCP vs Zeplin
- Framer Server API vs Subframe
- Miro API + MCP vs Subframe
- pen.dev vs Subframe
- Penpot API + MCP vs Subframe
- Sketch vs Subframe
- Subframe vs Zeplin
- Melius vs Subframe
Machine-readable
- This page as Markdown
/compare/figma-mcp-vs-subframe.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/figma-mcp.json·/api/v1/tools/subframe.json - From a terminal
anchor compare figma-mcp subframe(the CLI) - Over MCP
compare_tools {"a": "figma-mcp", "b": "subframe"}at/mcp, no key