draw.io MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_sessionA | Open the current .drawio file in the locally installed Draw.io desktop app. |
| create_new_diagramB | Create a new diagram from mxGraphModel or mxfile XML, save it locally, and open it in Draw.io. |
| get_diagramA | Read the current local .drawio file XML. |
| edit_diagramA | Edit the current local .drawio file by ID-based add/update/delete operations. get_diagram is recommended but not required. |
| export_diagramB | Export the current local .drawio file. .drawio copies XML; png/svg/pdf/jpg use the local Draw.io exporter. |
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 clearly distinct purpose: creating, editing, exporting, reading, and starting a session for the diagram. No overlapping functionality.
All tool names follow a consistent verb_noun snake_case pattern (create_new_diagram, edit_diagram, export_diagram, get_diagram, start_session), making the set predictable.
With 5 tools, the set is well-scoped for a single-file diagram editor—covering creation, reading, editing (including delete), exporting, and desktop app integration.
The tool surface covers the complete lifecycle of a single .drawio file: create, read, update/delete (via edit_diagram), export, and open in desktop app. No obvious gaps.