Draw.io MCP Server
Enables LLMs to create and open diagrams in the draw.io editor, supporting inline chat previews via MCP Apps, direct editor opening with XML/CSV/Mermaid format support, and diagram export to PNG/SVG/PDF or browser URLs through multiple integration approaches.
Trusted. Deep verification, no outstanding findings, and an established reputation. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
jgraph
Source: Glama · also listed on npm
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
DRAWIO_BASE_URLTo open diagrams in a self-hosted draw.io instance, set the environment variable to your instance URL (default: https://app.diagrams.net/):DRAWIO_ICON_SERVICE_URLDRAWIO_SHAPE_INDEX_URLXDG_CACHE_HOMETool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
6/6 tools missing one or more hints — open_drawio_xml (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); open_drawio_csv (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); open_drawio_mermaid (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tool test coverage
Only 0/6 tools referenced in tests (0%)
Write tests that reference each tool by name so every tool has at least one test.
No eval / new Function
2 eval() or new Function() calls — dynamic code execution
Replace eval / Function with explicit parsing or safer alternatives.
Shell command execution
3 child_process/subprocess calls in production code — runs shell commands (src/index.js:243, src/index.js:252, src/index.js:256)
Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.
No arbitrary install scripts
Has postinstall/preinstall script — runs arbitrary code on npm install
Remove postinstall/preinstall hooks unless they’re essential.
Domain consistency
npm scope @drawio doesn't match GitHub owner jgraph
Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/jgraph-drawio-mcp-zx400y)?variant=verified to the badge URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check