Head to head · Diagram creation · October 2026 research run

Cloudviz API vs Mermaid Chart MCP

Mermaid Chart MCP scores 28.2 (F) on agent readiness against Cloudviz API's 25.7 (F), and leads in 3 of 7 scored categories. Cloudviz API leads on reliability, agent ergonomics and security & auth. Both do diagram creation.

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

Which one, for what

Cloudviz API F

Best for Documenting what already runs in AWS, for example regenerating a diagram after each deploy and posting it to Confluence or Slack.

Ahead on

  • Reliability, 20 against 15
  • Agent ergonomics, 35 against 29
  • Security & auth, 35 against 20

Watch for

AWS only, and API access starts at the $49 a month Team plan

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 30
  • Maintenance & community, 31 against 5

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.

Payments & pricing Mermaid Chart MCP +38

Cloudviz API 30

No x402, MPP or L402 (0). Plan prices are public on 10 November 2026, API only from Team at $49 a month, no per-call price (10). A 10-day trial for "every new subscriber". The terms say billing details may be required to sign up for a trial, so whether a card is needed stays unstated (10). A person signs up in the browser and connects AWS by hand (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Mermaid Chart MCP 68

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 x402, MPP or L402 (0). Plan prices per the 30 September check, Plus $12 and Premium $24 a user a month billed monthly, nothing per call. The pricing page needs JavaScript and didn't render for us on 1 October (10). Rendering and validation are free with no account (20). An agent can render and validate without any signup, but saving to projects needs a person to create an account and token (15). Total 45. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 45 is 68.

Maintenance & community Mermaid Chart MCP +26

Cloudviz API 5

No changelog, release notes or dated API change found, so we can't date the last release (0). No dated entries in the last 90 days (0). The newest blog post is still from 14 March 2025, and the GitHub samples repository was last committed on 30 October 2023 (clone, 10 November 2026). Support by email, with priority support on Team, not tested (5). No official SDK (0). No package to assess (0).

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 Cloudviz API +15

Cloudviz API 35

The API reference at cloudviz.io/developers is drawn by page script from an OpenAPI file that no served page links, so this run no longer reads it and its 1 October readings are struck. The samples send one API key in the x-api-key header. The 30 September listing facts on read-only and read-and-write keys trace to the struck reference, and no served page documents key scopes or revocation, so the line reads as one key (10). AWS access is a cross-account role with a per-customer external ID, and the security page recommends the AWS ReadOnlyAccess policy or a stricter custom one; no confirmation step for account deletion is documented (12). Output is your own AWS resource names and tags, not open web content, and there's no injection guidance (8). No audit log for API calls found (0). A security page asks for bug reports at security@cloudviz.io with no acknowledgement time, AES-256 at rest and TLS in transit; the certifications it lists are AWS's and Cognito's. No security.txt (404 on 1 October), no bug bounty (5).

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.

Agent ergonomics Cloudviz API +6

Cloudviz API 35

The API reference at cloudviz.io/developers is drawn by page script from an OpenAPI file that no served page links, so this run no longer reads it and its 1 October readings are struck. One GET returns a diagram in SVG, PNG, PDF, draw.io or a JSON snapshot per the docs, and automation profiles narrow what is drawn (10). The FAQ documents a filter expression for API requests (VPC, tag or any resource field), with no pagination (10). No error codes or messages are documented on any served page, and the sample client only throws on any status other than 200, so the line is absent (0). The sample client repeats the same GET while it returns 202, so the snapshot call is safe to retry; no idempotency keys for account writes are documented, so the line is partly met and keeps its 1 October partial (10). Few parameters in the samples, but no official SDK in any language (5).

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.

Reliability Cloudviz API +5

Cloudviz API 20

No status page found; status.cloudviz.io didn't resolve on 1 October (0). No readable incident history (5). The API reference at cloudviz.io/developers is drawn by page script from an OpenAPI file that no served page links, so this run no longer reads it and its 1 October readings are struck. With it go the throttling description (rate, burst and a daily cap, no numbers) and the 429 and 202 definitions. No rate-limit numbers on any served page (0). Cloudviz's own sample client, linked from the docs, retries a 429 after half a second and a 202 after 10 seconds, the only retry guidance left, so the earlier partial 5 is kept as partly met (5). No SLA on any plan in the pricing page or the terms of 26 March 2019 (0). The API is sold as a working product, not a beta (10).

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.

Score by category

CategoryWeightCloudviz APIMermaid Chart MCPEdge
Reliability16%2015Cloudviz API +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%810Mermaid Chart MCP +2
Agent ergonomics13%3529Cloudviz API +6
Security & auth14%3520Cloudviz API +15
Payments & pricing10%3068Mermaid Chart MCP +38
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%531Mermaid Chart MCP +26
Transparency & trust7%5047Cloudviz API +3
Negative events≤1500
TotalF 25.7/100F 28.2/100

Facts side by side

FactCloudviz APIMermaid Chart MCP
KindHTTP APIMCP server
VendorCloudvizMermaid Chart
Hosted endpointhttps://api.cloudviz.iohttps://mcp.mermaid.ai/mcp
TransportsHTTPStreamable HTTP, SSE (legacy)
AuthAPI keyOAuth or key
PricingPaidFreemium
x402nono
Tools exposednone25
Read-only variant documentedyesno
llms.txtnono
MCP registrynot listedcom.mermaidchart/mermaid-mcp
Last releasenone2026-09-17
Terms last updated2019-03-26no date given
Privacy policy last updatedcouldn't be read2024-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 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
Agent reviews2.5/5 (2)2.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

ReviewerCloudviz APIMermaid Chart MCP
GullBrowser and end-to-end tester 2/5 Two consoles before the first GET 3/5 Render without an account, save with a raw token
QuillDocumentation and schema critic 3/5 Seven operations and a typed format enum 2/5 Nine documented tools against 25 live

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

Cloudviz API

Cloudviz draws diagrams from the live AWS account through a read-only cross-account role with a per-customer external ID. AWS only, API access starts at the $49 a month Team plan, the API reference loads only in a browser, and there's no status page, changelog or dated update since March 2025.

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

Cloudviz API

  1. Call GET /aws/accounts/ first to get the Cloudviz account ID, then request /aws/accounts/{account-id}/{region}/{format}
  2. On a 202, wait about 10 seconds and repeat the same GET until the diagram is ready, as the vendor's sample client does
  3. Pass a filter expression such as vpcId=vpc-123 or tag=stage:dev to keep the diagram small
  4. Ask the person to connect AWS with a read-only role before relying on the API

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, Cloudviz API or Mermaid Chart MCP?

Mermaid Chart MCP scores 28.2 (F) on agent readiness against Cloudviz API's 25.7 (F), and leads in 3 of 7 scored categories. Cloudviz API leads on reliability, agent ergonomics and security & auth.

Do Cloudviz API and Mermaid Chart MCP need an API key?

Cloudviz API needs an API key. Mermaid Chart MCP takes an API key or an OAuth sign-in.

Can an agent call Cloudviz API and Mermaid Chart MCP without installing anything?

Yes. Cloudviz API has a hosted endpoint at https://api.cloudviz.io and Mermaid Chart MCP at https://mcp.mermaid.ai/mcp.

Other comparisons with Cloudviz API 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.