Head to head · Diagram creation · October 2026 research run
Structurizr + MCP vs tldraw SDK + MCP
Structurizr + MCP scores 64.1 (B) on agent readiness against tldraw SDK + MCP's 59.3 (C), and leads in 3 of 7 scored categories. tldraw SDK + MCP leads on schema & documentation and agent ergonomics. Both do diagram creation.
Best diagramming APIs and diagram-as-code for AI agents · All 149 diagrams comparisons
Which one, for what
Best for Teams that model architecture in C4 and want an agent to write and check the model as text.
Ahead on
- Payments & pricing, 75 against 53
- Transparency & trust, 76 against 51
Also in its favour
- Open source
- No incidents deducted, where tldraw SDK + MCP loses 5 points for them
Watch for
The hosted cloud API is gone. Storage and rendering need your own server
Best for Teams building a product where a person and an agent share a canvas.
Ahead on
- Schema & documentation, 79 against 61
- Agent ergonomics, 71 against 55
Also in its favour
- No key needed to call it
Watch for
Source-available, and commercial prices aren't published
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.
Transparency & trust Structurizr + MCP +25
Structurizr + MCP 76
Apache 2.0, and the prebuilt binaries add a EULA (28). The privacy policy, updated 1 February 2026, covers only licence purchase data, keeps it for ten years after the licence ends, and says Structurizr has no access to data in your installation. The hosted MCP isn't covered (20). The end-of-life page and cloud migration guide gave dated notice, sign-ups closed 31 December 2025 and shutdown on 30 September 2026; the page was taken down on 25 October after the shutdown and stays readable in the docs repository's history (20). No telemetry mentioned in the docs or EULA, and a search of the source found no analytics or usage calls (12).
tldraw SDK + MCP 51
Source-available under the tldraw licence, explicitly not open source, with clear terms (15). The SDK runs in your app. The hosted MCP App keeps canvas checkpoints in a Durable Object SQLite store, capped by count, with exec results kept 10 minutes, none of which we found in a policy (12). RELEASES.md commits to warnings several releases before a breaking change, and v5.4 deprecated useViewportHeight() ahead of removal, though the breaking changes in v5.2.0, v5.3.0 and v5.5.0 came without earlier warnings (12). Licence pings are documented on the licence key page, but the licence page still says less than the code sends. Opting out means a commercial licence (6).
Payments & pricing Structurizr + MCP +22
Structurizr + MCP 75
Apache 2.0 code with a paid option, the licence for prebuilt binaries. No payment protocol (0). The licence table is public, £300 to £2,400 a month by unique users billed annually, bought by email and paid by bank transfer or PayPal invoice (10). Building from source is free, and a 14-day trial licence comes from trial.structurizr.com with no payment (20). The hosted MCP needs no key and the local tools need no signup (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.
tldraw SDK + MCP 53
No payment protocol (0). Commercial prices are agreed with sales, "value-based", nothing published (0). Development use needs no key, and a 100-day production trial licence is emailed on submitting a form, with no payment step (20). An agent can use the SDK in development and the hosted MCP App with no signup, but production needs a person to request a licence (15). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Schema & documentation tldraw SDK + MCP +18
Structurizr + MCP 61
OpenAPI 3.0 definition for the workspace JSON and API, and the MCP tools get typed schemas from their Java signatures (25). No llms.txt found (0). Tool descriptions are one line, such as "Validates a Structurizr DSL workspace", with the parameter described as "DSL" (6). Required flags and a numeric workspace ID, no enums (8). curl examples for each API case, errors undocumented, and tools return the raw exception message (7). Dated changelogs for the application and the library (15).
tldraw SDK + MCP 79
Full TypeScript types, and the MCP App's search tool queries an extracted Editor API spec. Both model-facing MCP tools have zod inputs (22). llms.txt per the 30 September check (10). The exec description says to call search first and gives seven worked examples (16). exec takes free-form JavaScript, which is the design but leaves nothing to validate (6). Many examples, errors come back as JavaScript exceptions (10). Dated release notes for every minor version (15).
Agent ergonomics tldraw SDK + MCP +16
Structurizr + MCP 55
Six compact tools on the hosted MCP, and the self-hosted image enables tool groups by flag (-dsl, -server-read, -server-update and so on) (25). The workspace API returns or replaces whole workspaces, and export works one view key at a time (8). Errors come back as exception text, and API errors aren't documented (8). PUT replaces a workspace and the update tool merges layout from the server copy, with lock and unlock endpoints, but the hosted tools carry Spring AI's default annotations, which mark them destructive per the 30 September check (6). Official Java client library, no second language (8).
tldraw SDK + MCP 71
Two model-facing MCP tools, with four more hidden from the model as app-only (25). search returns matching parts of the API spec instead of the whole thing, and canvases export to image or JSON (12). exec returns the thrown error text (10). All six tools carry readOnlyHint, destructiveHint and idempotentHint, search is read-only, exec isn't idempotent (16). TypeScript only, and the canvas needs a host that renders MCP Apps (8).
Score by category
| Category | Weight | Structurizr + MCP | tldraw SDK + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 70 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 61 | 79 | tldraw SDK + MCP +18 |
| Agent ergonomics | 13% | 55 | 71 | tldraw SDK + MCP +16 |
| Security & auth | 14% | 43 | 40 | Structurizr + MCP +3 |
| Payments & pricing | 10% | 75 | 53 | Structurizr + MCP +22 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 89 | tldraw SDK + MCP +1 |
| Transparency & trust | 7% | 76 | 51 | Structurizr + MCP +25 |
| Negative events | ≤15 | 0 | -5 | |
| Total | B 64.1/100 | C 59.3/100 |
Facts side by side
| Fact | Structurizr + MCP | tldraw SDK + MCP |
|---|---|---|
| Kind | HTTP API | SDK + MCP |
| Vendor | Structurizr | tldraw |
| Hosted endpoint | https://mcp.structurizr.com/mcp | https://tldraw-mcp-app.tldraw.workers.dev/mcp |
| Transports | HTTP, Streamable HTTP | Streamable HTTP, SSE (legacy) |
| Auth | OAuth or key | None |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Apache-2.0 | tldraw licence (source-available, production needs a licence key) |
| Tools exposed | 6 | 6 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | io.github.tldraw/tldraw |
| Last release | 2026-10-26 | 2026-10-28 |
| Terms last updated | not read yet | couldn't be read |
| Privacy policy last updated | not read yet | couldn't be read |
| Customer content may train models | not read yet | couldn't be read |
| Terms restrict automated access | not read yet | couldn't be read |
| Terms restrict benchmarking | not read yet | couldn't be read |
| Terms or service can change without notice | not read yet | couldn't be read |
| Arbitration or class-action waiver | not read yet | couldn't be read |
| Popularity | 419 stars | 51k stars, 490k npm/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Structurizr + MCP | tldraw SDK + MCP |
|---|---|---|
| GullBrowser and end-to-end tester | 3/5 The cloud is gone, so bring a server | 2/5 Every route out runs through a browser |
| QuillDocumentation and schema critic | 3/5 One-line descriptions and a destructive default | 4/5 Two model-facing tools and seven worked examples |
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
Structurizr + MCP
One text model generates several C4 architecture views, and the project shipped four releases between 17 September and 26 October 2026. The hosted cloud API has closed, so storage and rendering need a customer-managed server, and the free hosted MCP covers only validation, parsing and export.
tldraw SDK + MCP
Full editor API to create, read, bind and export shapes from code, with agent, chat and workflow starter kits and a hosted MCP App. Source-available, commercial prices aren't published, and monthly minor releases can break existing code without earlier warning.
Before you call either
Structurizr + MCP
- Call
validateand theninspecton the DSL before pushing a workspace - Use the Mermaid export when the diagram has to render in Markdown without a Structurizr server
- Export needs a view key. Parse the DSL first to list the views
- Run the
structurizr/mcpimage with only the flags you need, such as-dsl -server-read, to keep write and delete tools out of reach - The workspace API returns JSON, never images. PNG and SVG come from the separate export command
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
Questions
Which is better for AI agents, Structurizr + MCP or tldraw SDK + MCP?
Structurizr + MCP scores 64.1 (B) on agent readiness against tldraw SDK + MCP's 59.3 (C), and leads in 3 of 7 scored categories. tldraw SDK + MCP leads on schema & documentation and agent ergonomics.
Can an agent call Structurizr + MCP and tldraw SDK + MCP without installing anything?
Yes. Structurizr + MCP has a hosted endpoint at https://mcp.structurizr.com/mcp and tldraw SDK + MCP at https://tldraw-mcp-app.tldraw.workers.dev/mcp.
Are Structurizr + MCP and tldraw SDK + MCP open source?
Structurizr + MCP is open source (Apache-2.0). No open-source release is listed for tldraw SDK + MCP.
Other comparisons with Structurizr + MCP or tldraw SDK + MCP
- AI Diagram Maker MCP vs Structurizr + MCP
- AI Diagram Maker MCP vs tldraw SDK + MCP
- Cloudviz API vs Structurizr + MCP
- Cloudviz API vs tldraw SDK + MCP
- Diagrams.so API + MCP vs Structurizr + MCP
- Diagrams.so API + MCP vs tldraw SDK + MCP
- draw.io + MCP vs Structurizr + MCP
- draw.io + MCP vs tldraw SDK + MCP
- Eraser API + MCP vs Structurizr + MCP
- Eraser API + MCP vs tldraw SDK + MCP
- ExcaliClaw vs Structurizr + MCP
- ExcaliClaw vs tldraw SDK + MCP
- Excalidraw vs Structurizr + MCP
- Excalidraw vs tldraw SDK + MCP
- Lucid API + MCP vs Structurizr + MCP
- Lucid API + MCP vs tldraw SDK + MCP
- Mermaid Chart MCP vs Structurizr + MCP
- Mermaid Chart MCP vs tldraw SDK + MCP
- Mumble vs Structurizr + MCP
- Mumble vs tldraw SDK + MCP
- Mural MCP vs Structurizr + MCP
- Mural MCP vs tldraw SDK + MCP
- Structurizr + MCP vs Whimsical MCP
- tldraw SDK + MCP vs Whimsical MCP
- D2 vs Structurizr + MCP
- D2 vs tldraw SDK + MCP
- Kroki vs Structurizr + MCP
- Kroki vs tldraw SDK + MCP
- PlantUML vs Structurizr + MCP
- PlantUML vs tldraw SDK + MCP
Machine-readable
- This page as Markdown
/compare/structurizr-vs-tldraw.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/structurizr.json·/api/v1/tools/tldraw.json - From a terminal
anchor compare structurizr tldraw(the CLI) - Over MCP
compare_tools {"a": "structurizr", "b": "tldraw"}at/mcp, no key