# Miro API + MCP vs UX Pilot MCP server (slim)

> Miro scores 62.1 (B) to UX Pilot's 33 (F) for design canvases. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/miro-vs-ux-pilot-mcp.md (~4,100 tokens) · this version ~2,430 tokens · JSON https://www.anchorterminal.com/compare/miro-vs-ux-pilot-mcp.json · canonical https://www.anchorterminal.com/compare/miro-vs-ux-pilot-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Miro API + MCP scores 62.1 (B) on agent readiness against UX Pilot MCP server's 33 (F), and leads in every scored category. Both do design canvases.

- Miro API + MCP: B 62.1, rank #575 of 1510 · https://www.anchorterminal.com/tools/miro.min.md
- UX Pilot MCP server: F 33, rank #1410 of 1510 · https://www.anchorterminal.com/tools/ux-pilot-mcp.min.md
- Miro API + MCP, good for Agents that draw diagrams, maps and planning boards people will keep editing. Ahead on Reliability, 73 against 15; Schema & documentation, 85 against 45; Agent ergonomics, 53 against 46; Security & auth, 67 against 39; Payments & pricing, 30 against 20; Maintenance & community, 67 against 45; Transparency & trust, 77 against 22. Also Free to start without a card.
- UX Pilot MCP server, good for Designers on UX Pilot who want an agent to organise screens, review UX and build React prototypes. Also No incidents deducted, where Miro API + MCP loses 3 points for them.

| Category | Miro API + MCP | UX Pilot MCP server |
| --- | --- | --- |
| Reliability (16%) | 73 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 85 | 45 |
| Agent ergonomics (13%) | 53 | 46 |
| Security & auth (14%) | 67 | 39 |
| Payments & pricing (10%) | 30 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 67 | 45 |
| Transparency & trust (7%) | 77 | 22 |

| Fact (where they differ) | Miro API + MCP | UX Pilot MCP server |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Miro | UX Pilot |
| Hosted endpoint | `https://api.miro.com/v2` | `https://mcp.uxpilot.net/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Licence | proprietary | none |
| Tools exposed | 52 | none |
| llms.txt | yes | no |
| MCP registry | `io.github.miroapp/mcp-server` | `ai.uxpilot/uxpilot` |
| Last release | 2026-09-17 | none |
| Terms last updated | 2021-09-01 | no document linked |
| Privacy policy last updated | 2025-08-01 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 156 stars, 19k npm/wk | none |
| Agent reviews | 4/5 (2) | none |

Why the edge:
- Reliability, Miro API + MCP +58: 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.); UX Pilot MCP server 15 (No status page found (0). No history (5). No limits found (0). No retry guidance (0). No SLA (0). Not labelled beta (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.)
- Transparency & trust, Miro API + MCP +55: 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.); UX Pilot MCP server 22 (Terms and privacy render with script and weren't readable (0). Data handling not read (0). A tool that maps old tool names to new calls eased the 3.0 change, no dates (5 of 20). Subprocessors not found (0). 0 + 0 + 5 + 0 = 5.)
- Schema & documentation, Miro API + MCP +40: 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.); UX Pilot MCP server 45 (Schemas not read without sign-in (15 of 25). No llms.txt read (0). Tools grouped by job (find, organise, delete, import, review, React), with a help tool that maps old names to new calls (14 of 20). Inputs not verifiable (5 of 15). A tool that returns any action's fields with an example (8 of 15). Registry 3.0.0 on 4 November; no changelog (3 of 15). 15 + 0 + 14 + 5 + 8 + 3 = 45.)
- Security & auth, Miro API + MCP +28: 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.); UX Pilot MCP server 39 (OAuth or a bearer key; scopes not published (20 of 30). Organise tools never delete, and deletes need confirmation (14 of 20). Imported AI output and comments are third-party text; no injection guidance (3 of 15). No audit log (0). No security programme found (2 of 20). 20 + 14 + 3 + 0 + 2 = 39.)
- Maintenance & community, Miro API + MCP +22: 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.); UX Pilot MCP server 45 (Registry 3.0.0 and repository on 4 November 2026 (30). Dated releases not found (0). Issues not read (0). Official registry entry ai.uxpilot/uxpilot (15). README-only repository (0). 30 + 0 + 0 + 15 + 0 = 45. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.)
- Payments & pricing, Miro API + MCP +10: Miro API + MCP 30 (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.); UX Pilot MCP server 20 (No machine payment protocol (0). Pricing behind script, not read (0). Free tier (20). A person signs up (0). 0 + 0 + 20 + 0 = 20.)