drawio-impl-mermaid-conversion

Guide Mermaid-to-Draw.io conversion versus native mxGraph XML for diagram generation.

4|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/OpenAEC-Foundation/Draw.io-Claude-Skill-Package --skill drawio-impl-mermaid-conversion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drawio-impl-mermaid-conversion
Source: https://github.com/OpenAEC-Foundation/Draw.io-Claude-Skill-Package/tree/main/skills/source/drawio-impl/drawio-impl-mermaid-conversion
Command: npx skills add https://github.com/OpenAEC-Foundation/Draw.io-Claude-Skill-Package --skill drawio-impl-mermaid-conversion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Mermaid conversions in Draw.io can produce a single compound shape, making individual mxCells non-editable. This skill clarifies when to use Mermaid vs native mxGraph XML and documents the supported Mermaid types, conversion methods, and limitations to prevent incorrect diagram assumptions.

Core Features & Use Cases

  • Supports a range of Mermaid types and explains conversion options
  • Provides a decision framework for when to use Mermaid versus native Draw.io XML
  • Documents MCP tool usage and the limitations around editing after Mermaid conversion

Quick Start

Pass Mermaid content to open_drawio_mermaid to render a diagram and decide whether to continue with Mermaid or switch to native Draw.io XML for production use.

Frequently Asked Questions about drawio-impl-mermaid-conversion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Mermaid diagram convert to a single non-editable shape in Draw.io?

Mermaid conversion in Draw.io can produce a single compound shape, making individual mxCells non-editable. This happens because the conversion process groups the entire diagram rather than mapping individual elements to separate editable mxCells.

When should I use Mermaid versus native Draw.io XML for diagram generation?

Use Mermaid for rapid prototyping and supported diagram types, but switch to native Draw.io XML (mxGraph) for production diagrams requiring individual element editing. A decision framework evaluates editability needs to determine the correct approach.

How do I render Mermaid diagrams using the open_drawio_mermaid MCP tool?

Pass Mermaid content directly to the open_drawio_mermaid MCP tool to render the diagram. Validate syntax beforehand and follow safe workflow requirements to ensure the output meets production standards before deciding on final format.

What Mermaid diagram types are supported for conversion to Draw.io?

The conversion supports a specific range of Mermaid diagram types. Supported types and their conversion methods are documented to clarify which diagrams can be rendered, along with known limitations for each type during the conversion process.

What are the limitations of converting Mermaid to Draw.io mxGraph format?

Key limitations include loss of individual mxCell editability after conversion, producing compound shapes instead. The documentation outlines these constraints to prevent incorrect assumptions about post-conversion editing capabilities in production environments.

Can I edit individual elements in a Draw.io diagram after importing from Mermaid?

No, Mermaid conversion typically creates a single compound shape where individual mxCells are non-editable. For editable individual elements, use native Draw.io XML (mxGraph) instead of Mermaid conversion for the final production diagram.