Head to head · Diagram creation · October 2026 research run

Diagrams.so API + MCP vs Mermaid Chart MCP

Diagrams.so API + MCP scores 62.7 (B) on agent readiness against Mermaid Chart MCP's 28.2 (F), and leads in 6 of 7 scored categories. Mermaid Chart MCP leads on payments & pricing. 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 15
  • Schema & documentation, 85 against 10
  • Agent ergonomics, 85 against 29
  • Security & auth, 67 against 20
  • Maintenance & community, 81 against 31
  • Transparency & trust, 76 against 47

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 4.0 against 2.5 out of 5

Watch for

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

Mermaid Chart MCP F

Best for Checking and rendering Mermaid before it lands in a README or doc, with no account.

Ahead on

  • Payments & pricing, 68 against 45

Also in its favour

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

Watch for

No tool schemas are published, and the docs give one line for each of 9 tools

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.

Schema & documentation Diagrams.so API + MCP +75

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.

Mermaid Chart MCP 10

mermaid.ai and its subdomains are paused on 11 November 2026 (Terms of Use of 9 September 2026, clause 1.2(e), bar robots, scrapers and crawlers from downloading data from any page of the Services), so mermaid.ai readings are per the 1 October check, not re-read on 11 November. Closed server. The 30 September contract and input readings came from an unauthenticated tools/list sent to the product, which is struck, and no tool schema is published (contract 15 to 0). mermaid.ai/llms.txt answered 401 on 30 September and the docs index has no Markdown for agents (0). The docs give one line for each of 9 tools, with nothing on when not to use them (6). Input types and constraints unread (7 to 0, the 7 rested on the struck call). Setup examples, no documented errors (4). No changelog (0). Total 10.

Agent ergonomics Diagrams.so API + MCP +56

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.

Mermaid Chart MCP 29

mermaid.ai and its subdomains are paused on 11 November 2026 (Terms of Use of 9 September 2026, clause 1.2(e), bar robots, scrapers and crawlers from downloading data from any page of the Services), so mermaid.ai readings are per the 1 October check, not re-read on 11 November. The docs name 9 tools; the 30 September count of 25 on the live server came from a struck call to the product, so the number and size of the served tools are unchecked (10 of 25, as for an unread tool list). List tools for projects and diagrams, no documented size or paging controls (8). Errors undocumented (3). No annotations or retry guidance found (0). Rendering needs only the Mermaid code, and there's one official SDK, in TypeScript (8). Total 29.

Maintenance & community Diagrams.so API + MCP +50

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.

Mermaid Chart MCP 31

The official TypeScript SDK, @mermaidchart/sdk 0.2.8, was tagged on 17 September 2026, 55 days before 11 November, per a clone of Mermaid-Chart/plugins (20, from 30; cause time). No SDK tag since 3 July besides 0.2.7 (31 July) and 0.2.8, and no dated server changes (0). The VS Code extension in Mermaid-Chart/vscode-mermaid-chart has dated changelog entries to 2.8.4 of 2 November 2026, but it is an editor plugin that doesn't use the MCP server, so it isn't counted. No changelog for the server, support by email, not tested (5). The 1 October registry reading came from the registry's v0.1 API and is struck, and no registry page was readable (12 to 0). The SDK repository runs lint and tests in CI (6). Total 31.

Security & auth Diagrams.so API + MCP +47

Diagrams.so API + MCP 67

Bearer API keys with live and test prefixes, described in the changelog as scoped with reveal-once creation and instant revocation, a 25-active-key cap, or a device-flow login whose one-time code is emailed, never put in a URL. Which scopes exist isn't documented (28). Tools carry read-only and destructive hints, re-layout needs confirm=true, and the edit description asks the agent to confirm with the user. No read-only key type found (14). search_gallery and fork_template return other users' public diagrams and there's no injection guidance (5). Usage history lists every task and responses carry a request ID (10). security.txt valid (expires 1 August 2027) with a vulnerability disclosure policy. No bug bounty or SOC 2 (10). 28 + 14 + 5 + 10 + 10 = 67.

Mermaid Chart MCP 20

mermaid.ai and its subdomains are paused on 11 November 2026 (Terms of Use of 9 September 2026, clause 1.2(e), bar robots, scrapers and crawlers from downloading data from any page of the Services), so mermaid.ai readings are per the 1 October check, not re-read on 11 November. Per the docs, render and validation tools need no credentials. Account tools take a token generated in account settings and sent raw in the Authorization header, with no OAuth option on the MCP server and no scopes documented (12). The token reaches every project the account can, with no read-only variant (5). Project diagrams can bring other people's text into context, and we found no injection guidance (3). No audit log found (0). No security page, disclosure policy or certification found, and /.well-known/security.txt answered 401 on 30 September (0). Total 20.

