What problem does it solve? Drawing an accurate MCP server or AI tool architecture diagram is error-prone: the LLM often ends up inside the server trust boundary, auth gets collapsed into the transport node, and bearer keys or database URLs leak into the drawing. This Skill produces a validated Excalidraw architecture diagram with the correct lane separation and zero leaked secrets. ## Core Features & Use Cases - Structured MCP architecture generation: Builds four lanes β client (host + LLM, outside the trust boundary), transport (/mcp JSON-RPC), server (bearer auth -> tool registry -> services), and backend (PostgreSQL + library cache) β via the ExcaliDash MCP tools. - Quality-gated workflow: Runs a lint -> score -> repair loop until the diagram scores at least 95 with zero hard blockers, then validates architecture separation before saving and exporting. - Secret redaction: Redacts bearer tokens, database URLs, and JWT secrets before they reach any tool argument, and re-scans exports as a backstop. - Use Case: Ask to diagram your ExcaliDash MCP server and receive a saved, shareable SVG/PNG showing the host and LLM outside the trust boundary, the exd_ bearer gate as an explicit node, and storage reachable only through services. ## Quick Start Ask the AI to draw the architecture of your MCP server with transport, bearer auth, the tool registry, and PostgreSQL storage as separate nodes, keeping the LLM outside the trust boundary.