cli2mcp vs mcpify
cli2mcp is an MCP server published by RonieNeubauer. Marketplaces we read that list it: 1 (Official MCP Registry). mcpify is an MCP server published by furkan708. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.4 Downloads/month (npm): 179 Downloads/week (npm): 28 Forks (GitHub): 0 Stars (GitHub): 12 Not marked · First seen |
Listed Version: 1.19.0 Downloads/month (PyPI): 1 131 Downloads/week (PyPI): 180 Forks (GitHub): 3 Stars (GitHub): 2 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 | cli2mcp | mcpify |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 0 (worse) | 3 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (cli2mcp) | On your machine (mcpify-openapi) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/ronieneubauer/cli2mcp | github.com/furkan708/mcpify |
| 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
cli2mcp
Wrap any CLI as a Model Context Protocol server - schema auto-inferred from --help.
mcpify
Focused, production-ready CLI: turn any OpenAPI REST API into an MCP server.
How to run each
cli2mcp As a local MCP server: npm package
claude mcp add --transport stdio cli2mcp -- npx -y cli2mcp "<YOUR_COMMAND>"
Requires: <command>
mcpify As a local MCP server: PyPI package
claude mcp add --transport stdio mcpify -- uvx mcpify-openapi
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
Neither one's marketplaces publish the settings it asks for.
What it can do: cli2mcp · What it can do: mcpify · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.