Draw.io MCP Server
Enables programmatic creation and management of draw.io diagrams through MCP tools. Supports building architecture diagrams, flowcharts, and visualizations with stateless operations that generate VSCode-compatible .drawio.svg files.
README
Draw.io MCP Server
A Model Context Protocol (MCP) server that provides programmatic tools for creating and managing draw.io diagrams using mxgraph. Generate architecture diagrams, flowcharts, and other visualizations through a clean API that works with Claude Desktop and other MCP-compatible clients.
Overview
This server enables you to build diagrams incrementally by providing stateless tools that operate on .drawio.svg files. Each operation specifies the target file, making it compatible with VSCode's draw.io extension while maintaining a clean separation between diagram state and server operations.
Key Features
- Stateless API: Each tool call specifies the target file path
- VSCode Compatible: Generates
.drawio.svgfiles that work seamlessly with VSCode draw.io extension - Rich Node Types: Support for rectangles, ellipses, cylinders, clouds, actors, and more
- Connection Management: Create labeled connections with various styling options
- Batch Operations: Create, update, and link multiple nodes in a single MCP call for efficient diagram building
- Flexible Positioning: Precise control over node placement and sizing
- MCP Integration: Works with Claude Desktop and other MCP-compatible applications
- TypeScript: Full type safety and IntelliSense support
Demo