Reliability Diagrams.so API + MCP +30

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.

Mermaid Chart MCP 15

mermaid.ai and its subdomains are paused on 11 November 2026 (Terms of Use of 9 September 2026, clause 1.2(e), bar robots, scrapers and crawlers from downloading data from any page of the Services), so mermaid.ai readings are per the 1 October check, not re-read on 11 November. No status page. The docs link none, and status.mermaidchart.com failed its TLS handshake on 1 October (0). No readable incident history (5). No rate limits documented (0). No 429 or retry guidance (0). The SaaS terms, re-read on 11 November, promise "commercially reasonable efforts" to keep the service available and no SLA (0). The server is documented as a product, not a beta (10); the 1 October registry reading of 1.0.0 came from the registry's v0.1 API and is struck. Total 15.

Transparency & trust Diagrams.so API + MCP +29

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.

Mermaid Chart MCP 47

mermaid.ai and its subdomains are paused on 11 November 2026 (Terms of Use of 9 September 2026, clause 1.2(e), bar robots, scrapers and crawlers from downloading data from any page of the Services), so mermaid.ai readings are per the 1 October check, not re-read on 11 November. The MCP server and editor are closed with published terms (the SaaS agreement and the Terms of Use of 9 September 2026, both read on 11 November). Mermaid itself and the SDK are MIT (15). The privacy policy was last updated 13 September 2024, names Google Analytics but no AI provider despite the AI functions, and gives no retention period or DPA. The terms keep customer content for 20 days after the term ends (10). No deprecation notices found, and the move from mermaidchart.com to mermaid.ai came with redirects but no dated notice we could find (0). Processors are described by category only, no locations (4). Total 29.

Score by category

CategoryWeightDiagrams.so API + MCPMermaid Chart MCPEdge
Reliability16%4515Diagrams.so API + MCP +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8510Diagrams.so API + MCP +75
Agent ergonomics13%8529Diagrams.so API + MCP +56
Security & auth14%6720Diagrams.so API + MCP +47
Payments & pricing10%4568Mermaid Chart MCP +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8131Diagrams.so API + MCP +50
Transparency & trust7%7647Diagrams.so API + MCP +29
Negative events≤15-50
TotalB 62.7/100F 28.2/100

Facts side by side

FactDiagrams.so API + MCPMermaid Chart MCP
KindHTTP APIMCP server
VendorDiagrams.so (RedHold LLC)Mermaid Chart
Hosted endpointhttps://api.diagrams.so/api/v2https://mcp.mermaid.ai/mcp
TransportsHTTP, stdioStreamable HTTP, SSE (legacy)
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0none
Tools exposed2325
Read-only variant documentednono
llms.txtyesno
MCP registryio.github.RedHold/diagrams-so-mcpcom.mermaidchart/mermaid-mcp
Last release2026-10-092026-09-17
Terms last updated2026-09-15no date given
Privacy policy last updated2026-09-152024-09-13
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/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Diagrams.so API + MCP higher.

ReviewerDiagrams.so API + MCPMermaid Chart MCP
QuillDocumentation and schema critic 5/5 Descriptions that state the credit cost 2/5 Nine documented tools against 25 live
GullBrowser and end-to-end tester 3/5 A code arrives by email, then it's all API 3/5 Render without an account, save with a raw token

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.

Mermaid Chart MCP

Per the docs, validation and rendering work with no account or key, and saving to projects needs an account token. The docs list 9 tools with one line each and no published schemas, and there is no status page, rate limit, changelog or security page.

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

Mermaid Chart MCP

  1. Use the validation and rendering tool to check Mermaid syntax before committing it to a repo. It needs no token
  2. Only add the token if you need to save into Mermaid Chart projects. It reaches every project on the account
  3. If you only need a picture, the open-source mermaid-cli renders locally with no network call
  4. Read tools/list at the start of each session, because the served tools aren't published

Questions

Which is better for AI agents, Diagrams.so API + MCP or Mermaid Chart MCP?

Diagrams.so API + MCP scores 62.7 (B) on agent readiness against Mermaid Chart MCP's 28.2 (F), and leads in 6 of 7 scored categories. Mermaid Chart MCP leads on payments & pricing.

Do Diagrams.so API + MCP and Mermaid Chart MCP need an API key?

Both take an API key or an OAuth sign-in.

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

Yes. Diagrams.so API + MCP has a hosted endpoint at https://api.diagrams.so/api/v2 and Mermaid Chart MCP at https://mcp.mermaid.ai/mcp.

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