What problem does it solve? Creating editable architecture, network, cloud, flowchart, ER, and C4 diagrams in draw.io requires knowing the verbose mxGraph XML format and configuring the draw.io MCP server correctly across many agent platforms, which is error-prone and time-consuming. ## Core Features & Use Cases - MCP integration: Configures the official @drawio/mcp server for Claude Desktop, Claude Code, VS Code, Cursor, OpenCode, Windsurf, Devin, and Gemini, then opens diagrams directly in the draw.io editor via open_drawio_xml, open_drawio_mermaid, and open_drawio_csv. - XML authoring rules: Provides a rigid grid layout system, semantic color palette, container/swimlane patterns, cloud icon cheatsheets (AWS, Azure, GCP), and worked XML for layered, microservices, client-API-DB, and C4-lite architectures. - Local CLI export and validation: Exports PNG/SVG/PDF via the draw.io desktop CLI, repairs truncated IEND chunks in -e PNG exports, and lints .drawio files for structural errors. - Use Case: Ask the agent to draw a 3-tier web app architecture; it authors valid mxGraph XML, calls open_drawio_xml with libavoid routing, and the diagram opens in a browser editor with no file written to disk. ## Quick Start Use the drawio-architecture skill to create an architecture diagram of my system and open it in the draw.io editor.