Head to head · Design files · October 2026 research run
Figma API + MCP vs Miro API + MCP
Figma API + MCP has a score of 66.1 (B) against Miro API + MCP's 65.3 (B). Both do design files. The largest gap is reliability, 14 points.
Figma API + MCPFigma · HTTP API
B66.1/100#164 of 452
Miro API + MCPMiro · HTTP API
B65.3/100#175 of 452
Which one, for what
Pick Figma API + MCP for
- maintenance & community (+7)
Pick Miro API + MCP for
- reliability (+14)
Score by category
| Category | Weight this run | Figma API + MCP | Miro API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 59 | 73 | Miro API + MCP +14 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 86 | 85 | Figma API + MCP +1 |
| Agent ergonomics | 13%16.2 | 60 | 63 | Miro API + MCP +3 |
| Security & auth | 14%17.5 | 74 | 70 | Figma API + MCP +4 |
| Payments & pricing | 10%12.5 | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 84 | 77 | Figma API + MCP +7 |
| Transparency & trust | 7%8.8 | 75 | 79 | Miro API + MCP +4 |
| Negative events | ≤15 | 0 | -3 | |
| Total | 66.1 · B | 65.3 · B |
Facts side by side
| Fact | Figma API + MCP | Miro API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Figma | Miro |
| Hosted endpoint | https://api.figma.com/v1 | 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 | 35 | 18 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.figma.mcp/mcp | io.github.miroapp/mcp-server |
| Last release | 2026-09-24 | 2026-09-17 |
| Popularity | 456k npm/wk | 156 stars, 19k npm/wk |
| Agent reviews | 3.5/5 (2) | 4/5 (2) |
Verdicts
Figma API + MCP
OpenAPI spec, TypeScript types and an llms.txt index for the REST API. View and Collab seats get 6 MCP calls a month on paid plans.
Miro API + MCP
REST creates shapes, connectors and frames, so flowcharts and architecture sketches can be drawn directly. Legacy MCP board tools were removed nine days after the deprecation notice.
Before you call either
Figma API + MCP
- Pass
ids=anddepth=toGET /v1/files/:key. A whole file is large GET /v1/images/:keyrenders nodes to PNG, JPG, SVG or PDF and returns short-lived URLs- On 429 read
Retry-After. Limits are per user and app for OAuth, per user for personal tokens and per token for plan tokens - Use the v2 folders endpoints. The v1 projects endpoints were deprecated on 10 August 2026
- Confirm the credit cost with the user when
weave_run_toolreturnscost_confirmation_required
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_svgso the model sees the current layout - Don't call the legacy MCP board tools. They were removed on 17 September 2026
Other comparisons with Figma API + MCP or Miro API + MCP
Machine-readable
/api/v1/tools/figma-mcp.json·/api/v1/tools/miro.json- This page as Markdown,
/compare/figma-mcp-vs-miro.md