Manager.io MCP vs mcp-hub
Manager.io MCP is an MCP server published by flumpiey. Marketplaces we read that list it: 1 (Official MCP Registry). mcp-hub is an MCP server published by ni-c. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-14. 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 |   Manager.io MCP |  mcp-hub |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.6 Downloads/month (PyPI): 197 Downloads/week (PyPI): 36 Forks (GitHub): 3 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 0.12.0 Downloads/month (npm): 1 618 Downloads/week (npm): 385 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.12.0 Downloads/month (npm): 1 618 Downloads/week (npm): 385 Forks (GitHub): 1 Stars (GitHub): 4 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 | Manager.io MCP | mcp-hub |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (worse) | 4 (better) |
| Forks (GitHub) (differs) | 3 (better) | 1 (worse) |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | On your machine (manager-mcp) | On your machine (@ni-c/mcp-hub) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | 12, secrets among them: 2 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/flumpiey/manager-mcp | github.com/ni-c/mcp-hub |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Manager.io MCP
MCP server for Manager.io bookkeeping: read-first with opt-in scoped task and write tools
mcp-hub
Many stdio MCP servers from one container, published over HTTPS with OAuth 2.1 for any MCP client
How to run each
Manager.io MCP As a local MCP server: PyPI package
claude mcp add --env "MANAGER_API_KEY=<YOUR_MANAGER_API_KEY>" --env "MANAGER_API_URL=<YOUR_MANAGER_API_URL>" --transport stdio manager-mcp -- uvx manager-mcpRequires: MANAGER_API_KEY (secret), MANAGER_API_URL
mcp-hub As a local MCP server: npm package
claude mcp add --env "EXTERNAL_URL=<YOUR_EXTERNAL_URL>" --env "PASSWORD_HASH=<YOUR_PASSWORD_HASH>" --env "TOTP_SECRET=<YOUR_TOTP_SECRET>" --transport stdio mcp-hub -- npx -y @ni-c/mcp-hub --stdioRequires: EXTERNAL_URL, PASSWORD_HASH (secret), TOTP_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Manager.io MCP asks for
MANAGER_API_KEY (secret)MANAGER_API_URLMANAGER_MCP_DELETE_SCOPESMANAGER_MCP_WRITE_SCOPES
Only mcp-hub asks for
CIMD_ALLOWED_ORIGINSCLIENT_REGISTRATIONCONFIG_PATHEXTERNAL_URLIDLE_TIMEOUT_MINUTESLOG_FILEPASSWORD_HASH (secret)PORTTOOL_CACHE_PATHTOTP_SECRET (secret)TRUSTED_PROXIESTWO_FACTOR
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Manager.io MCP · What it can do: mcp-hub · 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). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.