Head to head · Design code · October 2026 research run
Magic Patterns vs Paper MCP
Magic Patterns scores 64.9 (B) on agent readiness against Paper MCP's 38.1 (E), and leads in every scored category. Both do design code.
Best design workspace and canvas APIs for AI agents · All 162 design comparisons
Which one, for what
Best for Generating and iterating on coded React prototypes from a coding agent, and pulling a design into a codebase.
Ahead on
- Reliability, 75 against 30
- Schema & documentation, 84 against 37
- Agent ergonomics, 67 against 39
- Security & auth, 55 against 31
- Payments & pricing, 35 against 30
- Maintenance & community, 70 against 65
Watch for
MCP and API-key access need a paid seat, Starter at $20 a month
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 Magic Patterns +47
Magic Patterns 84
The MCP server is closed, so its tool definitions weren't read. The v3 API has an OpenAPI 3.0.3 description, served as a block in each API reference page; the file llms.txt links at /docs/openapi-v3.yml answered with a not-found page (20 of 25). llms.txt and a Markdown copy of every docs page (10). The tools page sets out four workflows with call order, says when to poll and how often, splits read from write tools and warns that the user may edit at any time (17 of 20). Parameters are typed and marked required, the feedback category is an enum, and file writes take an array of name and content pairs (10 of 15). Request and response examples, an error table (400, 401, 402, 403) and 409 behaviour on writes (12 of 15). Versioned /v3 paths, a v2 deprecation notice and a dated product changelog (15). 20 + 10 + 17 + 10 + 12 + 15 = 84.
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.
Reliability Magic Patterns +45
Magic Patterns 75
Hosted lines, for the MCP server and v3 API. A Statuspage at magicpatterns.statuspage.io with incident history, but its two components are Web Platform and Figma Plugin, with nothing for the API or MCP server (15 of 20). The history page and Atom feed post no incident since 9 January 2026, so the 90 days before this check are clean as far as the page covers (30). The page's /api/ path is disallowed by its robots.txt, so the JSON feeds weren't used. Rate limit published as 1,000 generations per 10 hours per key, with polling no faster than once every 60 seconds (15). No 429, Retry-After or backoff guidance and no idempotency keys. Design-system writes take a baseArtifactId and return 409 on a concurrent change, with re-read-and-retry advice (5 of 15). No SLA found below Enterprise's custom contracts (0). The MCP server and v3 API carry no beta label (10). 15 + 30 + 15 + 5 + 0 + 10 = 75.
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 Magic Patterns +28
Magic Patterns 67
24 documented tools (15 for 11 to 30), plus 5 back for the read-only endpoint that registers only 12 (20 of 25). Message history pages by 10 and version history by 20 with skip, and file reads take a list of names (14 of 20). Documented status codes, a 402 that leaves reads working and non-blocking validationErrors on design-system writes (15 of 20). No idempotency keys; 409 conflict checks on design-system writes, and annotations couldn't be read on the closed server (10 of 20). create_design needs no parameter and makes a blank scaffold, but there is no official SDK (8 of 15). 20 + 14 + 15 + 10 + 8 = 67.
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.
Security & auth Magic Patterns +24
Magic Patterns 55
OAuth 2.1 with PKCE S256, dynamic registration and a device flow, issued by oauth.magicpatterns.com with WorkOS keys. Scopes are openid, email, profile and offline_access only, so a token carries the user's whole workspace role. API keys are shown once, with no scopes, expiry or rotation documented (22 of 30). The read-only endpoint doesn't register the 13 tools that create, change or publish. There is no confirmation step on the write endpoint (14 of 20). Tools return design code and chat history that collaborators wrote, and no prompt-injection guidance was found (3 of 15). x-mp-agent-name attributes changes in the UI, and audit logs come with Enterprise only (8 of 15). The security page describes encryption, logging and the Render and MongoDB Atlas setup and points to SOC 2 reports in a Trust Center drawn by script, which wasn't read. No security.txt, disclosure policy or bug bounty found (8 of 20). 22 + 14 + 3 + 8 + 8 = 55.
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.
Payments & pricing Magic Patterns +5
Magic Patterns 35
No x402, MPP or L402. A 402 means out of credits, with no payment requirements (0). Seat prices are public and the on-demand rate is $0.02 a credit, but a generation's credit cost isn't known before it runs (typical 70 per generation per the docs), so between plan-only and per-unit (15 of 20). The MCP overview and the plans table say MCP and API-key access need a paid plan, while the v3 API page says free-tier accounts can call v3 up to their credits. Taking the stricter reading for the MCP surface, the free tier gives an agent no MCP access (5 of 20). A person signs in through the browser; dynamic client registration and the device flow still end with a human approval (3 of 20). 0 + 15 + 5 + 3 = 23. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 23 is 35.
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.
Maintenance & community Magic Patterns +5
Magic Patterns 70
Changelog entry on 5 November 2026, the day before this check (30). Entries on twelve dates since 8 August, among them 23 September and 12 to 30 October (20). Closed service with a public changelog, email support within one to two business days, in-app chat and a Slack community. We didn't test them (12 of 15). Not in the official MCP registry (searches for magic-patterns and magicpatterns returned nothing of theirs). Official Claude connector, Cursor plugin and Codex plugin, and no SDKs (5 of 15). No public package or repository to check (3 of 10). 30 + 20 + 12 + 5 + 3 = 70.
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.
Score by category
| Category | Weight | Magic Patterns | Paper MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 30 | Magic Patterns +45 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 37 | Magic Patterns +47 |
| Agent ergonomics | 13% | 67 | 39 | Magic Patterns +28 |
| Security & auth | 14% | 55 | 31 | Magic Patterns +24 |
| Payments & pricing | 10% | 35 | 30 | Magic Patterns +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 65 | Magic Patterns +5 |
| Transparency & trust | 7% | 60 | 56 | Magic Patterns +4 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 64.9/100 | E 38.1/100 |
Facts side by side
| Fact | Magic Patterns | Paper MCP |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | North Park Labs, Inc. (Magic Patterns) | Paper |
| Hosted endpoint | https://mcp.magicpatterns.com/mcp | https://mcp.paper.design |
| Transports | Streamable HTTP, HTTP | stdio, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Closed service under the Magic Patterns terms of service (last updated 1 April 2025) | none |
| Tools exposed | 24 | none |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| Last release | 2026-11-05 | 2026-11-10 |
| Terms last updated | 2025-04-01 | 2026-10-11 |
| Privacy policy last updated | 2025-04-01 | 2026-03-30 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
How the scores have moved
Verdicts
Magic Patterns
Agents can create, prompt, read and edit coded prototypes through 24 documented MCP tools or a matching REST API, with a read-only endpoint and 409 conflict checks on writes. MCP access needs a paid seat from $20 a month, OAuth scopes don't narrow access below the user's role, and the status page doesn't track the API or MCP server.
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
Magic Patterns
- Use https://mcp.magicpatterns.com/mcp/readonly when the task only reads designs
- Call
get_design_statusbefore any change and poll it no more than once every 60 seconds - Pass
baseArtifactIdfromget_design_systemon writes, and on 409 re-read before retrying - Treat a 402 as out of credits and ask the user; read tools keep working
- Send
x-mp-agent-nameso the user sees which agent made a change
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, Magic Patterns or Paper MCP?
Magic Patterns scores 64.9 (B) on agent readiness against Paper MCP's 38.1 (E), and leads in every scored category.
Do Magic Patterns and Paper MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Magic Patterns and Paper MCP without installing anything?
Yes. Magic Patterns has a hosted endpoint at https://mcp.magicpatterns.com/mcp and Paper MCP at https://mcp.paper.design.
Other comparisons with Magic Patterns or Paper MCP
- Figma API + MCP vs Magic Patterns
- Figma API + MCP vs Paper MCP
- Framelink MCP for Figma vs Magic Patterns
- Framelink MCP for Figma vs Paper MCP
- Framer Server API vs Magic Patterns
- Framer Server API vs Paper MCP
- Kite vs Magic Patterns
- Kite vs Paper MCP
- Magic Patterns vs Miro API + MCP
- Miro API + MCP vs Paper MCP
- Paper MCP vs Zeplin
- Astryx vs Magic Patterns
- Astryx vs Paper MCP
- Magic Patterns vs UXKIN
- Paper MCP vs UXKIN
- Impeccable vs Magic Patterns
- Impeccable vs Paper MCP
- Magic Patterns vs pen.dev
- Magic Patterns vs Penpot API + MCP
- Magic Patterns vs Sketch
- Magic Patterns vs Subframe
- Magic Patterns vs UX Pilot MCP server
- Magic Patterns vs Zeplin
- Magic Patterns vs Melius
- 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/magic-patterns-vs-paper-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/magic-patterns.json·/api/v1/tools/paper-mcp.json - From a terminal
anchor compare magic-patterns paper-mcp(the CLI) - Over MCP
compare_tools {"a": "magic-patterns", "b": "paper-mcp"}at/mcp, no key