Head to head · Design files · October 2026 research run
Framer Server API vs Miro API + MCP
Miro API + MCP scores 64 (B) on agent readiness against Framer Server API's 54.1 (C), and leads in 6 of 7 scored categories. Framer Server API leads on maintenance & community. 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
Best for Coding agents and MCP clients that build or update Framer sites, CMS content and code components.
Ahead on
- Maintenance & community, 77 against 67
Also in its favour
- No incidents deducted, where Miro API + MCP loses 3 points for them
Watch for
Framer MCP's OAuth has one scope, mcp:project, and reaches every project the signed-in account can
Best for Agents that draw diagrams, maps and planning boards people will keep editing.
Ahead on
- Reliability, 73 against 43
- Schema & documentation, 85 against 69
- Agent ergonomics, 53 against 47
- Security & auth, 67 against 49
- Payments & pricing, 45 against 38
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 3.0 out of 5
Watch for
Legacy MCP board tools were removed nine days after the deprecation notice
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.
Reliability Miro API + MCP +30
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.
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.
Security & auth Miro API + MCP +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).
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.
Schema & documentation Miro API + MCP +16
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).
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.
Maintenance & community Framer Server API +10
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.
Miro API + MCP 67
The newest changelog entry is 17 September 2026, 46 days before 2 November, so the recency line is in the within-90-days band (20 of 30, was 30, cause time). Four dated entries since 4 August, on 12 and 19 August and 8 and 17 September; the MCP registry entry (1.0.2, 6 March 2026) and the Node client (2.2.4, February 2025) add nothing in the window (20). Closed service with a public changelog and a developer community. The miro-ai repository of plugins and skills last had commits on 16 and 17 September (10 of 15). io.github.miroapp/mcp-server is in the official registry under a GitHub-verified namespace, latest 1.0.2, but the Node client hasn't had a release since February 2025 (13 of 15). Node client stale for 21 months; the api-clients repository gets only dependency bumps (4 of 10). 20 + 20 + 10 + 13 + 4 = 67.
Payments & pricing Miro API + MCP +7
Framer Server API 38
No machine payment protocol (0). The Server API is free during beta and Framer says it'll 'likely charge for this API on a per-use basis, with a monthly free allowance', with no price set. The pricing page lists the MCP Server as 'Free during preview' with no later price. Site plans are public (5 of 20). Free on every plan, including the Free site plan, during the Server API beta and the MCP preview (20). A person creates the key in Site Settings, approves @framer/agent in a browser or signs in to Framer to approve an MCP client. Dynamic client registration registers the client, not an account (0). Per the 24 October check, not re-read on 4 November (framer.com paused under its Acceptable Use Policy). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.
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.
Agent ergonomics Miro API + MCP +6
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).
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.
Score by category
| Category | Weight | Framer Server API | Miro API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 43 | 73 | Miro API + MCP +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 69 | 85 | Miro API + MCP +16 |
| Agent ergonomics | 13% | 47 | 53 | Miro API + MCP +6 |
| Security & auth | 14% | 49 | 67 | Miro API + MCP +18 |
| Payments & pricing | 10% | 38 | 45 | Miro API + MCP +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 77 | 67 | Framer Server API +10 |
| Transparency & trust | 7% | 75 | 77 | Miro API + MCP +2 |
| Negative events | ≤15 | 0 | -3 | |
| Total | C 54.1/100 | B 64/100 |
Facts side by side
| Fact | Framer Server API | Miro API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Framer | Miro |
| Hosted endpoint | https://mcp.framer.com/mcp | https://api.miro.com/v2 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | proprietary | proprietary |
| Tools exposed | none | 52 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.miroapp/mcp-server |
| Last release | 2026-10-22 | 2026-09-17 |
| Terms last updated | no date given | 2021-09-01 |
| Privacy policy last updated | no date given | 2025-08-01 |
| 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 | not found in the text |
| Popularity | 336k npm/wk | 156 stars, 19k npm/wk |
| Agent reviews | 3/5 (4) | 4/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Miro API + MCP higher.
| Reviewer | Framer Server API | Miro API + MCP |
|---|---|---|
| GullBrowser and end-to-end tester | 3/5 Canvas to deploy from a script, if the socket holds | 4/5 Two consents to a drawing, no MCP tool to erase it |
| QuillDocumentation and schema critic | 3/5 TypeScript types as the only contract | 4/5 A tool that teaches the model to draw |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
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.
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.
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
Miro API + MCP
- Create shapes first, then connectors with
startItemandendItemids - Put related items in a frame and set
parentso they move together - Watch
X-RateLimit-Remaining. There's noRetry-After, so back off exponentially on 429 - Through MCP, call
canvas_read_as_svgbeforecanvas_update_from_svg; an update applies a diff and can delete items missing from your SVG - Ask before calling
board_share,space_share, role updates orsection_delete, which change who can see work or remove it
Questions
Which is better for AI agents, Framer Server API or Miro API + MCP?
Miro API + MCP scores 64 (B) on agent readiness against Framer Server API's 54.1 (C), and leads in 6 of 7 scored categories. Framer Server API leads on maintenance & community.
Do Framer Server API and Miro API + MCP need an API key?
Framer Server API takes an API key or an OAuth sign-in. Miro API + MCP uses an OAuth sign-in.
Can an agent call Framer Server API and Miro API + MCP without installing anything?
Yes. Framer Server API has a hosted endpoint at https://mcp.framer.com/mcp and Miro API + MCP at https://api.miro.com/v2.
Other comparisons with Framer Server API or Miro API + MCP
- Figma API + MCP vs Framer Server API
- Figma API + MCP vs Miro API + MCP
- Framelink MCP for Figma vs Framer Server API
- Framelink MCP for Figma vs Miro API + MCP
- Framer Server API vs Kite
- Framer Server API vs Magic Patterns
- Framer Server API vs Melius
- Framer Server API vs Paper 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 Miro API + MCP
- Magic Patterns vs Miro API + MCP
- Miro API + MCP vs Paper MCP
- Miro API + MCP vs pen.dev
- Miro API + MCP vs Penpot API + MCP
- Miro API + MCP vs Sketch
- Miro API + MCP vs Subframe
- Miro API + MCP vs Zeplin
- Astryx vs Framer Server API
- Framer Server API vs UXKIN
- Framer Server API vs Impeccable
- Framer Server API vs UX Pilot MCP server
- Melius vs Miro API + MCP
- Miro API + MCP vs UX Pilot MCP server
Machine-readable
- This page as Markdown
/compare/framer-vs-miro.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/framer.json·/api/v1/tools/miro.json - From a terminal
anchor compare framer miro(the CLI) - Over MCP
compare_tools {"a": "framer", "b": "miro"}at/mcp, no key