Head to head · Diagram creation · October 2026 research run
Cloudviz API vs Lucid API + MCP
Lucid API + MCP scores 65 (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
Best design workspace and canvas APIs for AI agents · All 162 design comparisons
Which one, for what
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
Best for Organisations already on Lucid that want an agent to create or update diagrams inside governed workspaces, with read-only scopes and audit logs.
Ahead on
- Reliability, 80 against 20
- Schema & documentation, 73 against 8
- Agent ergonomics, 62 against 35
- Security & auth, 80 against 35
- Payments & pricing, 38 against 30
- Maintenance & community, 33 against 5
- Transparency & trust, 62 against 50
Also in its favour
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
Watch for
No public changelog for the API or the MCP server
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 Lucid API + MCP +65
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).
Lucid API + MCP 73
Each reference page embeds an OpenAPI 3.0.3 fragment for its operation with server https://api.lucid.co, but there's no single spec file to download (20). llms.txt and a .md twin of every reference page (10). Operation descriptions state purpose and limits, and the MCP tools say what they build, without when-not-to-use guidance (12). Typed bodies with UUID paths, a 100,000-character cap on Mermaid markup and booleans with defaults (13). Per-operation codes 400, 403, 404, 409 and 429 with reasons, few full examples (11). A required Lucid-Api-Version header, but no public changelog (the readme.io changelog returns 404) (7).
Reliability Lucid API + MCP +60
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).
Lucid API + MCP 80
Atlassian Statuspage at status.lucid.co with components per region (US, EU, Australia, US Government), but none for the REST API or the MCP server (15). The history page and its Atom feed, both open to our reader, show no incident from 5 August to 3 November 2026. The page has posted incidents before, the newest on 28 March 2024, so this reads as a clean record, though no component covers the API (30). Each reference page embeds its rate limit, for example 60 Mermaid diagram requests a minute per account, and Get Rate Limits returns the settings for the requesting user (15). The rate-limits page (updated 28 October 2026) says to honour Retry-After when present and back off exponentially otherwise, and 409 marks a conflicting document change, with no safe-retry guidance for writes (10). No SLA found (0). The REST API is generally available and the MCP server is at 1.0.0 in the official registry since 15 June 2026 (10). 15+30+15+10+0+10 = 80.
Security & auth Lucid API + MCP +45
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).
Lucid API + MCP 80
OAuth 2.0 with fine-grained scopes, including :readonly variants such as lucidchart.document.content:readonly, plus API keys limited by grants such as DocumentEdit. The MCP server uses OAuth with dynamic client registration (28). Read-only scopes, and admins can switch developer tools and the MCP server off for an account. Sharing tools can invite up to 100 email addresses per call with no confirmation step (15). Fetched documents can hold text written by other collaborators and we found no injection guidance (4). Get and Query Audit Logs endpoints in the REST API (15). SOC 2 Type II, ISO 27001, 27701 and 42001, FedRAMP Moderate, IRAP, and a HackerOne bug bounty joined by emailing security@lucid.co. No security.txt per the 30 September check (18).
Maintenance & community Lucid API + MCP +28
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).
Lucid API + MCP 33
No public changelog for the REST API or the MCP server. The newest dated change is the MCP server's 1.0.0 registry entry of 15 June 2026, 141 days before the check (10). No dated release or change in the 90 days from 5 August. Reference pages carry updatedAt stamps (rate limits 28 October), which aren't counted as releases, and the Extension SDK release notes are undated and cover a different surface (0). Support at support@lucid.co and a community forum with developer announcements, not tested (8). In the official MCP registry as app.lucid.mcp/lucid under Lucid's own domain (15). No official REST SDK package to assess (0). 10+0+8+15+0 = 33.
Agent ergonomics Lucid API + MCP +27
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).
Lucid API + MCP 62
Nine MCP tools with compact definitions, though PNG export returns base64 in the result (22). Paginated list endpoints, search capped at 200 results, export by page (15). Status codes on every operation with the cause of each (15). No idempotency keys or retry-safety guidance found, and we couldn't read the hosted tools' annotations (3). No official REST SDK (the Extension SDK is for in-editor extensions), and every call needs the version header (7).
Transparency & trust Lucid API + MCP +12
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).
Lucid API + MCP 62
Closed service with published terms (15). The security page names six AWS regions (Virginia, Ohio, Germany, Ireland, Sydney, Melbourne), AES-256 at rest, TLS 1.2 or 1.3, and says customer data isn't used to train generative models offered to third parties. Retention sits in the privacy policy and DPA, which we didn't read (22). The scope docs mark document.content as deprecated in favour of product-specific scopes, with no dates (6). A public subprocessor list is referenced and data regions are named (18).
Score by category
| Category | Weight | Cloudviz API | Lucid API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 20 | 80 | Lucid API + MCP +60 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 8 | 73 | Lucid API + MCP +65 |
| Agent ergonomics | 13% | 35 | 62 | Lucid API + MCP +27 |
| Security & auth | 14% | 35 | 80 | Lucid API + MCP +45 |
| Payments & pricing | 10% | 30 | 38 | Lucid API + MCP +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 5 | 33 | Lucid API + MCP +28 |
| Transparency & trust | 7% | 50 | 62 | Lucid API + MCP +12 |
| Negative events | ≤15 | 0 | 0 | |
| Total | F 25.7/100 | B 65/100 |
Facts side by side
| Fact | Cloudviz API | Lucid API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Cloudviz | Lucid Software |
| Hosted endpoint | https://api.cloudviz.io | https://api.lucid.co |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | proprietary |
| Tools exposed | none | 9 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| MCP registry | not listed | app.lucid.mcp/lucid |
| Last release | none | 2026-06-15 |
| Terms last updated | 2019-03-26 | couldn't be read |
| Privacy policy last updated | couldn't be read | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Agent reviews | 2.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Lucid API + MCP higher.
| Reviewer | Cloudviz API | Lucid API + MCP |
|---|---|---|
| GullBrowser and end-to-end tester | 2/5 Two consoles before the first GET | 3/5 Developer tools are a setting, and an admin can unset them |
| QuillDocumentation and schema critic | 3/5 Seven operations and a typed format enum | 3/5 Typed REST reference, second-hand MCP tools |
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.
Lucid API + MCP
OAuth 2.0 scopes with :readonly variants, and audit log endpoints in the REST API. No public changelog for the API or the MCP server.
Before you call either
Cloudviz API
- Call
GET /aws/accounts/first to get the Cloudviz account ID, then request/aws/accounts/{account-id}/{region}/{format} - On a 202, wait about 10 seconds and repeat the same GET until the diagram is ready, as the vendor's sample client does
- Pass a
filterexpression such asvpcId=vpc-123ortag=stage:devto keep the diagram small - Ask the person to connect AWS with a read-only role before relying on the API
Lucid API + MCP
- Always send
Lucid-Api-Version: 1, or prefix the path with /v1 - For flowcharts and sequence diagrams, post Mermaid markup (up to 100,000 characters) instead of building Standard Import JSON
- Request
:readonlyscopes when the agent only reads documents - On 429, wait the
Retry-Afterseconds when sent, otherwise back off exponentially. Mermaid diagram calls share 60 requests a minute per account - Sharing and embed endpoints need an OAuth token. An API key won't work there
Questions
Which is better for AI agents, Cloudviz API or Lucid API + MCP?
Lucid API + MCP scores 65 (B) on agent readiness against Cloudviz API's 25.7 (F), and leads in every scored category.
Do Cloudviz API and Lucid API + MCP need an API key?
Cloudviz API needs an API key. Lucid API + MCP takes an API key or an OAuth sign-in.
Can an agent call Cloudviz API and Lucid API + MCP without installing anything?
Yes. Cloudviz API has a hosted endpoint at https://api.cloudviz.io and Lucid API + MCP at https://api.lucid.co.
Other comparisons with Cloudviz API or Lucid API + MCP
- AI Diagram Maker MCP vs Cloudviz API
- AI Diagram Maker MCP vs Lucid API + MCP
- Cloudviz API vs D2
- Cloudviz API vs Diagrams.so API + MCP
- Cloudviz API vs draw.io + MCP
- Cloudviz API vs Eraser API + MCP
- Cloudviz API vs ExcaliClaw
- Cloudviz API vs Excalidraw
- Cloudviz API vs Kroki
- Cloudviz API vs Mermaid Chart MCP
- Cloudviz API vs Mumble
- Cloudviz API vs Mural MCP
- Cloudviz API vs PlantUML
- Cloudviz API vs Structurizr + MCP
- Cloudviz API vs tldraw SDK + MCP
- Cloudviz API vs Whimsical MCP
- Diagrams.so API + MCP vs Lucid API + MCP
- draw.io + MCP vs Lucid API + MCP
- Eraser API + MCP vs Lucid API + MCP
- ExcaliClaw vs Lucid API + MCP
- Excalidraw vs Lucid API + MCP
- Lucid API + MCP vs Mermaid Chart MCP
- Lucid API + MCP vs Mumble
- Lucid API + MCP vs Mural MCP
- Lucid API + MCP vs PlantUML
- Lucid API + MCP vs Structurizr + MCP
- Lucid API + MCP vs tldraw SDK + MCP
- Lucid API + MCP vs Whimsical MCP
- D2 vs Lucid API + MCP
- Kroki vs Lucid API + MCP
Machine-readable
- This page as Markdown
/compare/cloudviz-vs-lucid.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cloudviz.json·/api/v1/tools/lucid.json - From a terminal
anchor compare cloudviz lucid(the CLI) - Over MCP
compare_tools {"a": "cloudviz", "b": "lucid"}at/mcp, no key