Every AI app reaches ToolPiper the same way: through the MCP server built into
the app, at http://127.0.0.1:9998/mcp on your Mac. Claude Desktop connects
with a one-click extension, and Claude Code and Codex each install a plugin or
take one command. Homebrew installs ToolPiper itself. None of
them needs an account or a pasted token, and ToolPiper has to be running for any
of them to see its tools.
Claude Desktop
Download the extension, a .mcpb file, from
modelpiper.com/download or the
releases page, and
double-click it. Claude Desktop opens its install sheet with the tool list;
click Install.
You can also drag the file onto the Claude Desktop window, or use Settings,
Extensions, Advanced settings, Install extension.
The extension needs ToolPiper 0.0.10-beta or later. It serves ToolPiper's tools minus the ones that generate images, video or audio with an AI model.
Claude Desktop's own claude_desktop_config.json only starts local programs, so
an HTTP server entry pasted there does nothing. The extension is the way in.
If ToolPiper is not running, Claude sees a single status tool and tells you to open ToolPiper. The full tool list appears by itself once the app starts.
Claude Code
Install the plugin, and the MCP server is configured for you:
claude plugin marketplace add ModelPiper/toolpiper
claude plugin install toolpiper@modelpiper
The plugin serves the same set as the Claude Desktop extension and adds a setup skill that checks ToolPiper is installed, running and listening. For the full catalog, add the server by hand instead:
claude mcp add --transport http toolpiper http://127.0.0.1:9998/mcp
When both exist, Claude Code uses the server you added by hand.
Codex
Install the plugin from ToolPiper's marketplace:
codex plugin marketplace add ModelPiper/toolpiper
codex plugin add toolpiper@modelpiper
The plugin serves the full catalog and adds the same setup skill. To add the server by hand instead:
codex mcp add toolpiper --url http://127.0.0.1:9998/mcp
That writes [mcp_servers.toolpiper] with the URL to ~/.codex/config.toml.
When both exist, Codex uses the server you added by hand.
Codex signs in to ToolPiper once: ToolPiper shows its consent page for the new connection, and once you approve it Codex reports that it is logged in. Codex in the ChatGPT desktop app lists the server in its MCP settings with a switch to turn it on or off. Always use the Streamable HTTP URL. Do not register ToolPiper as a legacy SSE server.
Approving tool calls
ToolPiper decides which calls need your approval, whichever app makes them. Claude Code shows ToolPiper's question in its own window. For Claude Desktop and Codex, ToolPiper asks on its own card on your Mac. If nobody answers the card, the call is refused and the app is told where the question was shown.
Installing ToolPiper with Homebrew
brew tap modelpiper/tap
brew trust modelpiper/tap
brew install --cask toolpiper
The middle line is required on Homebrew 6, which refuses a cask from any tap outside Homebrew's own until you trust that tap once. You never repeat it.
macOS shows its usual first-launch dialog once, as it does for the download.
ToolPiper keeps updating itself, so brew upgrade leaves it alone unless you
pass --greedy. brew uninstall --cask toolpiper removes the app.
brew uninstall --zap --cask toolpiper also removes ToolPiper's data, including
downloaded models. ToolPiper needs macOS 26 or later on Apple Silicon.