Draw.io MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track Draw.io integration and diagram-tool coverage as the editor changes

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

AI-assisted diagramming and visual documentation in Draw.io/diagrams.net.

What we know

An MCP server for creating, inspecting and modifying Draw.io diagrams, pages, layers and document content.

Maintenance / activity evidence

Observed Sep 14, 2026 (UTC)Merge branch & 39;agent/kreacher/50db2c42829b& 39;: fix pnpm audit failures a…

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Write access to connected diagrams. Writes: Create/edit/delete shapes/pages/layers; Save document.
No default auth documented
Sensitive access: Potentially confidential diagrams

The server can read and modify connected diagrams; protect local bridge access and use trusted documents and hosts.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

1,479 repository stars · 5.6k package downloads / 30 days

Stars observed Oct 6, 2026. Downloads observed Oct 6, 2026.

All limitations / Review context

Which Draw.io operations remain available through MCP?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

The server can read and modify connected diagrams; protect local bridge access and use trusted documents and hosts.
Write access to connected diagrams.
No default auth documented
Diagram contents are exchanged with the MCP client/editor bridge.
Reviewed write actions: Create/edit/delete shapes/pages/layers; Save document
Sensitive access: Potentially confidential diagrams
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Desktop integration is experimental.
Connected diagrams may contain confidential architecture data.

Original activity observations

2026-09-14T15:02:06Z: Merge branch & 39;agent/kreacher/50db2c42829b& 39;: fix pnpm audit failures a…

Technical identity

github.com/lgazo/drawio-mcp-server

Exact implementation source: https://github.com/lgazo/drawio-mcp-server ↗
Reviewed resource type: MCP Server
Repository identity: lgazo/drawio-mcp-server
Package identity: npm:drawio-mcp-server
Service endpoint: http://localhost:3000/

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
lgazo/drawio-mcp-server
Recorded repository material and project history.
Package registry ↗
drawio-mcp-server
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

codex

Publisher instructions with a documented client setup path.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher per-host installer: `npx drawio-mcp-server install <host>` with `<host>` one of `claude-code`, `claude-desktop`, `codex`, `zed`, `opencode`, `all`. Claude Code plugin route instead uses `/plugin marketplace add lgazo/drawio-mcp-server` and `/plugin install drawio`.
Configure / authenticate
Publisher instructions
Publisher recommends `npx drawio-mcp-server install <host>` for supported hosts. Browser extension needed for editor interaction; Claude plugin is another path.
publisher documented example · Publisher instructions · Review before use
```
npx drawio-mcp-server install codex
```
Check connection
Suggested check
Use publisher plugin `/drawio-status` if using Claude Code plugin route; confirm the intended Draw.io browser extension/connection for editing tools.
Remove / uninstall / revoke
MCP100 setup guide
For Claude Code registration named drawio; publisher plugin route instead remove plugin via `/plugin uninstall drawio`; for Codex delete generated entry from Codex config. Browser extension is separate.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
claude mcp remove drawio

Official Documentation & Sources

What it does

An MCP server for creating, inspecting and modifying Draw.io diagrams, pages, layers and document content.

Capability: Design & Creative
Resource type: MCP Server
Best fit: AI-assisted diagramming and visual documentation in Draw.io/diagrams.net.

Representative uses

Create architecture diagrams and flowcharts
Inspect shapes/pages/layers
Edit or delete diagram elements
Use cloud/vendor stencil libraries

Limitations

Desktop integration is experimental.
Connected diagrams may contain confidential architecture data.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: No default auth documented
Permissions: Write access to connected diagrams.
Data handling: Diagram contents are exchanged with the MCP client/editor bridge.
Cost: free
Risk and cautions: The server can read and modify connected diagrams; protect local bridge access and use trusted documents and hosts.

Access scope and cautions

Write actions: Create/edit/delete shapes/pages/layers Save document
Sensitive access: Potentially confidential diagrams
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Create architecture diagrams and flowcharts; Inspect shapes/pages/layers; Edit or delete diagram elements; Use cloud/vendor stencil libraries.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx drawio-mcp-server install <host>. Recorded endpoint: http://localhost:3000/. Recorded transport: stdio, websocket. Prerequisites: Node.js 22+. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No default auth documented; optional TLS/WSS.

Can it modify data or perform write operations?

Documented write actions include: Create/edit/delete shapes/pages/layers; Save document. Recorded permission boundary: Write access to connected diagrams.

What data-handling boundary should I consider?

Diagram contents are exchanged with the MCP client/editor bridge. Recorded sensitive-access context: Potentially confidential diagrams.

What limitations and risks should I check before use?

The server can read and modify connected diagrams; protect local bridge access and use trusted documents and hosts. Desktop integration is experimental. Connected diagrams may contain confidential architecture data. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

lgazo is listed as Community implementation in MCP100’s current evidence.