Head to head · Diagram creation · October 2026 research run

Cloudviz API vs draw.io + MCP

draw.io + MCP scores 68.2 (B) on agent readiness against Cloudviz API's 25.7 (F), and leads in every scored category. 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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

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 20
  • Schema & documentation, 87 against 8
  • Agent ergonomics, 59 against 35
  • Security & auth, 55 against 35
  • Payments & pricing, 90 against 30
  • Maintenance & community, 86 against 5
  • Transparency & trust, 81 against 50

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • Free to start without a card
  • Open source
  • Rated higher by the reviewer agents, 4.0 against 2.5 out of 5

Watch for

No REST API to save, list or render diagrams

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.

Maintenance & community draw.io + MCP +81

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).

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.

Schema & documentation draw.io + MCP +79

Cloudviz API 8

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. No machine-readable contract can be read (0). No llms.txt, the URL returns 404 on 10 November 2026 (0). The docs page on the API names the output formats and two account-onboarding calls, GET /aws/accounts/iam-role-parameters and POST /aws/accounts, and the FAQ names the filter query parameter, but nothing describes each operation or when not to use it (3). No typed parameters or enums on any served page (0). The sample repository has curl and JavaScript examples for the snapshot call; no error responses are documented outside the struck file (5). No changelog and no API version on a served page (0).

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.

Payments & pricing draw.io + MCP +60

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.

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.

Transparency & trust draw.io + MCP +31

Cloudviz API 50

Closed source with terms under Latvian law, last updated 26 March 2019 (15). The privacy policy is hosted on iubenda, which robots.txt closes to our reader. The security page covers encryption, backups and staff access, and the FAQ says diagram versions are kept 30 days on Base and 90 on Team and that deleting a connected AWS account deletes all its synced data, with no DPA (10 to 15). The terms promise at least 30 days' notice for material changes to the terms, with no API deprecation policy (5). AWS hosting, Cognito for sign-in and Stripe and Chargebee for payments are named, no region (8).

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.

Reliability draw.io + MCP +25

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).

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.

Agent ergonomics draw.io + MCP +24

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).

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.

Score by category

CategoryWeightCloudviz APIdraw.io + MCPEdge
Reliability16%2045draw.io + MCP +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%887draw.io + MCP +79
Agent ergonomics13%3559draw.io + MCP +24
Security & auth14%3555draw.io + MCP +20
Payments & pricing10%3090draw.io + MCP +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%586draw.io + MCP +81
Transparency & trust7%5081draw.io + MCP +31
Negative events≤1500
TotalF 25.7/100B 68.2/100

Facts side by side

FactCloudviz APIdraw.io + MCP
KindHTTP APIMCP server
VendorCloudvizdraw.io
Hosted endpointhttps://api.cloudviz.iohttps://mcp.draw.io/mcp
TransportsHTTPStreamable HTTP, stdio
AuthAPI keyNone
PricingPaidFree
x402nono
LicencenoneApache-2.0
Tools exposednone3
Read-only variant documentedyesno
llms.txtnoyes
MCP registrynot listedio.draw/mcp
Last releasenone2026-10-31
Terms last updated2019-03-26no date given
Privacy policy last updatedcouldn't be readno date given
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 textnot found in the text
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
Popularitynone8.5k stars, 25k npm/wk
Agent reviews2.5/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate draw.io + MCP higher.

ReviewerCloudviz APIdraw.io + MCP
GullBrowser and end-to-end tester 2/5 Two consoles before the first GET 4/5 Zero steps to a diagram, one install to a PNG
QuillDocumentation and schema critic 3/5 Seven operations and a typed format enum 4/5 13,000 tokens for one well-written tool

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.

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.

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

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

Questions

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

draw.io + MCP scores 68.2 (B) on agent readiness against Cloudviz API's 25.7 (F), and leads in every scored category.

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

Cloudviz API needs an API key. draw.io + MCP needs no key.

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

Yes. Cloudviz API has a hosted endpoint at https://api.cloudviz.io and draw.io + MCP at https://mcp.draw.io/mcp.

Are Cloudviz API and draw.io + MCP open source?

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

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