Skip to main content
isotopo-mcp exposes the agent loop as Model Context Protocol tools over stdio, so Claude Code / Claude Desktop / Cursor / any MCP client can draw isometric diagrams without shelling out to the CLI.

Install

Single static binary, no runtime deps — same as the CLI.

Register

Claude Code:
Claude Desktop / generic MCP client — add to the client’s MCP config (e.g. claude_desktop_config.json):
(Use the absolute path from which isotopo-mcp if your client doesn’t inherit $GOPATH/bin on PATH.)

Tools

The loop, MCP-shaped

  1. iso_capabilities → learn the DSL surface.
  2. Emit YAML following the positioning rules in PROMPT_TEMPLATE.md (or install the draw-iso-diagram skill, which encodes them).
  3. iso_validate → apply suggest values until issues is empty.
  4. iso_evaluate → fix layout until crossings and tunnels are 0, then act on composition.findings (balance / alignment / color) to lift composition.score toward the gallery band (≥ 0.85).
  5. iso_repair (compose: true) → apply the returned dsl — defects and off-track parts fixed in one call, comment-preserved.
  6. iso_render → read back output_dir/topology.svg.
  7. iso_snapshot → LOOK at the PNG before delivering — visual self-review catches what numbers cannot.
  8. iso_preview (optional) → crop a single node or edge to inspect it close up without re-reading the whole scene.

Protocol notes

Minimal, dependency-free implementation: JSON-RPC 2.0 over newline-delimited stdio per the MCP spec. Supported methods: initialize (echoes the client’s protocolVersion), ping, tools/list, tools/call; notifications are accepted and ignored. Resources and prompts are not implemented — the capability surface is deliberately tools-only for now.