Head to head · Design canvases · October 2026 research run
Melius vs Miro API + MCP
Miro API + MCP scores 64 (B) on agent readiness against Melius's 54.5 (C), and leads in every scored category. Both do design canvases.
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
Melius C
Best for An agent producing batches of ad creative, product images or short videos on a shared canvas that people then review, with many models behind one key.
Also in its favour
- No incidents deducted, where Miro API + MCP loses 3 points for them
Watch for
API keys have no scopes. A key works with its creator's role in every team the creator belongs to
Best for Agents that draw diagrams, maps and planning boards people will keep editing.
Ahead on
- Schema & documentation, 85 against 70
- Security & auth, 67 against 43
- Payments & pricing, 45 against 30
- Maintenance & community, 67 against 56
- Transparency & trust, 77 against 56
Also in its favour
- Free to start without a card
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.
Security & auth Miro API + MCP +24
Melius 43
API keys are revocable at once, can expire and are shown once, but have no scopes. A key works with its creator's access in every team that user belongs to, capped at the user's role. The MCP OAuth flow uses S256 PKCE and dynamic client registration, lists no scopes, and ties the connector key to one team (22 of 30). A key made by a viewer can only read, bulk_delete_node asks the user to confirm and a run can return a pending approval, but there is no read-only key and the setup guide tells users to select Always Allow for every tool (9 of 20). Canvas text, comments from collaborators and files fetched by url_to_canvas reach the model, and no prompt-injection guidance was found (2 of 15). Keys list a lastUsedAt time, connector keys are named after the client, and generation history is kept per member. No audit log is documented (7 of 15). No security.txt, disclosure policy or bug bounty found. A Vanta trust centre exists at trust.melius.com but needs JavaScript, so certifications are unchecked (3 of 20). Per the 8 October check, not re-read on 4 November, because the terms of 30 October 2026 bar automated access to melius.com and its subdomains.
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.
Transparency & trust Miro API + MCP +21
Melius 56
Closed service under terms effective 30 October 2026, read on 4 November, which name Melius AI, Inc. and Delaware law. The CLI package is MIT with no public repository (15 of 30). The new terms (section 5.6, no training of models on user input or outputs), the privacy policy and the pricing FAQ agree that user input and outputs are not used to train models, and say third-party model providers process content under their own terms without a guarantee from Melius. Retention is described as a reasonable period with no numbers, and no DPA was found (14 of 30). Deprecated models keep working for an unstated grace period with an in-app warning. No API deprecation policy found (5 of 20). No sub-processor list or hosting location found beyond a statement that data is processed in the United States (4 of 20). The privacy policy, deprecation and sub-processor readings are per the 8 October check, not re-read on 4 November.
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.
Schema & documentation Miro API + MCP +15
Melius 70
Public OpenAPI 3.0.2 spec with 59 operations (25). llms.txt, llms-full.txt and a Markdown copy of every docs page (10). 58 of the 59 operations have a summary and no description. The MCP reference gives each of 75 tools one line, with ordering rules for get_guide, show_presence and canvas_plan_layout, and the tool definitions themselves need a signed-in client, so we didn't read them (8 of 20). Request bodies are typed with 336 enums, ranges, UUID formats and required fields, with 52 open additionalProperties objects (13 of 15). 401, 403 and 429 are declared on every operation and 400, 404 and 409 where they apply, but the spec has no examples and most error bodies are a bare message (9 of 15). The path is versioned at /api/v1 and the CLI states semantic versioning. No public changelog found (5 of 15). Per the 8 October check, not re-read on 4 November, because the terms of 30 October 2026 bar automated access to melius.com and its subdomains.
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.
Payments & pricing Miro API + MCP +15
Melius 30
No machine payment protocol (0). Plan prices and monthly credits are public, but per-model credit costs sit behind an authenticated endpoint and the top-up price is not published (10 of 20). A Free plan at $0 gives trial credits. The amount is not published and we couldn't confirm that sign-up needs no card (10 of 20). A person signs up in a browser and creates the first key in Team settings. POST /api-keys needs an existing key (0). Per the 8 October check, not re-read on 4 November, because the terms of 30 October 2026 bar automated access to melius.com and its subdomains. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
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 Miro API + MCP +11
Melius 56
The newest dated release is the CLI, 0.16.2 on 10 September 2026 per the 8 October npm reading, 55 days before this check. The vendor's Homebrew tap, whose bot tracks npm hourly, has no version after 0.16.2, and no other dated source could be read (20). Versions 0.15.0 to 0.16.2, eight in all, fall between 7 August and 10 September by the tap's bump commits, which match the 19 versions since 10 July in the 8 October npm reading (20). Closed service with no public changelog or issue tracker. Support is by email at support@melius.com and a Discord server linked from the site (5 of 15). There is no SDK library, though the CLI is on npm and Homebrew (5 of 15). The CLI has three dependencies, needs Node.js 20 and is published from GitHub Actions through npm trusted publishing. Its source is not public (6 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.
Score by category
| Category | Weight | Melius | Miro API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 69 | 73 | Miro API + MCP +4 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 70 | 85 | Miro API + MCP +15 |
| Agent ergonomics | 13% | 51 | 53 | Miro API + MCP +2 |
| Security & auth | 14% | 43 | 67 | Miro API + MCP +24 |
| Payments & pricing | 10% | 30 | 45 | Miro API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 56 | 67 | Miro API + MCP +11 |
| Transparency & trust | 7% | 56 | 77 | Miro API + MCP +21 |
| Negative events | ≤15 | 0 | -3 | |
| Total | C 54.5/100 | B 64/100 |
Facts side by side
| Fact | Melius | Miro API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Melius AI, Inc. | Miro |
| Hosted endpoint | https://api.melius.com/api/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 service under Melius's terms of service. The mel CLI on npm is MIT, with no public source repository found | proprietary |
| Tools exposed | 75 | 52 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.miroapp/mcp-server |
| Last release | 2026-09-10 | 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 | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 9 npm/wk | 156 stars, 19k npm/wk |
| Agent reviews | none | 4/5 (2) |
How the scores have moved
Verdicts
Melius
One backend serves a 59-operation REST API with a public OpenAPI spec, a hosted MCP server with OAuth sign-in and a JSON-only CLI, and the status page showed no incidents from July to early October 2026. API keys carry no scopes and work with their creator's role, and no rate-limit numbers, changelog or per-model credit prices are published.
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
Melius
- Generate by creating a node on a canvas, starting a run with POST /nodes/{nodeId}/runs, then polling GET /node-runs/{nodeRunId} until
statusis finished or failed - Over MCP, call
get_guidefirst,show_presencebefore node changes andcanvas_plan_layoutbeforebulk_create_nodes - On 429 wait
Retry-Afterseconds. After a timeout or 5xx on a write, read the canvas or run state before resubmitting, because there are no idempotency keys - Read credit costs from GET /generation/models?category=image before a bulk run. A 400 can mean the team is out of credits
- Downloads arrive as a ZIP from a signed URL. Fetch that URL without the
Authorizationheader
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, Melius or Miro API + MCP?
Miro API + MCP scores 64 (B) on agent readiness against Melius's 54.5 (C), and leads in every scored category.
Do Melius and Miro API + MCP need an API key?
Melius takes an API key or an OAuth sign-in. Miro API + MCP uses an OAuth sign-in.
Can an agent call Melius and Miro API + MCP without installing anything?
Yes. Melius has a hosted endpoint at https://api.melius.com/api/v1 and Miro API + MCP at https://api.miro.com/v2.
Other comparisons with Melius or Miro API + MCP
- ArtCraft vs Melius
- Figma API + MCP vs Melius
- Figma API + MCP vs Miro API + MCP
- Framelink MCP for Figma vs Melius
- Framelink MCP for Figma vs Miro API + MCP
- Framer Server API vs Melius
- Framer Server API vs Miro API + MCP
- Kite vs Melius
- Kite vs Miro API + MCP
- Magic Patterns vs Miro API + MCP
- Melius vs Zeplin
- 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
- Magic Patterns vs Melius
- Melius vs Paper MCP
- Melius vs pen.dev
- Melius vs Penpot API + MCP
- Melius vs Sketch
- Melius vs Subframe
- Melius vs UX Pilot MCP server
- Miro API + MCP vs UX Pilot MCP server
Machine-readable
- This page as Markdown
/compare/melius-vs-miro.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/melius.json·/api/v1/tools/miro.json - From a terminal
anchor compare melius miro(the CLI) - Over MCP
compare_tools {"a": "melius", "b": "miro"}at/mcp, no key