Plugin · Claude Code · Development Tools

Ekusiadadus Draw Mcp

ekusiadadus draw-mcp is a Claude Code plugin for the Build phase that provides an MCP server to generate, validate, and export draw.io diagrams.

by ekusiadadus · github.com/ekusiadadus/draw-mcp

Generate and export high-quality draw.io diagrams from Claude Code via MCP with layering, arrows, and validation.

27
GitHub stars
0
Installs
0
Community votes
One vote per signed-in builder - it helps surface the tools the community actually relies on.
Install

Add it to Claude Code

Install the plugin in Claude Code. One command, paste-ready.

Install the plugin
/plugin install ekusiadadus-draw-mcp@ekusiadadus/draw-mcp
Add to ClaudeUse the Agent APISkillselion is itself an MCP server - your agent can fetch this config directly.
Agent API

Built to be called by your agent

Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.

Retrieve this entry with skillselion.get_details("plugin:ekusiadadus/draw-mcp") and the paste-ready config with skillselion.get_install_config("plugin:ekusiadadus/draw-mcp").

About

What it does

ekusiadadus-draw-mcp is a single-plugin Claude Code integration that exposes draw.io diagram generation through the Model Context Protocol. Solo builders use it when they want Claude to draft system architecture, sequence flows, or infrastructure sketches as structured diagrams instead of ASCII-only explanations in chat. The server emphasizes high-quality export, explicit layering, and validation so diagrams survive handoff to stakeholders or repositories. It fits developers documenting APIs, onboarding flows, or agent tool graphs during Build, especially when draw.io is already the team’s diagram standard. With one plugin in the bundle, setup stays minimal: register the MCP, invoke diagram tools from the agent, and iterate on arrows and layout without leaving Claude Code.

Highlights

  • MCP server that generates draw.io compatible diagrams from agent requests
  • Layering, arrows, and layout settings for readable architecture charts
  • Export pipeline for high-quality diagram files
  • Validation hooks to catch diagram structure issues before share
  • Japanese-language handling noted in catalog keywords for localized docs

Why builders use it

Builders paste messy text descriptions of architecture because the agent cannot produce editable draw.io diagrams with proper layers and arrows.

Claude creates validated draw.io diagrams you can export and drop into specs, PRDs, or repo docs in one workflow.

At a glance

  • Type - Plugin in Development Tools.
  • Adoption - 0 installs, 27 stars, 0 votes.

FAQ

Who is draw-mcp for?

Claude Code users who document backends, APIs, or agent flows in draw.io and want the model to generate and export diagrams via MCP.

When should I use draw-mcp?

Use it during Build docs work when you need architecture, sequence, or component diagrams with layering and validation before sharing.

How do I add draw-mcp to my agent?

Install the ekusiadadus/draw-mcp Claude Code plugin, configure the draw MCP server in your agent’s MCP settings, and call its diagram generate and export tools from sessions.

Discussion

Comments

Share how you use ekusiadadus-draw-mcp, gotchas, or tips for other indie builders.

No comments yet - be the first to share how you use it.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.