ToolPiper MCP Server
One install. Only the tools you need.
ToolPiper is a local MCP server for macOS: 470 tools for your browser, files and Git, images, video and the Mac itself, behind one URL. Connect only the categories you need and cut tool overhead in your context window by up to 95%. PiperMatch finds the rest when your agent asks.
Every plan, counted.
207 of ToolPiper's 470 native tools stay free. Pro adds 135, Studio adds 111 and Max adds the last 17. Each plan includes everything before it, and any MCP server you install runs free on every plan.
- Free207207 tools in all
- Pro$10/mo+135342 tools in all
- Studio$29/mo+111453 tools in all
- Max$49/mo+17470 tools in all
207 + 135 + 111 + 17 = 470 tools
See what each plan adds →Connect in under a minute.
The MCP server ships inside ToolPiper.app, with nothing else to install. Any client that speaks streamable HTTP can connect: Claude Code, Cursor, Devin, Codex, Gemini CLI, and Cline.
Claude Code
claude mcp add -s user --transport http toolpiper http://127.0.0.1:9998/mcpCursor / Devin / Gemini CLI in your MCP config
{
"mcpServers": {
"toolpiper": {
"type": "http",
"url": "http://127.0.0.1:9998/mcp"
}
}
}Filter to fewer tools to save context
claude mcp add -s user --transport http toolpiper "http://127.0.0.1:9998/mcp?profile=automation"Pick your categories.
470 tools, organized into 15 categories. Tap the ones you need and the install command below follows your selection.
Every tool costs context.
An MCP client can send its whole tool list to the model with every message, so each row takes room from your conversation. ToolPiper lists names and parameters and leaves descriptions out, which keeps all 470 tools to about 127 KB. Filtering with ?category= or ?profile= cuts that by up to 95%: the inference profile is about 5.4 KB and the automation profile about 17 KB. A filtered agent can still pull any tool it turns out to need through request_tools, which PiperMatch answers.
claude mcp add -s user --transport http toolpiper http://127.0.0.1:9998/mcpPiperMatch picks the right tools.
PiperMatch is ToolPiper's on-device tool matcher. It reads a request and ranks every tool you allow on your Mac's Neural Engine, with no language model and no cloud call. Filtering shortens the list you connect. PiperMatch finds the tool a request needs, whether it's on that list or not.
In ToolPiper's chat, voice and automations
On every turn. PiperMatch picks the tools that apply and ToolPiper sends only those, within one eighth of the model's window. With full definitions, the library is nearly four times the 32,768-token window ToolPiper gives a local model, so this is how a local model reaches all 470 tools.
In Claude Code, Cursor and other MCP clients
On request. These apps build their own requests from the tool list you connect, and every list carries request_tools. The agent describes what it needs ("read a PDF"), PiperMatch ranks the tools you allow, and the agent gets the five best matches back with their full definitions.
435 of 451
test requests had the right tool inside the 25 PiperMatch picked, and 360 ranked it first.
101 of 102
test requests ranked a tool PiperMatch had never seen, from 51 other MCP servers, inside the same 25.
26,844 bytes
of tool definitions per request instead of 105,026. Claude Sonnet 5.5 chose at least as well from 25 full definitions as from the 455-row MCP listing.
Measured in October 2026 on ToolPiper build 64, on test requests PiperMatch had never seen. What that saves in tokens →
How it works.
One local server, HTTP over loopback, every backend ToolPiper runs.
AI Client (Claude Code, Cursor, Devin, Codex, Gemini CLI, Cline, 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)Auth
A local connection needs no token and no setup. LAN and remote peers authenticate with a bearer. Every call still meets your Security level.
Errors
ToolPiper's own errors come back as clean tool results your agent can act on. If the app isn't running, the endpoint is unreachable: start ToolPiper and reconnect.
Annotations
Read-only tools advertise readOnlyHint, destructive tools advertise destructiveHint, so AI clients can tell a read from a delete before they act.
Filtering
Pass ?category= or ?profile= to serve only the tools you need.
On-demand discovery
Every tool list carries request_tools, so a filtered connection never dead-ends. PiperMatch answers it with the tools the agent asked for.
Client limits flagged
Devin silently drops tools past 100. ToolPiper warns you when your selection runs past a client's limit, so you can narrow that connection with ?category= or ?profile=. What you leave out stays reachable through request_tools.
204
macOS system tools built in.
The system category controls audio, display, Bluetooth, windows, Finder, Dock, notifications, contacts, calendar, and more, all built into ToolPiper. No extra apps or configuration needed.
All 470 tools.
Grouped by category. Click to expand.
Frequently asked questions.
Quick answers about the ToolPiper MCP server.
What is the ToolPiper MCP server?
ToolPiper is a local MCP server for macOS with 470 tools across 15 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.
How do I connect ToolPiper to Claude Code?
Install ToolPiper, then run: claude mcp add -s user --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.
Does ToolPiper work with Cursor, Devin, and other MCP clients?
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 -s user --transport http toolpiper http://127.0.0.1:9998/mcp.
How much context do the tools use?
Each tool is a row in the list your MCP client reads: its name and parameters, with descriptions left out. All 470 tools come to about 127 KB. Adding ?category= or ?profile= to the connect URL lists only the tools you need and cuts that by up to 95%: the inference profile is about 5.4 KB and the automation profile about 17 KB. A filtered agent can still fetch any missing tool on demand through the request_tools meta-tool, which returns its full definition.
What is PiperMatch?
PiperMatch is ToolPiper's on-device tool matcher. It ranks every tool you allow against a request on the Mac's Neural Engine, with no language model and no cloud call. ToolPiper's own chat, voice and automations use it to send a model only the tools that apply. MCP clients reach it through the request_tools meta-tool, which returns the five best matches with their full definitions.
How many MCP tools are free, and how many come with each plan?
207 of ToolPiper's 470 native tools stay free. Pro adds 135, Studio adds 111 and Max adds the last 17. Each plan includes everything before it, so Pro reaches 342, Studio 453 and Max all 470. Any MCP server you install runs free on every plan, and its tools are not part of these counts.
Is the ToolPiper MCP server free?
Yes. ToolPiper is a free download with no account required: the MCP server, the local model runner and all speech are included, and any MCP server you install runs through it. Our own native tools are the product. Pro ($10/mo) adds them: browser automation, files and Git, the clipboard cache, RAG, web scraping, screen and image analysis, the cloud proxy, the outreach toolkit, and API discovery with replay; Studio ($29/mo) is where the Mac makes things: image editing and generation, layered image workbenches, storyboards, video editing, image and video upscaling, and pose detection; and Max ($49/mo) adds PiperFlow, the agentic code editor, and automation for every other feature.
Does anything leave my Mac?
With local models, no prompts, responses, or files leave your Mac. Inference, speech, vision, RAG, and system actions all run on-device. ToolPiper contacts our servers for update checks, a license check when you're signed in, a daily activity count and optional usage counts; you can turn the last two off in Settings, and none of them include your content. Other traffic is traffic you start: browsing or downloading a model queries HuggingFace, which can log your IP address and search terms; a cloud provider you pick gets requests sent with your own API key; and a benchmark you choose to submit carries hardware and throughput numbers, never content, and is linked to your installation.
Ready?
Your command from the picker above, ready to paste.
claude mcp add -s user --transport http toolpiper http://127.0.0.1:9998/mcp