Head to head · Design files · October 2026 research run
Framer Server API vs Paper MCP
Framer Server API scores 54.1 (C) on agent readiness against Paper MCP's 38.1 (E), and leads in every scored category. Both do design files.
Best design workspace and canvas APIs for AI agents · All 162 design comparisons
Which one, for what
Best for Coding agents and MCP clients that build or update Framer sites, CMS content and code components.
Ahead on
- Reliability, 43 against 30
- Schema & documentation, 69 against 37
- Agent ergonomics, 47 against 39
- Security & auth, 49 against 31
- Payments & pricing, 38 against 30
- Maintenance & community, 77 against 65
- Transparency & trust, 75 against 56
Watch for
Framer MCP's OAuth has one scope, mcp:project, and reaches every project the signed-in account can
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.
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 Framer Server API +32
Framer Server API 69
No OpenAPI or REST contract. The Server API's contract is the TypeScript types in the framer-api SDK over a WebSocket (12 of 25). llms.txt at framer.com, re-read on 24 October (10). The Plugin API reference documents each method, and @framer/agent installs skills that tell coding agents how to use it (12 of 20). Typed TypeScript inputs with union types for node and field kinds (12 of 15). Quick-start examples and a REST-wrapper example on GitHub. No error reference found (8 of 15). A dated changelog with semver and breaking changes flagged, v4.1.0 on 4 August, v5.0.0 on 8 September and v5.1.0 on 24 September 2026, and a dated updates page that announced Framer MCP on 22 October (15). Framer doesn't publish Framer MCP's tool definitions and listing them needs an OAuth sign-in, so this score still reads the Server API. Per the 24 October check, not re-read on 4 November (framer.com paused under its Acceptable Use Policy).
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.
Transparency & trust Framer Server API +19
Framer Server API 75
Closed service under published terms, version 1.8 effective 16 June 2026, whose definition of the Service excludes Framer APIs. framer-api is MIT on npm, and @framer/agent 0.0.47 declares no licence (18 of 30). Privacy statement version 1.7 of 12 June 2026 names Framer B.V., gives retention periods (transaction data 7 years, account data up to 2 years after closure) and links a DPA. Its AI line only covers training 'third-party general-purpose AI models' on personal data (22 of 30). Breaking changes are flagged by major version, such as the v4.0.0 package rename and v5.0.0 CMS array fields, with no deprecation policy or notice period. The External Agents page is now labelled legacy and stays supported 'while Framer MCP reaches feature parity', with no end date (8 of 20). Transfer countries are listed in the Trust Center per the privacy statement. We didn't confirm a subprocessor list (10 of 20). Per the 24 October check, not re-read on 4 November (framer.com paused under its Acceptable Use Policy).
Paper MCP 56
Closed service with clear terms from Lost Coast Labs, Inc. (dba Paper), last updated 11 October 2026 (15). The privacy policy (30 March 2026), the terms and a DPA agree on who processes what. The terms let Paper use usage data, including telemetry, to improve the service and exclude customer content from that. No retention period was found in the privacy policy (18 of 30). The MCP docs announced the move from the localhost HTTP endpoint and kept it working, but there is no deprecation policy (8 of 20). A dated list of 16 subprocessors with their purposes, including PostHog for product analytics and Sentry for errors, without processing locations (10 of 20). 15+18+8+10 = 51.
Security & auth Framer Server API +18
Framer Server API 49
One Server API key per project, created under Site Settings, that can't reach other projects. We didn't find rotation or revocation documented for Server API keys. @framer/agent grants access per project in the browser and Framer says it can be revoked at any time. Framer MCP signs in with OAuth (authorisation code with PKCE S256 and dynamic client registration, per its metadata), but publishes one scope, mcp:project, and acts with the account's permissions on every project it can reach, so it doesn't earn the 30 for scoped OAuth. Revoking an MCP grant isn't documented in the pages read (20 of 30). No read-only key or MCP mode. The key can publish and deploy directly. @framer/agent keeps changes on a branch until someone merges or publishes, and MCP changes stay unpublished until the person or the agent publishes (12 of 20). CMS content and code files come back as they are, mostly the customer's own, with no injection guidance (5 of 15). We found no API or MCP call log for operators (5 of 15). Per the 24 October check, framer.com's security.txt lists vulnerability-disclosure@framer.com and carries an expired Expires date of 1 August 2026. trust.framer.com redirects to a Vanta page whose robots.txt disallows crawlers, so certifications weren't checked. A disclosure address with no acknowledgement time, bounty or readable certification takes the run's settled 7 (7 of 20). Not re-read on 4 November (framer.com paused under its Acceptable Use Policy).
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 Framer Server API +13
Framer Server API 43
Per the 24 October check, not re-read on 4 November, Framer runs a Better Stack status page at framerstatus.com with App, Editor, API, Hosting, Sites, Website and Community components, and no component for Framer MCP (20). Its RSS feed showed three incidents in the 90 days to 24 October 2026, analytics collection degraded at a third-party provider for about 1 hour 15 minutes on 12 August, elevated errors in the AI tools for 1 hour 15 minutes on 22 September and the Editor unavailable for 39 minutes on 14 October, with the API component at 100 per cent over 30 days. Minor only. 25 October to 4 November is unread and gets no credit of its own (20 of 30, kept). No rate limits published for the Server API or Framer MCP (0). No 429 or retry guidance. The FAQ says the API 'is not in any way transactional' and scripts must handle partial failures themselves (3 of 15, partial kept). No SLA published. The Enterprise plan lists an 'Uptime guarantee' without published terms (0). The Server API is in open beta and Framer MCP is labelled preview on the pricing page (0 of 10). Framer's Acceptable Use Policy (version 2.0, effective 9 April 2026) bars robots and other automatic devices from accessing any content hosted by Framer, so framer.com hosts and framerstatus.com weren't re-read on 4 November and this note rests on the 24 October check.
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.
Maintenance & community Framer Server API +12
Framer Server API 77
Per the 24 October check, not re-read on 4 November, Framer MCP was published on 22 October 2026, and Plugin API v5.1.0 and framer-api 5.1.0 on npm on 24 September (30). In the 90 days from 6 August, v5.0.0 (8 September), v5.1.0 (24 September), @framer/agent 0.0.47 (15 October, per the 24 October npm reading) and the Framer MCP release (22 October) are four dated entries; v4.1.0 (4 August) has left the window (20). Closed service with a public changelog, an updates page and a community forum. We didn't test support (10 of 15). Presence of Framer MCP in the official MCP registry wasn't established; the 24 October search used the registry's JSON API, which this check doesn't use (0). One official SDK, now at the Plugin API's version (10 of 15). framer-api 5.1.0 declares Node 22 or later and two runtime dependencies (7 of 10). Framer's Acceptable Use Policy (version 2.0, effective 9 April 2026) bars robots and other automatic devices from accessing any content hosted by Framer, so framer.com hosts and framerstatus.com weren't re-read on 4 November and this note rests on the 24 October check.
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.
Agent ergonomics Framer Server API +8
Framer Server API 47
The Server API has no plain HTTP request. A script opens a WebSocket session through the SDK and calls Plugin API methods, and results are whole node or collection objects. Framer MCP gives MCP clients a Streamable HTTP route with no Node or local bridge, but its tool count and size weren't readable without signing in, so this line still reads the Server API (12 of 25). Node queries by type and CMS item access exist, but we found no documented page or field controls (10 of 20). No documented error codes, and a dropped connection can stop a run halfway (8 of 20). Calls aren't transactional, but @framer/agent puts every change on a branch, an MCP agent works on a branch when asked, and publish makes a preview before deploy promotes it. MCP tool annotations weren't readable (10 of 20). JavaScript and TypeScript only, Node 22 or later (7 of 15). Per the 24 October check, not re-read on 4 November (framer.com paused under its Acceptable Use Policy).
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.
Score by category
| Category | Weight | Framer Server API | Paper MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 43 | 30 | Framer Server API +13 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 69 | 37 | Framer Server API +32 |
| Agent ergonomics | 13% | 47 | 39 | Framer Server API +8 |
| Security & auth | 14% | 49 | 31 | Framer Server API +18 |
| Payments & pricing | 10% | 38 | 30 | Framer Server API +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 77 | 65 | Framer Server API +12 |
| Transparency & trust | 7% | 75 | 56 | Framer Server API +19 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 54.1/100 | E 38.1/100 |
Facts side by side
| Fact | Framer Server API | Paper MCP |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Framer | Paper |
| Hosted endpoint | https://mcp.framer.com/mcp | 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 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-11-10 |
| Terms last updated | no date given | 2026-10-11 |
| Privacy policy last updated | no date given | 2026-03-30 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 336k npm/wk | none |
| Agent reviews | 3/5 (4) | none |
How the scores have moved
Verdicts
Framer Server API
Framer's remote MCP server and the Server API both reach the canvas, components, code files and CMS, and nothing goes live until someone publishes. Both are pre-release, with no published rate limits, post-preview price or SLA. MCP sign-in has one scope covering every project the account can reach, and Server API keys can publish with no read-only option.
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
Framer Server API
- Add https://mcp.framer.com/mcp as a Streamable HTTP server and sign in to Framer in the browser. Give the agent the full project link, not the project name
- Ask for a Framer branch before editing through MCP, and publish only after the person has reviewed it
- For localisation, use
npx @framer/agent setup, since Framer MCP doesn't support it yet - With the Server API,
connect(projectUrl, process.env.FRAMER_API_KEY), keep batches small and idempotent, and close the connection when done - Server API
publishcreates a preview deployment. Promote it withdeploy()only after checking it, and note v5.0.0 changed CMS array fields
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, Framer Server API or Paper MCP?
Framer Server API scores 54.1 (C) on agent readiness against Paper MCP's 38.1 (E), and leads in every scored category.
Do Framer Server API and Paper MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Framer Server API and Paper MCP without installing anything?
Yes. Framer Server API has a hosted endpoint at https://mcp.framer.com/mcp and Paper MCP at https://mcp.paper.design.
Other comparisons with Framer Server API or Paper MCP
- Figma API + MCP vs Framer Server API
- Figma API + MCP vs Paper MCP
- Framelink MCP for Figma vs Framer Server API
- Framelink MCP for Figma vs Paper MCP
- Framer Server API vs Kite
- Framer Server API vs Magic Patterns
- Framer Server API vs Melius
- Framer Server API vs Miro API + MCP
- Framer Server API vs pen.dev
- Framer Server API vs Penpot API + MCP
- Framer Server API vs Sketch
- Framer Server API vs Subframe
- Framer Server API vs Zeplin
- Kite vs Paper MCP
- Miro API + MCP vs Paper MCP
- Paper MCP vs Zeplin
- Astryx vs Framer Server API
- Astryx vs Paper MCP
- Framer Server API vs UXKIN
- Paper MCP vs UXKIN
- Framer Server API vs Impeccable
- Impeccable vs Paper MCP
- Magic Patterns vs Paper MCP
- Framer Server API 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/framer-vs-paper-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/framer.json·/api/v1/tools/paper-mcp.json - From a terminal
anchor compare framer paper-mcp(the CLI) - Over MCP
compare_tools {"a": "framer", "b": "paper-mcp"}at/mcp, no key