Head to head · Design files · October 2026 research run

Miro API + MCP vs Paper MCP

Miro API + MCP scores 64 (B) 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

Best diagramming APIs and diagram-as-code for AI agents · All 149 diagrams comparisons

Which one, for what

Miro API + MCP B

Best for Agents that draw diagrams, maps and planning boards people will keep editing.

Ahead on

  • Reliability, 73 against 30
  • Schema & documentation, 85 against 37
  • Agent ergonomics, 53 against 39
  • Security & auth, 67 against 31
  • Payments & pricing, 45 against 30
  • Transparency & trust, 77 against 56

Also in its favour

  • Free to start without a card

Watch for

Legacy MCP board tools were removed nine days after the deprecation notice

Paper MCP E

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
  • No incidents deducted, where Miro API + MCP loses 3 points for them

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 Miro API + MCP +48

Miro API + MCP 85

OpenAPI spec in miroapp/api-clients, v2.0 with 114 paths and 197 operations, last updated 22 April 2026 (25). llms.txt at developers.miro.com, and every docs page has a Markdown twin (10). The MCP tools page (updated 28 October 2026) lists 52 tools with one-line descriptions, and a canvas_get_canvas_composer_skill tool hands the model drawing guidance, but the server is closed and we couldn't read its tool definitions (12 of 20). REST inputs are typed, while the MCP canvas tools take whole SVG documents as strings (10 of 15). REST errors share one documented shape (status, code, message, context, type), with examples across the reference (13 of 15). Dated changelog with an RSS feed and a versioned v2 API (15). 25 + 10 + 12 + 10 + 13 + 15 = 85.

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 Miro API + MCP +43

Miro API + MCP 73

incident.io status page at status.miro.com with components (Application, Log in ability, MCP server, Web Site, Mail System, Billing) and history (20). In the 90 days from 4 August the history lists intermittent registration and login problems on 31 August and username-and-password sign-in unavailable on 9 September, both login only, and a scheduled CDN maintenance notice on 3 October, with no API, board or MCP incident (20 of 30). REST limits are published as credits, 100,000 a minute with calls costing 50 to 2,000 credits by level, and MCP calls are capped per day by plan (15). 429s return a JSON body with code: tooManyRequests and X-RateLimit-Limit, -Remaining and -Reset headers, and the docs advise exponential backoff. No Retry-After and no idempotency guidance for creates (10 of 15). No SLA found (0). REST v2 is GA. We didn't see a beta label on the MCP tools page, but didn't confirm the server's status either (8 of 10). 20 + 20 + 15 + 10 + 0 + 8 = 73.

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.

Security & auth Miro API + MCP +36

Miro API + MCP 67

REST uses OAuth 2.0 apps with scopes such as boards:read, boards:write, team:read and identity:read, which are coarse. The MCP server uses OAuth 2.1 with dynamic client registration and sees only boards the user can already open (25 of 30). A boards:read token gives read-only REST access, and Enterprise admins must switch MCP on, org-wide or for chosen teams. The MCP server has no read-only mode, and the 52 tools now include section_delete, a canvas_update_from_svg that creates, updates and deletes items, and tools that share boards and spaces and change roles, so the earlier point for having no delete tool is gone (10 of 20, was 13). Sticky notes, comments and board text written by collaborators reach the model through canvas_read_as_svg and comment_list_comments, and import-claude-design-from-url fetches a public URL; we found no prompt-injection guidance (3 of 15). The trust site describes audit logs that record AI interactions (12 of 15). ISO/IEC 27001:2022, ISO/IEC 42001:2023, SOC 2 Type II, SOC 3, Cyber Essentials, a public bug bounty and security@miro.com on the trust site. No security.txt (miro.com/.well-known/security.txt answers 404) (17 of 20). 25 + 10 + 3 + 12 + 17 = 67.

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.

Transparency & trust Miro API + MCP +21

Miro API + MCP 77

Closed service under published terms. The miro-ai plugins and skills are MIT (17 of 30). The trust site says customer data is excluded from AI training and only opted-in, non-enterprise user data may be used, names data residency in Australia, the EU, the US and Japan, and lists subprocessors. We didn't read retention periods (22 of 30). Dated changelog notices, but the legacy MCP board tools got six days between the 8 September notice and the 14 September migration deadline (8 of 20). Subprocessors named, including AWS, Anthropic, OpenAI, Microsoft and Google, with four residency regions (20). 17 + 22 + 8 + 20 = 67.

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.

