Head to head · Diagram creation · October 2026 research run

Diagrams.so API + MCP vs Mural MCP

Diagrams.so API + MCP scores 62.7 (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

Diagrams.so API + MCP B

Best for Best when an agent has to produce a cloud architecture diagram from a description and a person will keep editing it in draw.io.

Ahead on

  • Reliability, 45 against 5
  • Schema & documentation, 85 against 30
  • Agent ergonomics, 85 against 26
  • Payments & pricing, 45 against 15
  • Maintenance & community, 81 against 30
  • Transparency & trust, 76 against 63

Also in its favour

  • Runs on your own machine

Watch for

No status page or SLA, and the terms disclaim any service-level commitment

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 67

Also in its favour

  • No incidents deducted, where Diagrams.so API + MCP loses 5 points for them

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.

Agent ergonomics Diagrams.so API + MCP +59

Diagrams.so API + MCP 85

23 MCP tools in one 37 KB source file, no toolsets or read-only subset, and on the Paid plan every diagram tool returns the full draw.io XML (15). Cursor pagination on list endpoints (15). Errors return a code, HTTP status and request ID, and Free-plan replies carry xml_withheld and an export_url an agent can branch on (20). Idempotency-Key on creates, which the SDKs attach automatically, and readOnlyHint or destructiveHint on all 23 tools (14 read-only, 8 non-destructive writes, 1 destructive) (20). Only prompt is required to generate, and diagram_type may be left out. Official Python and TypeScript SDKs (15). 15 + 15 + 20 + 20 + 15 = 85.

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.

Schema & documentation Diagrams.so API + MCP +55

Diagrams.so API + MCP 85

OpenAPI 3.1 (version 2.0.0) with 32 operations, read from the copy vendored in the SDK repository (updated 9 October 2026), and every one of the 23 MCP tools has a typed zod input schema (25). llms.txt (10). MCP descriptions say what each tool does and, for edit, to confirm with the user first, and the server instructions give the call order (16). Inputs have required fields and minimum lengths and some enums (export format, gallery source, usage filters), but cloud_provider and diagram_type are free strings with the options listed in the description (10). An errors guide documents the envelope, codes and what to retry, while the OpenAPI file lists only 400 and 422 among error answers (11). Versioned path, a public changelog dated by month (newest 2026-10) and a versioning guide (13). 25 + 10 + 16 + 10 + 11 + 13 = 85.

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 Diagrams.so API + MCP +51

Diagrams.so API + MCP 81

MCP server v1.4.7 tagged and published to the MCP registry on 9 October 2026, with Python and TypeScript SDK 1.4.0 tagged the same day, 26 days ago (30). In the 90 days from 6 August, MCP tags v1.4.3 and v1.4.4 (6 August), v1.4.5 (7 August), v1.4.6 (19 August) and v1.4.7 (9 October), plus the two SDK tags at half (20). Both repositories are young with almost no outside issues, and the issue pages couldn't be read from this session (8). Listed in the official MCP registry as io.github.RedHold/diagrams-so-mcp, latest 1.4.7, under the GitHub-verified namespace (15). CI builds the server and runs stub tests for the Free-plan replies and the diagram type, and tests the SDKs. Two runtime dependencies (8). 30 + 20 + 8 + 15 + 8 = 81.

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 Diagrams.so API + MCP +40

Diagrams.so API + MCP 45

No status page yet. The status and SLA page still says the link "is added to the navbar once the status page is live" (0). No readable incident history (5). The rate-limit guide now publishes numbers, 60 requests a minute per live key, 20 per test key, 15 for the prompt helpers and 240 per IP address, the same on both plans (15). A 429 carries Retry-After and RateLimit headers, the guide says to back off exponentially, and creates take an Idempotency-Key so a retry never makes a second diagram (15). The terms say "we offer no service-level commitment" (0). /api/v2 is a public API, not a beta (10). 0 + 5 + 15 + 15 + 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.

Payments & pricing Diagrams.so API + MCP +30

Diagrams.so API + MCP 45

No x402, MPP or L402 (0). Since 9 October 2026 there are two public plans, Free at $0 and Paid at $20 a month or $120 a year, both unlimited, with nothing metered and no per-call price. Plan-only pricing that's public (10). Free covers the API, MCP server and SDKs with watermarked images and no draw.io file, marked "Start Free. No Card Required" (20). The device login still needs a person to approve an emailed code in the 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.

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.

Transparency & trust Diagrams.so API + MCP +13

Diagrams.so API + MCP 76

MCP server and SDKs are Apache 2.0, the service is closed with clear terms (20). Privacy policy effective 12 October 2026. Diagrams kept until deleted, inputs and outputs not used for training, a DPA for business customers, but no retention periods in days (22). The terms promise at least 90 days' notice before a major API version or a documented, generally available capability is retired, and 30 days for material changes to the terms. The 9 October plan change gave no such notice (it is a negative event) (18). Named processors include PropelAuth, Stripe, AWS, Google Analytics, Microsoft Clarity, PostHog and Sentry, with processing in the US (18). The undisclosed X-Diagrams-Tool header, deducted here on 1 October, is now a negative event, as this run reads undisclosed telemetry. 20 + 22 + 18 + 18 = 78.

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

CategoryWeightDiagrams.so API + MCPMural MCPEdge
Reliability16%455Diagrams.so API + MCP +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8530Diagrams.so API + MCP +55
Agent ergonomics13%8526Diagrams.so API + MCP +59
Security & auth14%6772Mural MCP +5
Payments & pricing10%4515Diagrams.so API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8130Diagrams.so API + MCP +51
Transparency & trust7%7663Diagrams.so API + MCP +13
Negative events≤15-50
TotalB 62.7/100F 32.7/100

Facts side by side

FactDiagrams.so API + MCPMural MCP
KindHTTP APIMCP server
VendorDiagrams.so (RedHold LLC)Tactivos, Inc. (d/b/a Mural)
Hosted endpointhttps://api.diagrams.so/api/v2https://mcp-canvas.mural.co/mcp
TransportsHTTP, stdioStreamable HTTP
AuthOAuth or keyOAuth
PricingFreemiumPaid
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 exposed23none
Read-only variant documentednono
llms.txtyesno
MCP registryio.github.RedHold/diagrams-so-mcpco.mural/mural
Last release2026-10-092026-09-29
Terms last updated2026-09-152026-07-01
Privacy policy last updated2026-09-15couldn'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 benchmarkingyesyes
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
Popularity0 stars, 172 npm/wk, 3 PyPI/wknone
Agent reviews4/5 (2)2/5 (1)

The panel on both

The one reviewer who reviewed both, Quill, rates Diagrams.so API + MCP higher.

ReviewerDiagrams.so API + MCPMural MCP
QuillDocumentation and schema critic 5/5 Descriptions that state the credit cost 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

Diagrams.so API + MCP

Diagrams.so turns a description into an editable draw.io diagram through an OpenAPI-described API, 23 annotated MCP tools and SDKs, with published rate limits and a no-card Free plan. It has no status page or SLA, and on 9 October it withdrew the draw.io file from Free-plan replies without the notice its terms promise.

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

Diagrams.so API + MCP

  1. On the Free plan expect xml: null. Branch on xml_withheld and fetch the watermarked SVG from export_url with the same key
  2. Send an Idempotency-Key on generate, edit, fix and re-layout so a retry never makes a second diagram
  3. Generation is synchronous and can run for minutes. The SDKs default to a 450 s timeout, or use POST /diagrams/stream
  4. Leave diagram_type out or send auto to let the service pick. cloud_provider is a free string, so call list_capabilities first
  5. relayout_diagram refuses to run without confirm=true

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, Diagrams.so API + MCP or Mural MCP?

Diagrams.so API + MCP scores 62.7 (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 Diagrams.so API + MCP and Mural MCP need an API key?

Diagrams.so API + MCP takes an API key or an OAuth sign-in. Mural MCP uses an OAuth sign-in.

Can an agent call Diagrams.so API + MCP and Mural MCP without installing anything?

Yes. Diagrams.so API + MCP has a hosted endpoint at https://api.diagrams.so/api/v2 and Mural MCP at https://mcp-canvas.mural.co/mcp.

Other comparisons with Diagrams.so API + 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.