ToolPiper MCP Server
ToolPiper is a local MCP server for macOS with 421 tools across 14 categories. Load all of them, or filter to just the ones you need — saving up to 90% of context window overhead.
The MCP server ships inside ToolPiper.app — nothing else to install. Any client that speaks streamable HTTP can connect: Claude Code, Cursor, Windsurf, Gemini Code, and Codex.
Claude Code
claude mcp add --transport http toolpiper http://127.0.0.1:9998/mcpCursor / Windsurf / Gemini Code — add to your MCP config
{
"mcpServers": {
"toolpiper": {
"type": "http",
"url": "http://127.0.0.1:9998/mcp"
}
}
}Filter to fewer tools — save context
claude mcp add --transport http toolpiper "http://127.0.0.1:9998/mcp?profile=automation"421 tools, organized into 14 categories. Tap the ones you need — the install command below follows your selection.
Every tool definition rides along in the AI's context window on every message. All 421 tools ≈ 33,000 tokens per message. Filtering with ?category= or ?profile= cuts that by up to 90%.
claude mcp add --transport http toolpiper http://127.0.0.1:9998/mcp181
The system category controls audio, display, Bluetooth, windows, Finder, Dock, notifications, contacts, calendar, and more — integrated directly into ToolPiper. No extra apps or configuration needed.
One local server, HTTP over loopback, every backend ToolPiper runs.
AI Client (Claude Code, Cursor, Windsurf, Gemini Code, Codex, etc.)
↓ JSON-RPC over Streamable HTTP
POST 127.0.0.1:9998/mcp [?category= | ?profile=]
↓
ToolPiper.app (macOS, running)
↓
Backends (llama.cpp, FluidAudio, MLX Audio, Apple Intelligence, Vision, NLP, Pose, CDP, System Actions)The MCP binary reads ToolPiper's session key from disk on every request. Zero configuration.
If ToolPiper isn't running, every tool returns an install message pointing to modelpiper.com.
Read-only tools advertise readOnlyHint, destructive tools advertise destructiveHint, so AI clients can tell a read from a delete before they act.
Pass ?category= or ?profile= to serve only the tools you need.
Grouped by category. Click to expand.
Quick answers about the ToolPiper MCP server.
ToolPiper is a local MCP server for macOS with 421 tools across 14 categories — local LLM inference, speech, vision and OCR, RAG, browser automation, files and Git, testing, video, and macOS system control. The MCP binary ships inside the ToolPiper app and everything runs on-device.
Install ToolPiper, then run: claude mcp add --transport http toolpiper http://127.0.0.1:9998/mcp. The MCP server runs inside the app over streamable HTTP on loopback, so there is no separate binary to install.
Yes. Any MCP client that speaks streamable HTTP can connect. Add an HTTP server entry ({"type":"http","url":"http://127.0.0.1:9998/mcp"}) to your client's MCP config, or run claude mcp add --transport http toolpiper http://127.0.0.1:9998/mcp.
Loading all 421 tools costs roughly 33,000 tokens per message. Adding ?category= or ?profile= to the connect URL serves only the tools you need and cuts that overhead by up to 90%.
Yes. ToolPiper is a free download with no account required, and the MCP server with the full local model runner is included. Three paid rungs add more on top: Pro ($10/mo) for RAG, scraping, and the cloud proxy, Studio ($29/mo) for image and video upscaling, and Max ($49/mo) for the agentic code editor and PiperTest.
No prompts, responses, or files leave your Mac. Inference, speech, vision, RAG, and system actions all run on-device. ToolPiper reaches the network in three places, each one you start: browsing or downloading a model queries HuggingFace, which can log your IP address and search terms; a cloud provider you pick using your own API key; and an anonymous benchmark score you choose to publish, which carries hardware and throughput numbers, never content.
Your command from the picker above, ready to paste.
claude mcp add --transport http toolpiper http://127.0.0.1:9998/mcp