Add ToolPiper to the client as a Streamable HTTP MCP server at
http://127.0.0.1:9998/mcp. Any MCP client on the same Mac that speaks
Streamable HTTP connects this way, with no account and no token to paste, as long
as ToolPiper is running. Pick Streamable HTTP even when the client also offers
SSE or a command to launch: ToolPiper serves neither.
Cursor
Add the server to ~/.cursor/mcp.json:
{
"mcpServers": {
"toolpiper": {
"type": "http",
"url": "http://127.0.0.1:9998/mcp"
}
}
}
Cursor lists it under Customize, MCPs, with the number of tools it found. If Cursor tried to connect while ToolPiper was not running, it can keep treating the server as failed even after a restart: turn the server off and on again there and it connects.
Use an agent that runs on this Mac. Cursor's cloud agents run on another machine, so they cannot reach ToolPiper, and Cursor reports that as the server needing authentication.
Cline and other clients
Use the client's MCP settings to add a server of type Streamable HTTP with the URL above. If the client only offers SSE, or only launches local programs, it cannot reach ToolPiper.
Claude Desktop, Claude Code and Codex have their own install steps: see Using ToolPiper with Claude Desktop, Claude Code, Codex and Homebrew.
Apps that cannot connect
Connectors that run in the cloud, such as ChatGPT's or the ones on claude.ai and in mobile apps, cannot reach a server on your Mac, so they cannot use ToolPiper.
A shorter tool list
A client gets ToolPiper's whole tool list. To offer it fewer, add a profile to the
URL, for example http://127.0.0.1:9998/mcp?profile=automation for the browser
and testing tools with the core ones.
Approving tool calls
ToolPiper decides which calls need your approval, whichever client makes them, and asks you before a call that needs it runs: on ToolPiper's approval card, or in the client's own window when the client can show the question itself. Choices you make in ToolPiper's MCP Tools apply to every connected client.