M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
D

Draw.io MCP Server

Community
Let AI create and edit Draw.io diagrams directly.
How to install ↓ Compare GitHub source repository ↗
Category
Other #131 of 230
Stars
★ 1.5k Very popular
Transport
stdio (local process)
Runtime
Node.js 22+
Credentials
No credential needed
License
MIT
Last commit
Tools
6
52FMRS · D

This is a community-maintained Draw.io MCP Server that runs locally through stdio. The README provides configuration examples for several MCP clients, diagram-editing capabilities, document and page targeting, and built-in-editor and browser-extension modes. Because no complete tool manifest is provided, the tools field includes only identifiers explicitly named in the README.

Strongest · Setup experience 14/20 Weakest · Security and permissions 7/20

Reliability
8/20
Security and permissions
7/20
Maintenance
10/20
Documentation
13/20
Setup experience
14/20
Why each score
Reliability 8/20
The README describes the MCP server, editor mode, browser extension, and multiple tool capabilities, and states runtime and launch requirements. However, no server manifest, source code, tests, or actual CI workflow contents are provided, so initialization, tool-list consistency, error handling, and key-path behavior cannot be verified statically. The score is conservatively reduced and remains within the static-review cap of 12.
Security and permissions 7/20
The README indicates that the server can create, modify, and delete diagram elements and can connect through a built-in editor, browser extension, and optional TLS. It does not document authentication, access control, data boundaries, external network behavior, or confirmation requirements for deletion. No explicit credential theft, covert exfiltration, or other red-line behavior is shown, but permissions and data-flow evidence are incomplete, warranting substantial deductions.
Maintenance 10/20
The repository is reported as not archived, uses the MIT license, and displays CI, npm version, and MSeeP assessment badges. These are primarily README claims; no commit history, release cadence, dependency-update process, maintainer identity, or security-response channel is supplied. There are some maintenance signals, but sustained ownership and governance are not sufficiently evidenced.
Documentation 13/20
The README covers capabilities, Node.js requirements, configuration examples for several mainstream MCP clients, built-in editor and browser-extension setup, and links to configuration, tool reference, troubleshooting, and architecture documentation. It also discloses the experimental desktop limitation and TLS option. However, the linked documents are not included, and reviewable evidence for tool parameters, authentication, limits, cost, and troubleshooting is incomplete.
Setup experience 14/20
The README provides concrete npx configurations from a Node.js environment for Claude Desktop, Claude Code, Zed, Codex, and OpenCode, plus a local editor URL and browser-extension alternative. However, there is no manifest or executable verification evidence, and the Node.js 22+ requirement, extension installation, and TLS scenarios add environment complexity, so full marks are not justified.

Static review · not runListed 2026-07-29

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkControls a browser

Best for

  • Teams that want AI to generate or maintain Draw.io diagrams
  • Users of Claude Desktop, Claude Code, Zed, Codex, or OpenCode
  • Diagram workflows requiring multi-document, multi-page, and vendor-stencil support

Not for

  • Text-only workflows with no diagram-editing requirement
  • Users requiring a stable end-to-end Draw.io Desktop integration
  • Users unwilling to install Node.js or a browser extension

Required permissions

  • Access to connected Draw.io document instances and diagram contents
  • Permission to create, modify, and delete elements in target diagrams
  • In browser-extension mode, a connection to the Draw.io browser page and extension

Risks and side effects

  • AI actions can modify or delete diagram elements, so mistakes may damage diagram content
  • Browser-extension mode depends on connectivity between the extension and the Draw.io page
  • Self-signed TLS certificates may require browser trust and connection configuration
  • Draw.io Desktop integration is experimental and limited by an upstream CSP issue

Setup

Before you start

Runtime：Node.js 22+

Add the JSON from install_config to a supported MCP client configuration, restart the client, and open http://localhost:3000/. Node.js 22 or newer is required. Browser-extension usage additionally requires the extension and Draw.io open in a browser.

claude_desktop_config.json 
{"mcpServers":{"drawio":{"command":"npx","args":["-y","drawio-mcp-server","--editor"]}}}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "drawio": {
      "command": "npx",
      "args": [
        "-y",
        "drawio-mcp-server",
        "--editor"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add drawio -- npx -y drawio-mcp-server --editor

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After restarting the MCP client, check that the drawio server's tools (list-documents, list-pages, get-current-page, create-page, copy-page, rename-page) appear in the tool list, then open http://localhost:3000/ and ask the assistant to call list-pages to inspect the current diagram.

Troubleshooting

  1. Verify that Node.js 22 or newer is installed
  2. Restart the MCP client and confirm that the configuration loads
  3. For the built-in editor, check whether http://localhost:3000/ is reachable
  4. For browser-extension mode, confirm the extension is installed, Draw.io is open, and the connection indicator is green
  5. For Firefox, ensure TLS mode is enabled
  6. For Draw.io Desktop connection failures, check the documented upstream CSP limitation

Things to try

Once connected, you can ask your AI assistant things like:

  • Create an event-driven architecture diagram showing a message queue with producers, consumers, and three backend services
  • Create a three-page event-driven architecture diagram using three agents in parallel for service topology, message flow, and retry/failure handling, each assigned to a separate target page
  • Draw a CRUD API diagram with a database, API gateway, and four microservices with their endpoints
  • Add a new layer called 'Background', move all decorative elements to it, then create a new layer for annotations

Tools 6

list-documents read-only
Lists connected Draw.io document instances for target selection.
list-pages read-only
Lists pages in the target document.
get-current-page read-only
Retrieves information about the current page.
create-page writes
Creates a new page.
copy-page writes
Copies a page.
rename-page writes
Renames a page.

Use cases

Automatically create architecture diagrams, flowcharts, and visual documentation
Inspect, modify, and organize multi-page Draw.io diagrams
Import, embed, or expand Mermaid diagrams
Manage layers, pages, and nested shapes

Supported clients

Claude Desktop
Claude Code
Zed
Codex
OpenCode

Listed from the project's documentation, not tested by this site.

Overview

Draw.io MCP Server gives AI assistants control over Draw.io (Diagrams.net) diagrams, including inspection and modification of shapes, edges, pages, and layers through a built-in editor or browser extension.

Similar servers

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 659 · Tools 11 Compare with this →
Compare with other MCP servers

Source revision d2f7c32fa916 Data synced 2026-10-19 Read the FMRS scoring method