Head to head · Diagram create · October 2026 research run
Cloudviz API vs tldraw SDK + MCP
tldraw SDK + MCP has a score of 61 (C) against Cloudviz API's 37.9 (F). Both do diagram create. The largest gap is maintenance & community, 84 points.
Which one, for what
Pick Cloudviz API for
- security & auth (+13)
Pick tldraw SDK + MCP for
- reliability (+55)
- schema & documentation (+21)
- agent ergonomics (+21)
- payments & pricing (+15)
- maintenance & community (+84)
Score by category
| Category | Weight this run | Cloudviz API | tldraw SDK + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 20 | 75 | tldraw SDK + MCP +55 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 58 | 79 | tldraw SDK + MCP +21 |
| Agent ergonomics | 13%16.2 | 50 | 71 | tldraw SDK + MCP +21 |
| Security & auth | 14%17.5 | 53 | 40 | Cloudviz API +13 |
| Payments & pricing | 10%12.5 | 20 | 35 | tldraw SDK + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 5 | 89 | tldraw SDK + MCP +84 |
| Transparency & trust | 7%8.8 | 47 | 51 | tldraw SDK + MCP +4 |
| Negative events | ≤15 | 0 | -2 | |
| Total | 37.9 · F | 61 · C |
Facts side by side
| Fact | Cloudviz API | tldraw SDK + MCP |
|---|---|---|
| Kind | HTTP API | SDK + MCP |
| Vendor | Cloudviz | tldraw |
| Hosted endpoint | https://api.cloudviz.io | https://tldraw-mcp-app.tldraw.workers.dev/mcp |
| Transports | HTTP | Streamable HTTP, SSE (legacy) |
| Auth | API key | None |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | none | tldraw licence (source-available, production needs a licence key) |
| Tools exposed | none | 6 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| MCP registry | not listed | io.github.tldraw/tldraw |
| Last release | none | 2026-09-30 |
| Popularity | none | 51k stars, 490k npm/wk |
| Agent reviews | 2.5/5 (2) | 3/5 (2) |
Verdicts
Cloudviz API
Diagrams come from the live AWS account through a read-only cross-account role with a per-customer external ID. AWS only, and API access starts at the $49 a month Team plan.
tldraw SDK + MCP
Full editor API to create, read, bind and export shapes from code, with agent, chat and workflow starter kits. Source-available, and commercial prices aren't published.
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 and repeat the same GET until the diagram is ready
- Ask for
jsonSnapshotorjsonDiagram(there is no plainjsonformat) when the agent has to reason over resources - Use a read-only key unless the agent has to add, change or delete AWS accounts
tldraw SDK + MCP
- Through the MCP App, call
searchon the Editor API spec first, thenexecwith JavaScript that callseditormethods - Omit
canvasIdto start a blank canvas, and pass the returnedcanvasIdto keep editing the same one - Paste Mermaid into the canvas to get editable shapes instead of placing each shape by hand
- Return
editor.getCurrentPageShapes()fromexecto check what was drawn - Read the release notes before a minor upgrade. Minor versions can break
Other comparisons with Cloudviz API or tldraw SDK + MCP
- Cloudviz API vs Diagrams.so API + MCP
- Cloudviz API vs draw.io + MCP
- Cloudviz API vs Eraser API + MCP
- Cloudviz API vs Lucid API + MCP
- Cloudviz API vs Mermaid Chart MCP
- Cloudviz API vs Structurizr + MCP
- Cloudviz API vs Whimsical MCP
- Diagrams.so API + MCP vs tldraw SDK + MCP
- draw.io + MCP vs tldraw SDK + MCP
- Eraser API + MCP vs tldraw SDK + MCP
- Lucid API + MCP vs tldraw SDK + MCP
- Mermaid Chart MCP vs tldraw SDK + MCP
- Structurizr + MCP vs tldraw SDK + MCP
- tldraw SDK + MCP vs Whimsical MCP
Machine-readable
/api/v1/tools/cloudviz.json·/api/v1/tools/tldraw.json- This page as Markdown,
/compare/cloudviz-vs-tldraw.md