Head to head · Design files · October 2026 research run
Figma API + MCP vs Paper MCP
Figma API + MCP scores 64 (B) on agent readiness against Paper MCP's 38.1 (E), and leads in 6 of 7 scored categories. Paper MCP leads on payments & pricing. Both do design files.
Best design workspace and canvas APIs for AI agents · All 162 design comparisons
Which one, for what
Best for Design-to-code agents and teams already paying for Dev or Full seats.
Ahead on
- Reliability, 64 against 30
- Schema & documentation, 86 against 37
- Agent ergonomics, 60 against 39
- Security & auth, 71 against 31
- Maintenance & community, 84 against 65
- Transparency & trust, 67 against 56
Watch for
View and Collab seats get 20 MCP calls a month on every plan
Best for Design teams who want an agent to build and edit screens on a canvas that is HTML and CSS, and to turn frames into code.
Ahead on
- Payments & pricing, 30 against 15
Also in its favour
- Runs on your own machine
Watch for
No published tool schemas or tool list. The Claude extension manifest marks tools as generated by the app
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation Figma API + MCP +49
Figma API + MCP 86
Public OpenAPI spec in figma/rest-api-spec, with TypeScript types on npm (25). llms.txt at developers.figma.com (10). The MCP tools page explains each tool and splits read, write and Weave groups, but the server is closed, so we couldn't read its own tool definitions (13 of 20). Typed parameters with enums such as image format (png, jpg, svg, pdf) and depth limits (13 of 15). Reference examples throughout. We didn't read an error catalogue (10 of 15). A dated REST changelog with deprecation notices and v1 and v2 paths (15).
Paper MCP 37
The MCP tool definitions are generated by the app (tools_generated: true in the Claude extension manifest) and no page publishes their input schemas. The remote endpoint asks for OAuth before initialize, so no tool list was read. paper.design/openapi.json covers only two unauthenticated website endpoints and says the agent surface is the MCP server, not a REST API (0 of 25). llms.txt with a developer section (10). The MCP docs explain when to use the desktop server or the remote one, and say read tools are safe to always allow while write tools change the file, but the tool descriptions themselves were not readable (8 of 20). Tool names are known only from the ChatGPT plugin's review test cases (open_file, get_basic_info, get_screenshot, create_artboard, write_html, find_nodes, set_text_content, get_computed_styles and others), with no types (3 of 15). Example prompts and a troubleshooting section, with no list of error responses (6 of 15). A monthly dated build log, and plugin versions in the agent-plugins repository (10 of 15). 0+10+8+3+6+10 = 37.
Security & auth Figma API + MCP +40
Figma API + MCP 71
OAuth 2 with per-resource scopes such as file_content:read and file_comments:write (the 22 October Teams endpoints add teams:write, folders:write and team_members:write), scoped personal access tokens, and plan access tokens with resource allowlists and expiry of up to a year. The MCP server signs in with OAuth and only catalogue-listed clients can connect (30). Read-only scopes give least privilege on REST. The MCP server has no documented read-only mode, and canvas writes such as use_figma run without a confirmation step (13 of 20). File content, layer names and comments written by collaborators reach the model as they are, and we found no prompt-injection guidance (3 of 15). Activity logs and an AI usage API for Enterprise (12 of 15). Figma runs a bug bounty programme on HackerOne (hackerone.com/figma, "Figma - Bug Bounty Program"). www.figma.com's robots.txt disallows our crawler on every path, so the security page's certifications read on 1 October are struck and security.txt stays unread. Graded as meta-marketing-api's 13 (bounty route confirmed elsewhere, the vendor's own security pages unread) (13 of 20).
Paper MCP 31
The remote server answers 401 with an OAuth protected-resource pointer and signs in with the user's Paper account, and the ChatGPT plugin says the agent can reach only files that account can reach. No scopes or token lifetimes are documented. The local server needs no credential (20 of 30). No read-only mode. The docs rely on the agent client's permission prompts and say the Paper MCP 'can read and write, so make sure you're comfortable with the agent being able to manipulate this specific design file' (5 of 20). Files, comments and pasted or imported content written by others reach the model, and no prompt-injection guidance was found (3 of 15). The canvas shows agent presence and feedback while an agent works, with no audit log or per-call record documented (3 of 15). No security.txt (404), disclosure policy, bug bounty or certification found. SAML and SSO are on the Organizations plan (0 of 20). 20+5+3+3+0 = 31.
Reliability Figma API + MCP +34
Figma API + MCP 64
Statuspage at status.figma.com with history, read from its Atom feed (20). From 3 August to 1 November the feed posts four incidents. The 27 September "Service disruption" ("Figma Services are degraded or unavailable because of failures with AWS and other dependencies", 01:04 to 02:32 UTC) hit every service and reads as a major. The 26 August "Figma MCP Disruption" (10:14 to about 14:03 UTC) kept "some Codex and ChatGPT users" from seeing MCP tools, so it's partial and minor. The 13 October Figma agent and Make errors and the 30 October Sites publishing problem don't touch the REST API or the MCP server. The 27 July file-editing incident left the window. One major (10). Published limits for REST by tier, seat and plan, and for MCP by seat (Full and Dev up to 200 calls a day and 10 a minute on Professional, 15 on Organization, 600 a day and 20 a minute on Enterprise; View and Collab 20 a month on every plan) (15). REST 429s carry Retry-After, X-Figma-Plan-Tier and X-Figma-Rate-Limit-Type. No idempotency guidance for comment or variable writes (12 of 15). No SLA found on the developer pages (0). REST is GA, and writing to the canvas is still "free during the beta period" on the MCP introduction (7 of 10).
Paper MCP 30
Read with the local-software lines, because the main surface is the stdio server the Paper CLI runs on the owner's machine (paper mcp), with Paper Desktop installed from paper.design/downloads. The Claude extension manifest lists macOS, Windows and Linux, while llms.txt names a macOS download, and no runtime requirements are stated (15 of 20). The app and server are closed, so no public CI or test suite can be seen. The agent-plugins repository has a build workflow that validates plugin manifests only (0). No public issue tracker was found. Support is team@paper.design with a stated reply within 2 business days, plus Discord and Slack (5 of 25). The monthly build log is dated, and the move from the localhost HTTP endpoint to paper mcp kept the old endpoint working while a file is open, with migration steps (10 of 15). No version number is published for the desktop app, and the remote server is early access (0). The remote server and sign-in also depend on Paper's hosted service, which has no status page, and robots.txt disallows /status/. 15+0+5+10+0 = 30.
Agent ergonomics Figma API + MCP +21
Figma API + MCP 60
REST file reads can be cut down with ids and depth. The MCP server lists 41 tools (18 read, 14 write, 9 Weave; 35 on 1 October), with some remote-only and others desktop-only, and we found no toolsets or read-only subset (15 of 25). Cursor pagination on comments, versions and folders (16 of 20). REST errors carry a status and message (13 of 20). We couldn't confirm readOnlyHint or destructiveHint on the closed MCP server, and REST writes have no idempotency keys. weave_run_tool stops with cost_confirmation_required until the caller acknowledges the credit cost (8 of 20). TypeScript types for REST and the Code Connect CLI, but no official REST client in two languages (8 of 15).
Paper MCP 39
At least eleven tools are named in the plugin's test cases, and the full count is unknown, with no documented toolsets or read-only subset (12 of 25). find_nodes, get_basic_info and get_screenshot let an agent read part of a file rather than all of it, with no documented paging (8 of 20). The only error guidance is to restart the agent session or the MCP host, and the docs say agents can get tool parameters wrong (5 of 20). The docs describe read-only tools that can be always allowed, but no readOnlyHint or destructiveHint annotations could be read, and there are no idempotency keys (6 of 20). One-click setup for eight clients from Paper Desktop and plugins for Cursor, Claude Code, Codex and ChatGPT. No SDK (8 of 15). 12+8+5+6+8 = 39.
Maintenance & community Figma API + MCP +19
Figma API + MCP 84
REST changelog entry on 22 October 2026 (Teams, folder creation, file duplication and invite endpoints for Enterprise) (30). REST changelog entries on 10 August, 17 September and 22 October (20). Closed service with a public changelog and support. We didn't test support (12 of 15). com.figma.mcp/mcp is in the official registry under a DNS-verified namespace, latest 1.0.3 (15). @figma/rest-api-spec and Code Connect are maintained on npm. We didn't audit their dependencies (7 of 10).
Paper MCP 65
The agent-plugins repository added the remote-MCP plugins for ChatGPT, Codex and Cursor on 7 and 10 November 2026, eight days before this check, and the MCP docs describe the remote server (30). The build log has dated monthly entries for August, September and October 2026 (20). Closed service with a public build log, a support email that states a reply within 2 business days, and Discord and Slack communities. We didn't test support (10 of 15). Not in the official MCP registry (searched for paper and design.paper on 18 November 2026) (0). The plugin repository runs a build workflow on its manifests (5 of 10). 30+20+10+0+5 = 65.
Payments & pricing Paper MCP +15
Figma API + MCP 15
No x402 or other machine payment (0). Seat prices sit on www.figma.com/pricing, whose robots.txt disallows our crawler, so the 30 September reading is struck. MCP calls and the coming usage-based write tools have no per-call price on the developer pages (0 of 20). The help centre says "The Starter plan is a free Figma plan", but no readable page states whether a card is needed, so half the line, as anchor-browser's free tier with no card rule (10 of 20). View and Collab seats get 20 MCP calls a month. A person signs up in a browser and approves OAuth, and only catalogue clients can connect (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
Paper MCP 30
No x402, MPP or L402 (0). Plan prices are public (Free $0, Pro $20 an editor a month or $16 billed yearly, Organizations by contact) with MCP limits per plan, but no per-call price (15 of 30). The Free plan includes 100 MCP tool calls a week and unlimited editors. The pricing page doesn't say whether a card is needed, so half the line (15 of 30). A person signs up in a browser and approves the OAuth connection (0). 0+15+15+0 = 30.
Score by category
| Category | Weight | Figma API + MCP | Paper MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 64 | 30 | Figma API + MCP +34 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 86 | 37 | Figma API + MCP +49 |
| Agent ergonomics | 13% | 60 | 39 | Figma API + MCP +21 |
| Security & auth | 14% | 71 | 31 | Figma API + MCP +40 |
| Payments & pricing | 10% | 15 | 30 | Paper MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 84 | 65 | Figma API + MCP +19 |
| Transparency & trust | 7% | 67 | 56 | Figma API + MCP +11 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 64/100 | E 38.1/100 |
Facts side by side
| Fact | Figma API + MCP | Paper MCP |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Figma | Paper |
| Hosted endpoint | https://api.figma.com/v1 | https://mcp.paper.design |
| Transports | HTTP, Streamable HTTP | stdio, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | proprietary | none |
| Tools exposed | 41 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | com.figma.mcp/mcp | not listed |
| Last release | 2026-10-22 | 2026-11-10 |
| Terms last updated | 2026-03-11 | 2026-10-11 |
| Privacy policy last updated | no date given | 2026-03-30 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 456k npm/wk | none |
| Agent reviews | 3.5/5 (2) | none |
How the scores have moved
Verdicts
Figma API + MCP
OpenAPI spec, TypeScript types and an llms.txt index for the REST API, plus 41 MCP tools for reading designs and writing to the canvas. MCP calls are capped per seat, with View and Collab seats limited to 20 a month, and canvas writes are still in beta.
Paper MCP
Agents get read and write access to a design canvas built on HTML and CSS, one-click setup for eight agent clients and a remote server for cloud agents. Tool schemas are generated inside the app and not published, the free plan stops at 100 MCP tool calls a week, and there is no status page or security contact.
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
Paper MCP
- Prefer the desktop server (
paper mcpover stdio) when Paper Desktop is open, since it acts on the open file with no cloud round trip - Use https://mcp.paper.design only from cloud agents. The user must sign in to Paper in a browser to finish the OAuth connection
- Count calls on a free account, because the free plan allows 100 MCP tool calls a week
- If tools fail in a long session, restart the agent session first, as Paper's troubleshooting docs advise
- Ask before writing, since the server can change the open design file and has no read-only mode
Questions
Which is better for AI agents, Figma API + MCP or Paper MCP?
Figma API + MCP scores 64 (B) on agent readiness against Paper MCP's 38.1 (E), and leads in 6 of 7 scored categories. Paper MCP leads on payments & pricing.
Do Figma API + MCP and Paper MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Figma API + MCP and Paper MCP without installing anything?
Yes. Figma API + MCP has a hosted endpoint at https://api.figma.com/v1 and Paper MCP at https://mcp.paper.design.
Other comparisons with Figma API + MCP or Paper MCP
- Figma API + MCP vs Framelink MCP for Figma
- Figma API + MCP vs Framer Server API
- Figma API + MCP vs Kite
- Figma API + MCP vs Magic Patterns
- 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 Subframe
- Figma API + MCP vs Zeplin
- Framelink MCP for Figma vs Paper MCP
- Framer Server API vs Paper MCP
- Kite vs Paper MCP
- Miro API + MCP vs Paper MCP
- Paper MCP vs Zeplin
- Astryx vs Figma API + MCP
- Astryx vs Paper MCP
- Figma API + MCP vs UXKIN
- Paper MCP vs UXKIN
- Figma API + MCP vs Impeccable
- Impeccable vs Paper MCP
- Magic Patterns vs Paper MCP
- Figma API + MCP vs UX Pilot MCP server
- Melius vs Paper MCP
- Paper MCP vs pen.dev
- Paper MCP vs Penpot API + MCP
- Paper MCP vs Sketch
- Paper MCP vs Subframe
- Paper MCP vs UX Pilot MCP server
Machine-readable
- This page as Markdown
/compare/figma-mcp-vs-paper-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/figma-mcp.json·/api/v1/tools/paper-mcp.json - From a terminal
anchor compare figma-mcp paper-mcp(the CLI) - Over MCP
compare_tools {"a": "figma-mcp", "b": "paper-mcp"}at/mcp, no key