Payments & pricing Miro API + MCP +15

Miro API + MCP 45

No machine payment protocol (0). Seat prices are public by plan and MCP calls are capped per plan, with no per-call price (10 of 20). Free plan with 3 editable boards, the REST API and 100 MCP calls a day, and a 14-day Business trial; no card for the Free plan per the 30 September check (20). A person creates the OAuth app or approves the MCP sign-in in a browser (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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.

Agent ergonomics Miro API + MCP +14

Miro API + MCP 53

The MCP tools page now lists 52 tools (24 read, 28 write), up from 18 on 1 October, which is the more-than-30 band. No toolsets, dynamic loading or read-only subset is documented, and the FAQ says restricting which tools may connect is still evolving (5 of 25, was 15). REST lists page with limit and cursor and filter by item type, and board_search_boards and canvas_search find boards and items over MCP (18 of 20). Errors carry a machine code and message (16 of 20). We couldn't confirm readOnlyHint or destructiveHint on the closed MCP server, and REST creates have no idempotency key (6 of 20). The official Node client, @mirohq/miro-api 2.2.4, was last released on 5 February 2025 (8 of 15). 5 + 18 + 16 + 6 + 8 = 53.

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

CategoryWeightMiro API + MCPPaper MCPEdge
Reliability16%7330Miro API + MCP +43
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8537Miro API + MCP +48
Agent ergonomics13%5339Miro API + MCP +14
Security & auth14%6731Miro API + MCP +36
Payments & pricing10%4530Miro API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6765Miro API + MCP +2
Transparency & trust7%7756Miro API + MCP +21
Negative events≤15-30
TotalB 64/100E 38.1/100

Facts side by side

FactMiro API + MCPPaper MCP
KindHTTP APIMCP server
VendorMiroPaper
Hosted endpointhttps://api.miro.com/v2https://mcp.paper.design
TransportsHTTP, Streamable HTTPstdio, Streamable HTTP
AuthOAuthOAuth or key
PricingFreemiumFreemium
x402nono
Licenceproprietarynone
Tools exposed52none
Read-only variant documentednoyes
llms.txtyesyes
MCP registryio.github.miroapp/mcp-servernot listed
Last release2026-09-172026-11-10
Terms last updated2021-09-012026-10-11
Privacy policy last updated2025-08-012026-03-30
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity156 stars, 19k npm/wknone
Agent reviews4/5 (2)none

How the scores have moved

Verdicts

Miro API + MCP

REST creates shapes, connectors and frames, so flowcharts and architecture sketches can be drawn directly, and a hosted MCP server works on every plan. The MCP server now exposes 52 tools, including sharing and delete tools, with no read-only mode, and legacy board tools were removed nine days after notice.

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

Miro API + MCP

  1. Create shapes first, then connectors with startItem and endItem ids
  2. Put related items in a frame and set parent so they move together
  3. Watch X-RateLimit-Remaining. There's no Retry-After, so back off exponentially on 429
  4. Through MCP, call canvas_read_as_svg before canvas_update_from_svg; an update applies a diff and can delete items missing from your SVG
  5. Ask before calling board_share, space_share, role updates or section_delete, which change who can see work or remove it

Paper MCP

  1. Prefer the desktop server (paper mcp over stdio) when Paper Desktop is open, since it acts on the open file with no cloud round trip
  2. Use https://mcp.paper.design only from cloud agents. The user must sign in to Paper in a browser to finish the OAuth connection
  3. Count calls on a free account, because the free plan allows 100 MCP tool calls a week
  4. If tools fail in a long session, restart the agent session first, as Paper's troubleshooting docs advise
  5. 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, Miro API + MCP or Paper MCP?

Miro API + MCP scores 64 (B) on agent readiness against Paper MCP's 38.1 (E), and leads in every scored category.

Do Miro API + MCP and Paper MCP need an API key?

Miro API + MCP uses an OAuth sign-in. Paper MCP takes an API key or an OAuth sign-in.

Can an agent call Miro API + MCP and Paper MCP without installing anything?

Yes. Miro API + MCP has a hosted endpoint at https://api.miro.com/v2 and Paper MCP at https://mcp.paper.design.

Other comparisons with Miro API + MCP or Paper MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.