# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/figma-mcp-vs-miro
- Markdown: https://www.anchorterminal.com/compare/figma-mcp-vs-miro.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/compare/figma-mcp-vs-miro.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/figma-mcp-vs-miro.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-04

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 + MCP: grade B, 66.1/100, rank #164 of 452. Markdown https://www.anchorterminal.com/tools/figma-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/figma-mcp.json
- Miro API + MCP: grade B, 65.3/100, rank #175 of 452. Markdown https://www.anchorterminal.com/tools/miro.md · JSON https://www.anchorterminal.com/api/v1/tools/miro.json

## Which one, for what

Pick Figma API + MCP for maintenance & community (+7).

Pick Miro API + MCP for reliability (+14).

## Score by category

| Category | Weight | Figma API + MCP | Miro API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 59 | 73 | Miro API + MCP +14 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 85 | Figma API + MCP +1 |
| Agent ergonomics | 13% (16.2 this run) | 60 | 63 | Miro API + MCP +3 |
| Security & auth | 14% (17.5 this run) | 74 | 70 | Figma API + MCP +4 |
| Payments & pricing | 10% (12.5 this run) | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 84 | 77 | Figma API + MCP +7 |
| Transparency & trust | 7% (8.8 this run) | 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

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` so the model sees the current layout
5. 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

- [Figma API + MCP vs Framer Server API](https://www.anchorterminal.com/compare/figma-mcp-vs-framer.md)
- [Figma API + MCP vs Penpot API + MCP](https://www.anchorterminal.com/compare/figma-mcp-vs-penpot.md)
- [Framer Server API vs Miro API + MCP](https://www.anchorterminal.com/compare/framer-vs-miro.md)
- [Miro API + MCP vs Penpot API + MCP](https://www.anchorterminal.com/compare/miro-vs-penpot.md)