Connect your coding agent

Tomacco's command-line tool, tomaccoctl, is also an MCP server. A coding agent starts it as tomaccoctl mcp and talks to it over standard input and output. There is no network port and no token. The agent then has the same 224 operations as the desktop app.

The short way

tomaccoctl setup

Setup looks for the agents below. For each one it finds, it asks first, then adds a tomacco entry. Other servers and settings in the file stay as they were. The installer never changes an agent's settings; only tomaccoctl setup does.

What setup changes, per agent

Claude Code and Codex: setup runs their own mcp add command.
Gemini CLI: ~/.gemini/settings.json, under mcpServers.
Cursor: ~/.cursor/mcp.json, under mcpServers.
VS Code: ~/.config/Code/User/mcp.json, under servers.
Zed: ~/.config/zed/settings.json, under context_servers.
OpenCode: ~/.config/opencode/opencode.json, under mcp.

When $XDG_CONFIG_HOME is set, it takes the place of ~/.config. A file with comments, as Zed's settings often have, or a file that is a symbolic link, is left alone: setup prints the entry for you to add by hand.

By hand

claude mcp add --transport stdio --scope user tomacco -- "$(command -v tomaccoctl)" mcp
codex mcp add tomacco -- "$(command -v tomaccoctl)" mcp

Any other MCP client that can start a local stdio server works the same way: the command is the path of tomaccoctl, and the one argument is mcp. Without MCP, an agent can run tomaccoctl call OPERATION '{…}', which prints one JSON result.

Apps that drive these agents

Apps such as T3 Code start Claude Code, Codex, Cursor or OpenCode for you. Once setup has connected that agent, a session the app starts with it should have Tomacco's tools too. That follows from how T3 Code starts the agents; it has not been tried.

What has been tested

Tomacco's tests check how setup edits each settings file, in a scratch home directory: that it asks first, keeps everything else, and leaves commented files and symbolic links alone. Whether each agent then starts the server has not been checked. The Zed, VS Code and OpenCode setups were tested with stand-ins only.

The repository's agent guide covers the full contract: jobs, errors, device input and the MCP resources and prompts. To have your agent install Tomacco for you, give it tomacco.dev/agent.