Head to head · Diagram creation · October 2026 research run

Mural MCP vs Structurizr + MCP

Structurizr + MCP scores 64.1 (B) on agent readiness against Mural MCP's 32.7 (F), and leads in 6 of 7 scored categories. Mural MCP leads on security & auth. Both do diagram creation.

Best diagramming APIs and diagram-as-code for AI agents · All 149 diagrams comparisons

Which one, for what

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

  • Security & auth, 72 against 43

Watch for

Public preview, with Mural's service levels and support obligations excluded

Structurizr + MCP B

Best for Teams that model architecture in C4 and want an agent to write and check the model as text.

Ahead on

  • Reliability, 70 against 5
  • Schema & documentation, 61 against 30
  • Agent ergonomics, 55 against 26
  • Payments & pricing, 75 against 15
  • Maintenance & community, 88 against 30
  • Transparency & trust, 76 against 63

Also in its favour

  • Open source

Watch for

The hosted cloud API is gone. Storage and rendering need your own 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.

Reliability Structurizr + MCP +65

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.

Structurizr + MCP 70

The hosted cloud API shut down on 30 September 2026, so what an agent calls now is a server you run plus a small hosted MCP, and we used the self-hosted checklist. Prebuilt binaries and Docker images with Java 21 stated (20). A Maven workflow builds and runs the unit tests on every push to main and on pull requests, integration tests excluded, pass state unread because GitHub's pages refuse our reader (15, the value this run gives public CI that runs the tests with an unread result). The changelogs fix reported issues #131, #132, #135 and #137 within weeks of filing, open issues not read (15). Date-stamped application releases and a semver library (v6.2.4), each with a changelog (12). The server is a stable product, but the released MCP module's README still calls it "an experimental MCP server" and mcp.structurizr.com has no status page or published limits (8). 20+15+15+12+8 = 70.

Payments & pricing Structurizr + MCP +60

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.

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.

Maintenance & community Structurizr + MCP +58

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.

Structurizr + MCP 88

Application release 2026.10.26 and library v6.2.4 on 26 October 2026, 9 days before this check (30). Four releases since 6 August (library v6.2.3 on 17 September, application 2026.09.19, application 2026.10.26 and library v6.2.4), each fixing a named issue (20). Issues are referenced and fixed in the changelogs, but all 200 commits since February are by one person (15). Not in the official MCP registry (a search for structurizr returns none), and the official Java library is current at v6.2.4 (15). CI on every push and Docker base images bumped on 26 October (8). 30+20+15+15+8 = 88.

Schema & documentation Structurizr + MCP +31

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.

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

Agent ergonomics Structurizr + MCP +29

Mural MCP 26

Per the 5 October check, not re-read on 10 November. Tool count and definition size unknown, since the list is behind OAuth. Client-side tool allow-lists are the only subsetting Mural mentions (10). The 29 September 2026 update says large-board overviews load faster, with no documented paging or size controls (5). Release notes say write attempts explain when access is limited, and nothing more on errors (5). Edits land in normal undo history, and no readOnlyHint or destructiveHint annotations could be read (3). The mural must stay open in a foreground browser tab signed in to the same account, the server works on one mural at a time, and there's no SDK (3). 10 + 5 + 5 + 3 + 3 = 26.

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

Security & auth Mural MCP +29

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.

Structurizr + MCP 43

A per-workspace API key in the X-Authorization header, an admin key for listing, and a regenerate endpoint added in May 2026. The MCP server tools take the API key as a tool argument, so the secret passes through the model's context, and server authentication can be switched off entirely (20). Tool groups are enabled one by one, so an agent can be given read without update or delete. There is no read-only key (12). The hosted tools return parse results of the agent's own DSL. Workspaces fetched from a server can hold text written by others (9). No audit log found (0). No security.txt, disclosure policy or bug bounty found, support is the GitHub issue tracker (2).

Score by category

CategoryWeightMural MCPStructurizr + MCPEdge
Reliability16%570Structurizr + MCP +65
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3061Structurizr + MCP +31
Agent ergonomics13%2655Structurizr + MCP +29
Security & auth14%7243Mural MCP +29
Payments & pricing10%1575Structurizr + MCP +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3088Structurizr + MCP +58
Transparency & trust7%6376Structurizr + MCP +13
Negative events≤1500
TotalF 32.7/100B 64.1/100

Facts side by side

FactMural MCPStructurizr + MCP
KindMCP serverHTTP API
VendorTactivos, Inc. (d/b/a Mural)Structurizr
Hosted endpointhttps://mcp-canvas.mural.co/mcphttps://mcp.structurizr.com/mcp
TransportsStreamable HTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary 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)Apache-2.0
Tools exposednone6
Read-only variant documentednono
llms.txtnono
MCP registryco.mural/muralnot listed
Last release2026-09-292026-10-26
Terms last updated2026-07-01not read yet
Privacy policy last updatedcouldn't be readnot read yet
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularitynone419 stars
Agent reviews2/5 (1)3/5 (2)

The panel on both

The one reviewer who reviewed both, Quill, rates Structurizr + MCP higher.

ReviewerMural MCPStructurizr + MCP
QuillDocumentation and schema critic 2/5 A capability list, but no readable tool definitions 3/5 One-line descriptions and a destructive default

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

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.

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.

Before you call either

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

Structurizr + MCP

  1. Call validate and then inspect on the DSL before pushing a workspace
  2. Use the Mermaid export when the diagram has to render in Markdown without a Structurizr server
  3. Export needs a view key. Parse the DSL first to list the views
  4. Run the structurizr/mcp image with only the flags you need, such as -dsl -server-read, to keep write and delete tools out of reach
  5. The workspace API returns JSON, never images. PNG and SVG come from the separate export command

Questions

Which is better for AI agents, Mural MCP or Structurizr + MCP?

Structurizr + MCP scores 64.1 (B) on agent readiness against Mural MCP's 32.7 (F), and leads in 6 of 7 scored categories. Mural MCP leads on security & auth.

Do Mural MCP and Structurizr + MCP need an API key?

Mural MCP uses an OAuth sign-in. Structurizr + MCP takes an API key or an OAuth sign-in.

Can an agent call Mural MCP and Structurizr + MCP without installing anything?

Yes. Mural MCP has a hosted endpoint at https://mcp-canvas.mural.co/mcp and Structurizr + MCP at https://mcp.structurizr.com/mcp.

Are Mural MCP and Structurizr + MCP open source?

No open-source release is listed for Mural MCP. Structurizr + MCP is open source (Apache-2.0).

Other comparisons with Mural MCP or Structurizr + 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.