MCP

Zeo ships an MCP server that exposes every agent tool (schematic, PCB, multi-board, and component/library) to MCP-compatible clients like Claude Code, Cursor, and others.

Setup

The MCP server is part of the Zeo bundle. No separate install. To register it with an MCP client, add the following to the client's MCP config:

{
  "mcpServers": {
    "zeo": {
      "command": "zeo-mcp"
    }
  }
}

Then point your client at the running Zeo session. For Claude Code:

claude mcp add zeo zeo-mcp

What you get

Every tool documented under Agent → Tools is available through MCP. Same names, same parameters. The client calls them via standard MCP tool invocations and Zeo executes them against the live editor.

Notes

• Zeo must be running with at least one editor open before tool calls will succeed.
• After updating the kipy Python code (rare; only relevant if you've forked it), restart the MCP server in your client. C++ changes only need a Zeo rebuild.
• Some tools (e.g. launch_editor) are synchronous and block until the editor is open.