# Figma API + MCP vs Paper MCP (slim)

> Figma scores 64 (B) to Paper MCP's 38.1 (E) for design files. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/figma-mcp-vs-paper-mcp.md (~5,100 tokens) · this version ~1,130 tokens · JSON https://www.anchorterminal.com/compare/figma-mcp-vs-paper-mcp.json · canonical https://www.anchorterminal.com/compare/figma-mcp-vs-paper-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- Figma API + MCP: B 64, rank #605 of 1557 · https://www.anchorterminal.com/tools/figma-mcp.min.md
- Paper MCP: E 38.1, rank #1404 of 1557 · https://www.anchorterminal.com/tools/paper-mcp.min.md
- Figma API + MCP, good 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.
- Paper MCP, good 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 Runs on your own machine.

| Category | Figma API + MCP | Paper MCP |
| --- | --- | --- |
| Reliability (16%) | 64 | 30 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 37 |
| Agent ergonomics (13%) | 60 | 39 |
| Security & auth (14%) | 71 | 31 |
| Payments & pricing (10%) | 15 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 84 | 65 |
| Transparency & trust (7%) | 67 | 56 |

| Fact (where they differ) | 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 |
| Licence | proprietary | none |
| Tools exposed | 41 | none |
| Read-only variant documented | no | 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 |
| Popularity | 456k npm/wk | none |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Schema & documentation, Figma API + MCP +49: Figma API + MCP 86 (Public OpenAPI spec in figma/rest-api-spec, with TypeScript types on npm (25).); 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.)
- 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…); 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 rea…)
- Reliability, Figma API + MCP +34: Figma API + MCP 64 (Statuspage at status.figma.com with history, read from its Atom feed (20).); 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 ins…)
- Agent ergonomics, Figma API + MCP +21: Figma API + MCP 60 (REST file reads can be cut down with `ids` and `depth`.); 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).)
- 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).); 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 doc…)
- Payments & pricing, Paper MCP +15: Figma API + MCP 15 (No x402 or other machine payment (0).); Paper MCP 30 (No x402, MPP or L402 (0).)
