Head to head · Diagram creation · October 2026 research run

Cloudviz API vs Mural MCP

Mural MCP scores 32.7 (F) on agent readiness against Cloudviz API's 25.7 (F), and leads in 4 of 7 scored categories. Cloudviz API leads on reliability, agent ergonomics and payments & pricing. 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 5
  • Agent ergonomics, 35 against 26
  • Payments & pricing, 30 against 15

Watch for

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

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

  • Schema & documentation, 30 against 8
  • Security & auth, 72 against 35
  • Maintenance & community, 30 against 5
  • Transparency & trust, 63 against 50

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.

Security & auth Mural MCP +37

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

Mural MCP 72

Per the 5 October check, not re-read on 10 November. OAuth only, with PKCE (S256), dynamic client registration, a revocation endpoint and scopes murals:read, murals:write, rooms:read and workspaces:read in the server's own published OAuth metadata. The assistant inherits the user's Mural permissions and there's no service account (28). A read scope exists and view-only murals stay read-only, but enablement is account-wide, and deletes run with no server-side confirmation, relying on the client's approval prompts and undo (12). Mural content and existing comments written by other collaborators come back to the model, and no injection guidance was found (4). MCP actions are recorded in the mural activity log and the audit log as the user's, marked 'with AI'. The audit log needs the Enterprise plan (13). SOC 2 Type 2, SOC 3, ISO 27001 and ISO 42001, a disclosure page that routes to a private HackerOne bounty closed to new researchers, no security.txt (15). 28 + 12 + 4 + 13 + 15 = 72.

Maintenance & community Mural MCP +25

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

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.

Schema & documentation Mural MCP +22

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

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.

Reliability Cloudviz API +15

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

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

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.

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 Mural MCP +13

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

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

CategoryWeightCloudviz APIMural MCPEdge
Reliability16%205Cloudviz API +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%830Mural MCP +22
Agent ergonomics13%3526Cloudviz API +9
Security & auth14%3572Mural MCP +37
Payments & pricing10%3015Cloudviz API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%530Mural MCP +25
Transparency & trust7%5063Mural MCP +13
Negative events≤1500
TotalF 25.7/100F 32.7/100

Facts side by side

FactCloudviz APIMural MCP
KindHTTP APIMCP server
VendorCloudvizTactivos, Inc. (d/b/a Mural)
Hosted endpointhttps://api.cloudviz.iohttps://mcp-canvas.mural.co/mcp
TransportsHTTPStreamable HTTP
AuthAPI keyOAuth
PricingPaidPaid
x402nono
LicencenoneProprietary 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)
Read-only variant documentedyesno
llms.txtnono
MCP registrynot listedco.mural/mural
Last releasenone2026-09-29
Terms last updated2019-03-262026-07-01
Privacy policy last updatedcouldn't be readcouldn'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
Agent reviews2.5/5 (2)2/5 (1)

The panel on both

The one reviewer who reviewed both, Quill, rates Cloudviz API higher, the other way from the total score.

ReviewerCloudviz APIMural MCP
QuillDocumentation and schema critic 3/5 Seven operations and a typed format enum 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

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.

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

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

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

Mural MCP scores 32.7 (F) on agent readiness against Cloudviz API's 25.7 (F), and leads in 4 of 7 scored categories. Cloudviz API leads on reliability, agent ergonomics and payments & pricing.

Do Cloudviz API and Mural MCP need an API key?

Cloudviz API needs an API key. Mural MCP uses an OAuth sign-in.

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

Yes. Cloudviz API has a hosted endpoint at https://api.cloudviz.io and Mural MCP at https://mcp-canvas.mural.co/mcp.

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