MCP server

Let Claude Code and other agents drive GridTree over MCP.

GridTree runs a local Model Context Protocol server that lets an MCP-aware agent — Claude Code, Gemini CLI, OpenCode, and others — read your projects, worktrees, and issues, and start and tail your apps. It's how an agent working in a GridTree terminal can act on the rest of the app.

How it works#

GridTree runs a small local server on your machine while it's open. It listens on localhost only — nothing is exposed to the network — so your agents can reach it but nothing outside your machine can.

Agents connect through a helper that GridTree bundles, rather than talking to the server directly. If you run more than one GridTree window, an agent started in a terminal automatically reaches the window it belongs to.

Set it up#

Open Settings and find your agent under the MCP / agents section. GridTree detects which agents are installed and whether each is already configured, and gives you a Setup button that registers the GridTree server for you.

• Claude Code — installing the GridTree plugin wires up the MCP server. The Setup button is the fallback if you don't use the plugin (it runs claude mcp add … gridtree … mcp).
• Gemini CLI and OpenCode — Setup writes the server into the agent's config file.
• Cursor and other clients — there's no auto-setup, so add it by hand. Point the client at the bundled gridtree binary with the mcp argument; the Manual setup block in settings shows the exact path.

Tools#

The server exposes a flat set of tools. There is no per-agent permission model — a configured agent can use all of them.