drawio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRAWIO_MCP_READ_ROOTS | No | Semicolon-separated list of directories that the MCP server is allowed to read. If not set, only the project directory is accessible. | |
| DRAWIO_MCP_WRITE_ROOTS | No | Semicolon-separated list of directories that the MCP server is allowed to write to. If not set, only the project directory is accessible. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | Show allowed roots and supported workflow information. |
| create_diagramB | Create a new editable .drawio XML diagram from structured groups, nodes, and edges with automatic layout. |
| inspect_diagramA | Read the first page of a draw.io XML file and return nodes, edges, labels, and geometry. |
| validate_diagramA | Check draw.io XML structure, duplicate ids, invalid geometry, page bounds, dangling edges, and node overlaps. |
| update_diagramA | Add nodes/edges or update a node in an existing draw.io file. Writes a separate output unless overwrite is explicitly enabled. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clear and distinct role: informational, create, inspect, validate, and update. There is no meaningful overlap between the tools, and the descriptions make it easy for an agent to select the right one.
Four of the five tools follow a consistent verb_noun pattern: create_diagram, inspect_diagram, validate_diagram, and update_diagram. server_info breaks the pattern by using a noun_noun form without a verb, which is a minor deviation.
Five tools is a well-scoped size for a diagram-focused MCP server. Each tool contributes a necessary part of the workflow without unnecessary bloat or redundancy.
The core create-read-update-validate lifecycle is well covered for draw.io XML manipulation. Missing capabilities like deleting nodes/edges or inspecting more than the first page are notable but not critical gaps for common diagram workflows.