draw.io MCP server
3 tools · Last check that passed 27 Oct 2026, 01:50 UTC
draw.io's own remote MCP server draws diagrams from an agent's descriptions and shows them in the chat, with no sign-in. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 3 tools
| Tool | Counted as |
|---|---|
create_diagram | Changes things |
get_drawio_reference | Said to only read |
search_shapes | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
12 of the last 12 checks passed
A check passes when the server lists its tools. Checked at https://mcp.draw.io/mcp.
Recent changes
18 Oct 2026, 06:10 UTC, after a check on 16 Oct 2026, 18:18 UTC
Description rewritten on create_diagram. Inputs or outputs changed on create_diagram.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when draw.io's tools change.
One email when draw.io's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- What the agent sends to draw a diagram goes to draw.io's servers. draw.io says the server does not receive the conversation itself and does not store diagram data. draw.io's MCP server page
- Its shape search sends the search terms to draw.io's icon service, and the diagram viewer loads its code from draw.io's own sites. draw.io's MCP server README
How to limit it
With draw.io's own settings, as its documentation describes them. Stackduke has not tested them.
- To keep diagram data on your own network, run draw.io's Docker image yourself rather than the hosted server, as draw.io describes. draw.io's MCP server page
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.