Draw.io MCP Diagramming Skill

Create or update diagrams via the Draw.io MCP server. Before generating XML, read references/xml-authoring-rules.md — hard constraints, container rules, and edge routing guidance that prevent the most common rendering failures. For layout anti-pattern fixes, see references/layout-antipatterns.md. For cloud topology conventions, icon libraries, and worked examples, see references/azure.md and references/aws.md.

For diagrams that use only basic shapes (flowcharts, UML, ERD, org charts, mind maps, timelines, wireframes), skip icon discovery and proceed directly to drawio/create_diagram or drawio/open_drawio_mermaid.

When to Use

• The user asks to create or refine architecture diagrams (Azure, AWS, multi-cloud, or generic).
• The user wants draw.io/diagrams.net output from an MCP workflow.
• The user asks for Mermaid → draw.io conversion.
• The user asks for CSV → draw.io conversion (org charts, flowcharts from tabular data).
• The user needs Azure service icons in diagrams.
• The user needs AWS service icons in diagrams.
• The user reports that Azure or AWS icons/shapes are not appearing.
• The user asks for an auth or identity flow (OAuth 2.0, OIDC, JWT validation, SSO, login, token exchange, Entra, Cognito).
• The user asks for an API or microservice interaction diagram (request/response chain, service-to-service calls, API gateway flow).
• The user asks for a CI/CD pipeline or deployment workflow (build, test, deploy stages, GitHub Actions, Azure DevOps, approval gates).
• The user wants to edit an existing multi-page .drawio file (Tool Server only).