Head to head · Design files · October 2026 research run
Figma API + MCP vs Framer Server API
Figma API + MCP has a score of 66.1 (B) against Framer Server API's 52.8 (D). Both do design files. The largest gap is security & auth, 24 points.
Figma API + MCPFigma · HTTP API
B66.1/100#164 of 452
Framer Server APIFramer · HTTP API
D52.8/100#340 of 452
Which one, for what
Pick Figma API + MCP for
- reliability (+16)
- schema & documentation (+17)
- agent ergonomics (+13)
- security & auth (+24)
- payments & pricing (+5)
- maintenance & community (+7)
Pick Framer Server API for
No category where it leads by five points or more.
Score by category
| Category | Weight this run | Figma API + MCP | Framer Server API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 59 | 43 | Figma API + MCP +16 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 86 | 69 | Figma API + MCP +17 |
| Agent ergonomics | 13%16.2 | 60 | 47 | Figma API + MCP +13 |
| Security & auth | 14%17.5 | 74 | 50 | Figma API + MCP +24 |
| Payments & pricing | 10%12.5 | 30 | 25 | Figma API + MCP +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 84 | 77 | Figma API + MCP +7 |
| Transparency & trust | 7%8.8 | 75 | 77 | Framer Server API +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 66.1 · B | 52.8 · D |
Facts side by side
| Fact | Figma API + MCP | Framer Server API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Figma | Framer |
| Hosted endpoint | https://api.figma.com/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | proprietary | proprietary |
| Tools exposed | 35 | none |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.figma.mcp/mcp | not listed |
| Last release | 2026-09-24 | 2026-09-24 |
| Popularity | 456k npm/wk | 336k npm/wk |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
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.
Framer Server API
Same surface as the Plugin API, so canvas nodes, components, code files and CMS are writable. No REST endpoints and no official MCP server. You need Node 22 and the framer-api package.
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
Framer Server API
connect(projectUrl, process.env.FRAMER_API_KEY)then call Plugin API methods, and close the connection when done- Publish creates a preview deployment. Promote it with
deploy()only after checking it - Keep batches small and idempotent, since a dropped connection can stop a run halfway
- For interactive work from a coding agent,
npx @framer/agent setupis the supported route and keeps changes on a branch - Check the changelog before upgrading. v5.0.0 changed CMS array fields and requires stable
idvalues
Other comparisons with Figma API + MCP or Framer Server API
Machine-readable
/api/v1/tools/figma-mcp.json·/api/v1/tools/framer.json- This page as Markdown,
/compare/figma-mcp-vs-framer.md