Pitroom vs Hackle
Pitroom is an MCP server published by ATASTECH. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Hackle is an MCP server published by hackle-io. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-24. 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 |  Pitroom |  Hackle |
|---|---|---|
| Official MCP Registry | Listed Version: 0.25.0 Downloads/month (npm): 5 297 Downloads/week (npm): 1 349 Forks (GitHub): 1 Stars (GitHub): 28 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 3 Stars (GitHub): 3 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.25.0 Downloads/month (npm): 5 297 Downloads/week (npm): 1 349 Forks (GitHub): 1 Stars (GitHub): 28 Not marked · First seen |
Not listed |
| Docker MCP Catalog | Not listed | Listed Version: sha256:b45e8e1c6390 Forks (GitHub): 3 Pulls (Docker Hub): 16 302 Stars (Docker Hub): 0 Stars (GitHub): 3 Not marked · First seen |
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 | Pitroom | Hackle |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 28 (better) | 3 (worse) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 16 302 |
| Forks (GitHub) (differs) | 1 (worse) | 3 (better) |
| Last release (differs) | 2026-10-19 | Not published |
| Where it runs (differs) | On your machine (pitroom) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 19 |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/atastech/pitroom | github.com/hackle-io/hackle-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-22 |
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
Pitroom
Hands bounded coding work to cheaper worker agents: verified answers, exact diffs, cost receipts.
Hackle
Remote MCP server for the Hackle Admin API: experiments, feature flags, remote config, messaging.
How to run each
Pitroom As a local MCP server: npm package
claude mcp add --transport stdio pitroom -- npx -y pitroom mcpHackle As a remote MCP server
claude mcp add --transport http hackle-mcp https://mcp.hackle.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Hackle has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Pitroom publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Pitroom publish no settings it asks for, so we do not compare settings.
What it can do: Pitroom · What it can do: Hackle · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.