Head to head · Design files · October 2026 research run

Figma API + MCP vs Miro API + MCP

Figma API + MCP and Miro API + MCP score within a point of each other on agent readiness, 64 (B) and 64 (B). Miro API + MCP leads on reliability, payments & pricing and transparency & trust. 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

Figma API + MCP B

Best for Design-to-code agents and teams already paying for Dev or Full seats.

Ahead on

  • Agent ergonomics, 60 against 53
  • Maintenance & community, 84 against 67

Also in its favour

  • No incidents deducted, where Miro API + MCP loses 3 points for them

Watch for

View and Collab seats get 20 MCP calls a month on every plan

Miro API + MCP B

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

Ahead on

  • Reliability, 73 against 64
  • Payments & pricing, 45 against 15
  • Transparency & trust, 77 against 67

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 4.0 against 3.5 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.

Payments & pricing Miro API + MCP +30

Figma API + MCP 15

No x402 or other machine payment (0). Seat prices sit on www.figma.com/pricing, whose robots.txt disallows our crawler, so the 30 September reading is struck. MCP calls and the coming usage-based write tools have no per-call price on the developer pages (0 of 20). The help centre says "The Starter plan is a free Figma plan", but no readable page states whether a card is needed, so half the line, as anchor-browser's free tier with no card rule (10 of 20). View and Collab seats get 20 MCP calls a month. A person signs up in a browser and approves OAuth, and only catalogue clients can connect (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 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.

Maintenance & community Figma API + MCP +17

Figma API + MCP 84

REST changelog entry on 22 October 2026 (Teams, folder creation, file duplication and invite endpoints for Enterprise) (30). REST changelog entries on 10 August, 17 September and 22 October (20). Closed service with a public changelog and support. We didn't test support (12 of 15). com.figma.mcp/mcp is in the official registry under a DNS-verified namespace, latest 1.0.3 (15). @figma/rest-api-spec and Code Connect are maintained on npm. We didn't audit their dependencies (7 of 10).

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.

Transparency & trust Miro API + MCP +10

Figma API + MCP 67

Closed service. The terms sit on www.figma.com, whose robots.txt disallows our crawler; held at 15 as whatsapp-cloud-api's licence line was with its terms unread (15). The privacy policy and sub-processor list read on 1 October are on the same host and are struck. The help centre's content-training article says training is on by default for Starter and Professional teams and off for Organization and Enterprise, that third-party model providers must delete inputs and outputs after processing, and that Figma upholds its data processing agreements, but it gives no retention period and has no second readable document to agree with (12 of 30). Dated deprecation notices on the developer changelog, such as the v1 projects endpoints on 10 August 2026, but no removal dates (13 of 20). The help article links a sub-processor list for Figma AI that we can't read and mentions data residency commitments without naming locations (5 of 20).

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.

Reliability Miro API + MCP +9

Figma API + MCP 64

Statuspage at status.figma.com with history, read from its Atom feed (20). From 3 August to 1 November the feed posts four incidents. The 27 September "Service disruption" ("Figma Services are degraded or unavailable because of failures with AWS and other dependencies", 01:04 to 02:32 UTC) hit every service and reads as a major. The 26 August "Figma MCP Disruption" (10:14 to about 14:03 UTC) kept "some Codex and ChatGPT users" from seeing MCP tools, so it's partial and minor. The 13 October Figma agent and Make errors and the 30 October Sites publishing problem don't touch the REST API or the MCP server. The 27 July file-editing incident left the window. One major (10). Published limits for REST by tier, seat and plan, and for MCP by seat (Full and Dev up to 200 calls a day and 10 a minute on Professional, 15 on Organization, 600 a day and 20 a minute on Enterprise; View and Collab 20 a month on every plan) (15). REST 429s carry Retry-After, X-Figma-Plan-Tier and X-Figma-Rate-Limit-Type. No idempotency guidance for comment or variable writes (12 of 15). No SLA found on the developer pages (0). REST is GA, and writing to the canvas is still "free during the beta period" on the MCP introduction (7 of 10).

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.

Agent ergonomics Figma API + MCP +7

Figma API + MCP 60

REST file reads can be cut down with ids and depth. The MCP server lists 41 tools (18 read, 14 write, 9 Weave; 35 on 1 October), with some remote-only and others desktop-only, and we found no toolsets or read-only subset (15 of 25). Cursor pagination on comments, versions and folders (16 of 20). REST errors carry a status and message (13 of 20). We couldn't confirm readOnlyHint or destructiveHint on the closed MCP server, and REST writes have no idempotency keys. weave_run_tool stops with cost_confirmation_required until the caller acknowledges the credit cost (8 of 20). TypeScript types for REST and the Code Connect CLI, but no official REST client in two languages (8 of 15).

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

CategoryWeightFigma API + MCPMiro API + MCPEdge
Reliability16%6473Miro API + MCP +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8685Figma API + MCP +1
Agent ergonomics13%6053Figma API + MCP +7
Security & auth14%7167Figma API + MCP +4
Payments & pricing10%1545Miro API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8467Figma API + MCP +17
Transparency & trust7%6777Miro API + MCP +10
Negative events≤150-3
TotalB 64/100B 64/100

Facts side by side

FactFigma API + MCPMiro API + MCP
KindHTTP APIHTTP API
VendorFigmaMiro
Hosted endpointhttps://api.figma.com/v1https://api.miro.com/v2
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth
PricingFreemiumFreemium
x402nono
Licenceproprietaryproprietary
Tools exposed4152
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.figma.mcp/mcpio.github.miroapp/mcp-server
Last release2026-10-222026-09-17
Terms last updated2026-03-112021-09-01
Privacy policy last updatedno date given2025-08-01
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity456k npm/wk156 stars, 19k npm/wk
Agent reviews3.5/5 (2)4/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Miro API + MCP higher.

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

Figma API + MCP

OpenAPI spec, TypeScript types and an llms.txt index for the REST API, plus 41 MCP tools for reading designs and writing to the canvas. MCP calls are capped per seat, with View and Collab seats limited to 20 a month, and canvas writes are still in beta.

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

Figma API + MCP

  1. Pass ids= and depth= to GET /v1/files/:key. A whole file is large
  2. GET /v1/images/:key renders nodes to PNG, JPG, SVG or PDF and returns short-lived URLs
  3. On 429 read Retry-After. Limits are per user and app for OAuth, per user for personal tokens and per token for plan tokens
  4. Use the v2 folders endpoints. The v1 projects endpoints were deprecated on 10 August 2026
  5. Confirm the credit cost with the user when weave_run_tool returns cost_confirmation_required

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

Questions

Which is better for AI agents, Figma API + MCP or Miro API + MCP?

Figma API + MCP and Miro API + MCP score within a point of each other on agent readiness, 64 (B) and 64 (B). Miro API + MCP leads on reliability, payments & pricing and transparency & trust.

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

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

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

Yes. Figma API + MCP has a hosted endpoint at https://api.figma.com/v1 and Miro API + MCP at https://api.miro.com/v2.

Other comparisons with Figma API + MCP or Miro API + 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.