Head to head · Diagram creation · October 2026 research run

draw.io + MCP vs Mural MCP

draw.io + MCP scores 68.2 (B) on agent readiness against Mural MCP's 32.7 (F), and leads in 6 of 7 scored categories. Mural MCP leads on security & auth. Both do diagram creation.

Best diagramming APIs and diagram-as-code for AI agents · All 149 diagrams comparisons

Which one, for what

draw.io + MCP B

Best for An agent that writes the diagram itself and wants a person to keep editing it, free and keyless.

Ahead on

  • Reliability, 45 against 5
  • Schema & documentation, 87 against 30
  • Agent ergonomics, 59 against 26
  • Payments & pricing, 90 against 15
  • Maintenance & community, 86 against 30
  • Transparency & trust, 81 against 63

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • Free to start without a card
  • Open source

Watch for

No REST API to save, list or render diagrams

Mural MCP F

Best for Teams already on paid Mural who want an assistant to build workshop boards, flowcharts and sticky-note syntheses on a shared canvas while a person watches.

Ahead on

  • Security & auth, 72 against 55

Watch for

Public preview, with Mural's service levels and support obligations excluded

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 draw.io + MCP +75

draw.io + MCP 90

Free and Apache 2.0, nothing to buy for the MCP servers or the editor, so the self-hosted rule applies. No payment protocol (0). Nothing to price (20). Free with no account or card (20). Keyless, an agent can connect with no signup (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Mural MCP 15

Per the 5 October check, not re-read on 10 November. No x402, MPP or L402 (0). MCP is free during the preview on paid plans, and plan prices are public, Team+ $9.99 and Business $17 a member a month billed yearly, nothing per call (10). The Free plan is excluded from MCP, so there's no free route (0). Signup, plan purchase and OAuth consent all need a person (0). 0 + 10 + 0 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Schema & documentation draw.io + MCP +57

draw.io + MCP 87

Both servers declare typed input schemas, JSON Schema in the npm tool server and zod in the hosted App (25). www.drawio.com/llms.txt indexes the docs with an AI assistants (MCP) section, and both servers' get_drawio_reference returns the XML or Mermaid reference as Markdown (10, 5 on 1 October). Descriptions say when to use and when not to. create_diagram tells the model to call get_drawio_reference once per format before the first diagram and search_shapes first for industry icons, and the npm open_drawio_xml says to prefer Mermaid outside stencil-based diagrams (20). Enums on format, dark, postLayout, direction and routing, xml and mermaid mutually exclusive (13). Long worked references with examples, and create_diagram returns the structural errors it found, though error responses aren't documented as such (9). Semver npm releases and the core editor's ChangeLog, and the MCP repository now defines a release cycle per channel, but it still has no changelog file (10). 25 + 10 + 20 + 13 + 9 + 10 = 87.

Mural MCP 30

Per the 5 October check, not re-read on 10 November (Mural's website terms bar robots). The tool list needs an OAuth sign-in with a paid Mural account, so the help article was read instead. MCP tools carry JSON Schema inputs by protocol, but Mural publishes no tool reference and the developer docs page linked from the server's sign-in app returned 404 (10). No llms.txt or Markdown docs. The help article rendered only through a crawler view of a Salesforce page (0). The help article lists what the server can and can't do, which tells an agent when not to use it, but no per-tool descriptions are public (6). Input types and constraints unread (5). A prompt library and a troubleshooting section, no documented error responses (4). Dated weekly release notes that mention MCP and no MCP changelog. The registry version 1.0.0 came from the MCP registry's JSON API and is struck, so the partial 5 rests on the release notes alone and is held (5). 10 + 0 + 6 + 5 + 4 + 5 = 30.

Maintenance & community draw.io + MCP +56

draw.io + MCP 86

The hosted App went to 1.4.7 on 31 October 2026 and was published to the official registry that day, @drawio/mcp went to 1.10.1 on 30 October, and core v32.6.9 was tagged the same day (30). The tool server went from 1.6.3 to 1.10.1 and the App server from 1.0.6 to 1.4.7 in October, and the core repository tagged 20 versions from v31.1.8 (7 August) to v32.6.9 (20). Commits land most days, with weekly triage fixes. The core repo doesn't take pull requests, and we couldn't read issue replies because github.com refuses our requests (15). In the official MCP registry as io.draw/mcp under the draw.io domain namespace, at 1.4.7 with mcp.draw.io as its remote (15). Description-size and tool tests exist, but run only in the manual npm publish workflow, not on every push (6). 30 + 20 + 15 + 15 + 6 = 86.

Mural MCP 30

Release notes per the 5 October check, not re-read on 10 November (Mural's website terms bar robots). The newest dated MCP change is the 29 September 2026 release-notes entry (read and write changes), 42 days before 10 November (20). The registry release of 5 October came only from the MCP registry's JSON API and is struck, which leaves two dated MCP entries since 12 August, the public preview and fixes on 8 September and the 29 September update (0). Weekly public release notes, support@mural.co routing to a technical specialist and a community site, not tested (10). Registry presence under co.mural rested only on the struck JSON reading, and no readable registry page was found (0). Closed hosted service with no package or CI to assess (0). 20 + 0 + 10 + 0 + 0 = 30.

Reliability draw.io + MCP +40

draw.io + MCP 45

Better Stack status page at status.draw.io with 30, 60 and 90-day bars for app.diagrams.net and the Atlassian apps, but mcp.draw.io isn't one of the monitored components (15). Every bar reads 100 per cent bar one 99.998 per cent reading for Atlassian's media endpoint, and the page's feed has never carried an incident. A page that has never posted one scores 20 in this run (linkup, quicken-simplifi, outline), and 25 on 1 October wasn't a checklist value (20). No rate limits published, and none found in the hosted server's source (0). No 429 or retry guidance (0). No SLA found (0). The hosted MCP App (1.4.7) and @drawio/mcp (1.10.1) are released, not preview (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.

Mural MCP 5

Mural's Website Terms of Use (last revised 12 December 2023) bar robots, scraping and data mining on the websites that link to them, including mural.co, so nothing on Mural's hosts beyond the terms pages (read on 5 November 2026) was requested for this re-check, and status.mural.co, on Mural's own domain, falls under the same bar. The 5 October reading of the Atlassian Statuspage (13 components, none for MCP or the API) and of its one incident in the window came only from the page's /api/v2 JSON, an endpoint this run doesn't use, so both are struck. Status page with component history (0). Incident record unread (5). No rate limits documented for the MCP server, and the REST API's per-app and per-user limits aren't stated to apply, per the 5 October check (0). No 429 or retry guidance for MCP (0). The preview disclaimer says Mural's service levels don't apply (0). Public preview, not generally available (0). 0 + 5 + 0 + 0 + 0 + 0 = 5.

Agent ergonomics draw.io + MCP +33

draw.io + MCP 59

Since 12 October the hosted App serves the references from a tool instead of appending them to create_diagram. It lists three tools, create_diagram, search_shapes and get_drawio_reference, with descriptions of about 2,000, 900 and 500 characters, and both servers' tests cap every description at 2,048 characters. The parameter descriptions are not capped. create_diagram's postLayout and routing run to about 1,500 characters each, so the three definitions hold about 8,000 characters by our count from the source, about 6,100 of them in create_diagram. Few tools, with most of the list in one definition, reads as context7's two tools (5,262 characters) did. The npm server has eight tools (20 of 25, 10 on 1 October). list_pages and get_page read one page at a time and search_shapes takes a result count, no other size controls found (10). Error responses aren't documented (5). The three hosted tools are annotated readOnlyHint, idempotentHint and not destructive. The npm server's eight tools carry no annotations (14). One required parameter per tool with stated defaults, no SDK (10). 20 + 10 + 5 + 14 + 10 = 59.

Mural MCP 26

Per the 5 October check, not re-read on 10 November. Tool count and definition size unknown, since the list is behind OAuth. Client-side tool allow-lists are the only subsetting Mural mentions (10). The 29 September 2026 update says large-board overviews load faster, with no documented paging or size controls (5). Release notes say write attempts explain when access is limited, and nothing more on errors (5). Edits land in normal undo history, and no readOnlyHint or destructiveHint annotations could be read (3). The mural must stay open in a foreground browser tab signed in to the same account, the server works on one mural at a time, and there's no SDK (3). 10 + 5 + 5 + 3 + 3 = 26.

Transparency & trust draw.io + MCP +18

draw.io + MCP 81

Apache 2.0 (30). The privacy policy, v2.3.1 of 18 October 2026, says diagrams are processed and not kept, sets retention for logs (30 days) and user counts (24 months), and lists where data goes. A separate policy for the hosted MCP server (v1.1, 13 October 2026) says diagrams and requests aren't stored or logged, gives retention per item and names Cloudflare and Google Cloud as sub-processors. The two agree, and the 2023 policy's UK-only statement is gone. Neither policy publishes a DPA or says one is available, so the line sits with pen-dev (24) and pushary (25), whose retention tables and sub-processor lists come with a DPA on request (24, 15 on 1 October). No deprecation policy found, though the core ChangeLog records changes such as the Dropbox removal in 32.5.1 (3). Providers and data locations are listed in both policies, with Cloudflare processing in the data centre nearest the caller, which may be outside the UK. We found no telemetry in the MCP tool definitions (18, 10 on 1 October). 30 + 24 + 3 + 18 = 75.

Mural MCP 63

Per the 5 October check, except the terms, re-read on 5 November. Closed service with published terms (Services Agreement effective 1 July 2026), which the preview disclaimer limits by excluding service levels, support and indemnities (15). The help article says the server stores no mural content, keeps OAuth tokens, registration records and session state in Redis, and that customer content isn't used for training. It also says token keys have no TTL and that revocation and retention still need a documented policy, and the privacy statement's body didn't render on 5 October (18). No deprecation policy. The preview may change or end at any time without notice (0). A public subprocessor list with locations, mostly the US, and US hosting on Microsoft Azure by default with workspace-level data residency on Enterprise (18). 15 + 18 + 0 + 18 = 51.

Score by category

CategoryWeightdraw.io + MCPMural MCPEdge
Reliability16%455draw.io + MCP +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8730draw.io + MCP +57
Agent ergonomics13%5926draw.io + MCP +33
Security & auth14%5572Mural MCP +17
Payments & pricing10%9015draw.io + MCP +75
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8630draw.io + MCP +56
Transparency & trust7%8163draw.io + MCP +18
Negative events≤1500
TotalB 68.2/100F 32.7/100

Facts side by side

Factdraw.io + MCPMural MCP
KindMCP serverMCP server
Vendordraw.ioTactivos, Inc. (d/b/a Mural)
Hosted endpointhttps://mcp.draw.io/mcphttps://mcp-canvas.mural.co/mcp
TransportsStreamable HTTP, stdioStreamable HTTP
AuthNoneOAuth
PricingFreePaid
x402nono
LicenceApache-2.0Proprietary hosted service under Mural's Terms of Service. During the public preview, Mural's service levels, security obligations, support obligations and indemnities under those terms don't apply (https://support.mural.co/s/article/MCP-preview)
Tools exposed3none
Read-only variant documentednono
llms.txtyesno
MCP registryio.draw/mcpco.mural/mural
Last release2026-10-312026-09-29
Terms last updatedno date given2026-07-01
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity8.5k stars, 25k npm/wknone
Agent reviews4/5 (2)2/5 (1)

The panel on both

The one reviewer who reviewed both, Quill, rates draw.io + MCP higher.

Reviewerdraw.io + MCPMural MCP
QuillDocumentation and schema critic 4/5 13,000 tokens for one well-written tool 2/5 A capability list, but no readable tool definitions

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

draw.io + MCP

Free, keyless and Apache 2.0. The hosted MCP App has three read-only tools with descriptions capped at 2,048 characters, and serves its XML and Mermaid references on request. A privacy policy for the MCP server says diagrams aren't stored. No rate limits, SLA or status monitor cover mcp.draw.io, and the npm server's eight tools carry no annotations.

Mural MCP

Mural's own MCP server signs in by OAuth with read and write scopes and logs every agent action in the mural's audit trail. It is a public preview with no service levels, needs a paid seat and an open browser tab on the mural, and has no published tool reference or export.

Before you call either

draw.io + MCP

  1. Call get_drawio_reference once per format before the first diagram, then pass mermaid to create_diagram for any type on its Mermaid list. Use xml for icons, mockups or hand-placed layouts
  2. Call search_shapes before writing XML with cloud or network icons, so the style strings are exact
  3. Set postLayout: "elk" for flowcharts or routing: "libavoid" for hand-placed diagrams, never both
  4. Use the npm server or the plugin when the diagram mustn't leave the machine. The hosted App sends it to draw.io's server, which doesn't store it
  5. Expect each reference to cost thousands of tokens when fetched. Fetch only the format you will use

Mural MCP

  1. Ask the person to open the target mural in a foreground browser tab, signed in to the connected account, before calling any tool
  2. Work on one mural at a time and name it explicitly when switching
  3. Request only murals:read when the task only reads a board
  4. Deletes go through without a server-side prompt. Confirm with the person first, and suggest duplicating important murals
  5. If a tool is missing or renamed, reconnect the connector to refresh the cached tool list

Questions

Which is better for AI agents, draw.io + MCP or Mural MCP?

draw.io + MCP scores 68.2 (B) on agent readiness against Mural MCP's 32.7 (F), and leads in 6 of 7 scored categories. Mural MCP leads on security & auth.

Do draw.io + MCP and Mural MCP need an API key?

draw.io + MCP needs no key. Mural MCP uses an OAuth sign-in.

Can an agent call draw.io + MCP and Mural MCP without installing anything?

Yes. draw.io + MCP has a hosted endpoint at https://mcp.draw.io/mcp and Mural MCP at https://mcp-canvas.mural.co/mcp.

Are draw.io + MCP and Mural MCP open source?

draw.io + MCP is open source (Apache-2.0). No open-source release is listed for Mural MCP.

Other comparisons with draw.io + MCP or Mural 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.