Servidor del Model Context Protocol (MCP) que proporciona a los agentes de codificación de IA salvaguardas arquitectónicas C4 y UML de Draw.io y capacidades de conversión de diagramas.
diag2md-mcp conecta los diagramas de arquitectura de Draw.io (.xml, .drawio) con agentes de codificación de IA (como Antigravity, Cursor, Claude Desktop y clientes MCP de VS Code) al convertir diagramas C4 y UML en Markdown Mermaid estructurado en tiempo real.
Desarrollado con diag2md.
Descubrimiento automatizado del espacio de trabajo: Examina los directorios del proyecto en busca de archivos de diagramas de Draw.io que coincidan con patrones glob configurables (**/architecture/**/*.xml, **/*.drawio).
Conversión en memoria de alto rendimiento: Convierte modelos XML de Draw.io a Markdown Mermaid C4 y UML en memoria, sin la sobrecarga de crear subprocesos de shell.
Proveedor de contexto para IA (convert_diagrams_read): Lee y convierte diagramas dinámicamente para proporcionar un contexto arquitectónico enriquecido directamente a los asistentes de codificación de IA durante las sesiones de chat.
Sincronización por lotes de diagramas (convert_diagrams_write): Mantiene actualizada la documentación de arquitectura generando archivos .md junto a los archivos fuente de los diagramas.
Related MCP server: drawio-mcp
npxPuedes ejecutar el servidor MCP directamente sin necesidad de preinstalarlo:
npx -y diag2md-mcpnpm install -g diag2md-mcpPara conectar diag2md-mcp a tu asistente de IA o cliente MCP favorito, añade el servidor al archivo de configuración de tu cliente (por ejemplo, mcp_config.json, claude_desktop_config.json, Cursor o los ajustes MCP de Antigravity).
{
"mcpServers": {
"diag2md-mcp": {
"command": "diag2md-mcp"
}
}
}{
"mcpServers": {
"diag2md-mcp": {
"command": "node",
"args": ["/path/to/diag2md-mcp/dist/index.js"]
}
}
}npx{
"mcpServers": {
"diag2md-mcp": {
"command": "npx",
"args": ["-y", "diag2md-mcp"]
}
}
}diag2md-mcp expone 3 herramientas principales a los agentes de codificación de IA:
Nombre de la herramienta | Descripción | Argumentos |
| Descubre todos los archivos de diagramas de arquitectura de Draw.io ( |
|
| Escanea por lotes los archivos de diagramas del espacio de trabajo que coinciden con los patrones glob, los convierte y escribe los archivos |
|
| Escanea por lotes los archivos de diagramas del espacio de trabajo y devuelve el Markdown Mermaid convertido directamente como contexto para el asistente de IA. |
|
Los ajustes del servidor MCP se pueden personalizar mediante variables de entorno:
Variable de entorno | Descripción | Valor predeterminado |
| Patrones glob separados por comas para descubrir archivos de diagramas. |
|
| Patrones glob separados por comas que se ignorarán durante el descubrimiento de archivos. |
|
| Tipo de diagrama de conversión predeterminado ( |
|
envPuedes configurar patrones de búsqueda personalizados directamente en la configuración JSON de tu servidor MCP mediante el bloque env:
{
"mcpServers": {
"diag2md-mcp": {
"command": "diag2md-mcp",
"env": {
"DIAG2MD_PATTERNS": "**/architecture/**/*.xml, **/docs/**/*.drawio",
"DIAG2MD_IGNORE": "**/tmp/**, **/node_modules/**",
"DIAG2MD_TYPE": "c4"
}
}
}
}patternsLos asistentes de IA o las herramientas también pueden anular los patrones de búsqueda dinámicamente en cada solicitud:
{
"name": "convert_diagrams_read",
"arguments": {
"patterns": [
"**/architecture/**/*.xml",
"**/docs/**/*.drawio"
]
}
}# Clone the repository
git clone https://github.com/diag2md/diag2md-mcp.git
cd diag2md-mcp
# Install dependencies
npm install
# Build TypeScript to JavaScript dist/
npm run build
# Run unit tests
npm run test
# Run type checker
npm run typecheckBatch scan and convert all workspace diagram files (.xml, .drawio) into Mermaid Markdown, returning their content directly as AI context.
| Name | Required | Description | Default |
|---|---|---|---|
| patterns | No | Custom glob patterns to scan for diagram files | |
| diagramType | No | Diagram type: "c4" or "uml" (default: "c4") |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It usefully discloses batch behavior, file-type scope, output format, and that results are returned to the caller. However, it never explicitly states the operation is non-destructive/read-only (only the name's 'read' hints at it), and it does not warn that batch-converting 'all' workspace files could produce very large context output.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with zero filler: action and scope are front-loaded, followed by output format and return semantics. Every element earns its place, and no information is repeated from the schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with only 2 optional parameters, no output schema, and no annotations, the description supplies the core facts: what it scans, what it produces, and where the result goes. Remaining gaps — no explicit non-destructive statement, no failure/skip semantics for unparseable files, no per-file response structure — are relatively minor given the 'content directly as AI context' framing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% — both patterns and diagramType already have clear descriptions in the schema. The tool description adds only marginal context (e.g., the default 'all workspace files' behavior implied by 'Batch scan and convert all'), so the baseline 3 applies; it neither compensates for gaps nor adds meaningful parameter insight.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific action ('Batch scan and convert'), specific resources (workspace .xml/.drawio diagram files), and explicit output (Mermaid Markdown). The clause 'returning their content directly as AI context' signals a read-style operation that contrasts with the write sibling, making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied — this is the tool for getting diagram content into AI context as Mermaid — but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as convert_diagrams_write for persisting output or list_diagrams for merely enumerating files. An agent must infer selection criteria from the name and output framing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Batch scan workspace diagrams matching glob patterns and convert them to updated .md files on disk.
| Name | Required | Description | Default |
|---|---|---|---|
| patterns | No | Custom glob patterns to scan for diagram files | |
| diagramType | No | Diagram type: "c4" or "uml" (default: "c4") |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose side effects itself. It does say the tool writes/updates .md files on disk and that it scans in batch, which are important behaviors. However, it doesn't say whether existing files are overwritten, where new files land, or whether the operation is idempotent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no filler. The key constraints—batch scanning, glob patterns, and disk output—are front-loaded and every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter tool, the description covers what is scanned and what is produced, but it leaves ambiguity about overwrite behavior and doesn't clarify side effects in detail. Since no annotations or output schema exist, this gap is more significant.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds only 'workspace' and 'batch' context to the patterns parameter; the diagramType enum and default are already in the schema. No additional parameter meaning is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a concrete action ('Batch scan workspace diagrams matching glob patterns') and specifies the outcome ('convert them to updated .md files on disk'). This clearly names the resource and distinguishes it from the sibling tools by emphasizing disk writes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It doesn't explicitly state when to prefer this over convert_diagrams_read or list_diagrams. The 'Batch' and 'on disk' wording implies a write-oriented bulk use case, but there are no explicit alternatives or exclusion conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Discover all Draw.io architecture diagram files (.xml, .drawio) in the workspace using glob patterns.
| Name | Required | Description | Default |
|---|---|---|---|
| ignore | No | Custom glob patterns to ignore during search | |
| patterns | No | Custom glob patterns to search for diagram files (e.g. ["**/*.drawio"]) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Discover' implies a read-only search operation, and it specifies scope (workspace) and approach (glob patterns). However, it does not explicitly state that the tool returns a list of file paths, does not modify anything, or how defaults behave when no patterns are supplied.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single focused sentence that front-loads the purpose, resource type, file extensions, and search method. No unnecessary words or redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple listing tool with two optional parameters and full schema coverage, the description is mostly complete. It clearly communicates what files are searched and how. The main gaps are the absence of explicit return-value information and default pattern behavior, but these are minor for this type of tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and both parameters (patterns and ignore) already have meaningful descriptions. The tool description reinforces that glob patterns are involved and that .xml/.drawio files are the targets, but it does not add substantial new meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Discover'), names the resource ('Draw.io architecture diagram files'), and lists the relevant file extensions and method ('glob patterns'). This clearly distinguishes it from sibling tools like convert_diagrams_read and convert_diagrams_write, which are about conversion rather than discovery.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context: use this when you need to find Draw.io diagram files in the workspace by glob patterns. It does not explicitly mention alternatives or exclusions, but the purpose is distinct enough from the convert siblings that an agent can infer when to choose this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0convert_diagrams_readconvert_diagrams_writelist_diagramsScored across 3 tools
list_diagrams is clearly discovery-only, while the two convert tools are separated by output behavior: _write persists .md files to disk and _read returns content as AI context. There is no meaningful overlap between any pair.
All tool names follow a consistent verb_noun pattern in lowercase snake_case, using the same 'diagrams' resource. The _read/_write suffixes are a coherent way to distinguish output modes, and list_diagrams fits the pattern as an independent discovery action.
Three tools is a well-scoped set for a focused converter utility: discover source files, convert to files, and convert to context. Each tool addresses a distinct workflow step without unnecessary expansion.
The core workflow of finding Draw.io diagrams and converting them to Mermaid Markdown is fully covered in both output modes (disk and context). No obvious dead ends or missing lifecycle operations are apparent for this narrow domain.
Let Claude, Cursor, or ChatGPT author Mermaid diagrams your team can read and share.
Generate dynamic Mermaid diagrams and charts with AI assistance. Customize styles and export diagr…
Create and edit architecture diagrams from your AI agent; get an SVG and a live editable canvas.
Turn calls and notes into process flow diagrams in Claude, ChatGPT, VS Code, Cursor, and Teams.
