Local MCP vs io.github.ModelPiper/toolpiper
Local MCP is an MCP server published by local-mcp.com. Marketplaces we read that list it: 4 (Official MCP Registry, Claude Code: claude-plugins-community, npm registry (MCP servers), Community GitHub marketplaces). io.github.ModelPiper/toolpiper is an MCP server published by ModelPiper. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 3.0.421 Downloads/month (npm): 10 964 Downloads/week (npm): 1 023 Forks (GitHub): 12 Stars (GitHub): 73 Not marked · First seen |
Listed Version: 0.0.10-beta Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Listed Version: 3.0.421 Downloads/month (npm): 10 964 Downloads/week (npm): 1 023 Forks (GitHub): 12 Stars (GitHub): 73 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Local MCP | io.github.ModelPiper/toolpiper |
|---|---|---|
| Marketplaces that list it (differs) | 4 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 73 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 12 (better) | 0 (worse) |
| Last release (differs) | 2026-10-14 (worse) | 2026-10-16 (better) |
| Where it runs (differs) | Remote server or your machine | Not stated |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Parts of the bundle (differs) | 10 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/colibird-ai/local-mcp-releases | github.com/modelpiper/toolpiper |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 25 h ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Local MCP
Mac & Windows: let ChatGPT, Claude & Cursor use your email, calendar, iMessage, Teams, files.
io.github.ModelPiper/toolpiper
On-device MCP tools for macOS: local AI, speech, vision, browser automation, system control.
How to run each
Local MCP As a remote MCP server
claude mcp add --transport http local-mcp https://local-mcp.com/mcp
io.github.ModelPiper/toolpiper
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Local MCP has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.ModelPiper/toolpiper publish no settings it asks for, so we do not compare settings.
What it can do: Local MCP · What it can do: io.github.ModelPiper/toolpiper · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.