Installation
Prerequisites
- Node.js 18.0.0 or higher
- npm or yarn
Configuration
MCP Client Setup
Add this configuration to your MCP client (e.g., Claude Desktop, Cursor):
{
"mcpServers": {
"drawio-diagrams": {
"command": "npx",
"args": ["drawio-mcp"]
}
}
}
File Paths
The server supports both absolute and relative file paths:
- Absolute:
/Users/username/project/diagrams/architecture.drawio.svg - Relative:
./diagrams/architecture.drawio.svg(when cwd is configured)
All diagram files should use the .drawio.svg extension for proper VSCode integration.
Tools Reference
Batch Operations
All primary tools support batch operations, allowing you to perform multiple actions in a single MCP call for improved efficiency:
add_nodes: Create multiple nodes simultaneouslyedit_nodes: Update multiple nodes/edges simultaneouslylink_nodes: Create multiple connections simultaneouslyremove_nodes: Remove multiple nodes simultaneously
This approach reduces network overhead and provides atomic operations - either all changes succeed or none are applied.
new_diagram
Create a new empty diagram file.
Parameters:
file_path(string, required): Path for the new diagram file
Example:
{
"file_path": "./diagrams/system-architecture.drawio.svg"
}
add_nodes
Add one or more nodes to an existing diagram in a single operation. Optionally run an automatic layout after insertion.
Parameters:
file_path(string, required): Path to the diagram filelayout(object, optional): Automatic layout configurationalgorithm(string, required iflayoutis provided): One ofhierarchical,circle,organic,compact-tree,radial-tree,partition,stackoptions(object, optional): Algorithm-specific options- For
hierarchicalonly:direction∈"top-down" | "left-right"(default:"top-down")
- For
nodes(array, required): Array of node objects to add, each containing:id(string, required): Unique identifier for the nodetitle(string, required): Display label (supports newlines with\n)x(number, required): X coordinate positiony(number, required): Y coordinate positionkind(string, required): Node shape typeparent(string, optional): Parent node ID (default: "root")width(number, optional): Custom widthheight(number, optional): Custom heightcorner_radius(integer, optional): Corner radius in pixels (≥ 1). Only applies toRoundedRectangle. Default is 12 whenkindisRoundedRectangleandcorner_radiusis omitted. The effective visual radius is capped by draw.io/mxGraph to at most half of the shorter side of the node.
Available Node Types:
Rectangle: Standard rectangular nodeEllipse: Oval-shaped nodeCylinder: Database/storage representationCloud: Cloud service representationSquare: Square with fixed aspect ratioCircle: Circular nodeStep: Process step shapeActor: UML actor (stick figure)Text: Text-only nodeRoundedRectangle: Rectangle with rounded corners (supportscorner_radiusin pixels)
Example (Single Node):
{
"file_path": "./diagrams/system-architecture.drawio.svg",
"nodes": [
{
"id": "user-service",
"title": "User Service\nAPI Layer",
"kind": "Rectangle",
"x": 100,
"y": 150,
"width": 120,
"height": 80
}
]
}
Example (Multiple Nodes):
{
"file_path": "./diagrams/system-architecture.drawio.svg",
"nodes": [
{
"id": "user-service",
"title": "User Service",
"kind": "Rectangle",
"x": 100,
"y": 150
},
{
"id": "database",
"title": "Primary DB",
"kind": "Cylinder",
"x": 300,
"y": 150
},
{
"id": "cache",
"title": "Redis Cache",
"kind": "Cylinder",
"x": 200,
"y": 300
}
]
}
Example (With Layout):
{
"file_path": "./diagrams/system-architecture.drawio.svg",
"layout": {
"algorithm": "hierarchical",
"options": { "direction": "left-right" }
},
"nodes": [
{ "id": "api", "title": "API", "kind": "Rectangle", "x": 40, "y": 40 },
{ "id": "service", "title": "Service", "kind": "Rectangle", "x": 200, "y": 40 },
{ "id": "db", "title": "DB", "kind": "Cylinder", "x": 360, "y": 40 }
]
}
Note: The layout runs once after all insertions and considers existing edges in the diagram file. For best results when edges are created or modified later, a dedicated layout_diagram tool is recommended (to be added).
link_nodes
Create one or more connections between existing nodes in a single operation.
Parameters:
file_path(string, required): Path to the diagram fileedges(array, required): Array of edge objects to create, each containing:from(string, required): Source node IDto(string, required): Target node IDtitle(string, optional): Connection labeldashed(boolean, optional): Whether to use dashed line stylereverse(boolean, optional): Whether to reverse arrow directionundirected(boolean, optional): Create an undirected edge (no arrows). Overridesreverse.
Example (Single Connection):
{
"file_path": "./diagrams/system-architecture.drawio.svg",
"edges": [
{
"from": "user-service",
"to": "database",
"title": "queries",
"dashed": true
}
]
}
Example (Multiple Connections):
{
"file_path": "./diagrams/system-architecture.drawio.svg",
"edges": [
{
"from": "user-service",
"to": "database",
"title": "queries"
},
{
"from": "user-service",
"to": "cache",
"title": "cache lookup",
"dashed": true
},
{
"from": "database",
"to": "cache",
"title": "invalidate",
"reverse": true
}
]
}
Example (Undirected Connection):
{
"file_path": "./diagrams/system-architecture.drawio.svg",
"edges": [
{
"from": "service-a",
"to": "service-b",
"title": "peering",
"undirected": true
}
]
}
Notes on undirected behavior:
- When
undirectedis true, the edge is rendered without arrowheads (no arrow at either end). Thereverseparameter is ignored;dashedis still respected. - Undirected edges use a canonical ID format of
${min(from,to)}-2-${max(from,to)}when a new edge is created. - If an edge between the two nodes already exists (in either direction or with the canonical ID), calling
link_nodesagain will update that existing edge’s label and style rather than creating a duplicate. The existing edge ID is preserved (no renaming).
edit_nodes
Modify properties of one or more existing nodes or edges in a single operation.
Parameters:
file_path(string, required): Path to the diagram filenodes(array, required): Array of node/edge objects to update, each containing:id(string, required): Node or edge ID to updatetitle(string, optional): New display labelkind(string, optional): New shape type (nodes only)x(number, optional): New X coordinate (nodes only)y(number, optional): New Y coordinate (nodes only)width(number, optional): New width (nodes only)height(number, optional): New height (nodes only)corner_radius(integer, optional): Corner radius in pixels (≥ 1). Applies when the node isRoundedRectangle. If switching kind toRoundedRectangleand omitted, default 12 is applied. Ignored for other kinds.
Example (Single Node):
{
"file_path": "./diagrams/system-architecture.drawio.svg",
"nodes": [
{
"id": "user-service",
"title": "Updated User Service",
"x": 200,
"y": 100
}
]
}
Example (Multiple Nodes):
{
"file_path": "./diagrams/system-architecture.drawio.svg",
"nodes": [
{
"id": "user-service",
"title": "Auth Service",
"kind": "Rectangle",
"x": 200,
"y": 100
},
{
"id": "database",
"title": "Updated Database",
"x": 400,
"y": 200
},
{
"id": "connection-1",
"title": "secure connection"
}
]
}
remove_nodes
Remove one or more nodes from a diagram.
Parameters:
file_path(string, required): Path to the diagram fileids(array, required): Array of node IDs to remove
Example:
{
"file_path": "./diagrams/system-architecture.drawio.svg",
"ids": ["old-service", "deprecated-db"]
}
get_diagram_info
Retrieve information about a diagram including nodes and connections.
Parameters:
file_path(string, required): Path to the diagram file
Example:
{
"file_path": "./diagrams/system-architecture.drawio.svg"
}
Output Format
Diagrams are saved as .drawio.svg files with embedded metadata:
- SVG Format: Clean vector graphics suitable for web and print
- Draw.io Metadata: Full diagram data embedded in SVG for editing
- VSCode Compatible: Open directly in VSCode with draw.io extension
- Self-contained: No external dependencies or additional files needed
Development
Project Structure
src/
├── Graph.ts # Core graph data structure
├── GraphFileManager.ts # File I/O operations
├── Logger.ts # Logging utilities
├── index.ts # MCP server entry point
├── mcp/ # MCP tool implementations
│ ├── McpServer.ts # Server framework
│ ├── NewDiagramTool.ts
│ ├── AddNodeTool.ts # Supports batch operations (add_nodes)
│ ├── LinkNodesTools.ts # Supports batch operations (link_nodes)
│ ├── EditNodeTool.ts # Supports batch operations (edit_nodes)
│ ├── RemoveNodesTool.ts # Supports batch operations (remove_nodes)
│ └── GetDiagramInfoTool.ts
└── mxgraph/ # mxgraph integration
├── index.ts
└── jsdom.ts
Building From Source
# Install dependencies
npm install
# Run TypeScript compilation
npm run build
# Start development server
npm start
# Run linting
npm run lint
Support
- Create an issue on GitHub for bugs and feature requests
- Check existing issues before creating new ones
- Provide detailed reproduction steps for bug reports
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.