{"slug": "mcp-cli", "name": "mcp-cli", "category": "terminal", "category_name": "Terminal and shell", "description": "", "recommenders": 4, "commenters": 5, "warners": 0, "score": 3.684, "rising": 0.02, "first": "2026-01-11", "latest": "2026-08-05", "why": "used MCP-CLI to define all my MCP servers and wrap them in a CLI command for agent use.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 4, "neutral": 0, "compare": 1, "warn": 0}, "spark": [0, 0, 1, 0, 1, 1, 0, 0, 0, 1, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "used MCP-CLI to define all my MCP servers and wrap them in a CLI command for agent use.", "kind": "", "icon": true, "domain": null, "github_repo": "github.com/philschmid/mcp-cli", "official_url": "https://github.com/philschmid/mcp-cli", "pricing": "", "aliases": ["mcp-cli", "MCP-CLI"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 786880849, "item_id": 49180053, "url": "https://news.ycombinator.com/item?id=49180053", "by": "nextaccountic", "date": "2026-08-05", "stance": "recommend", "quote": "have your agent use a CLI tool that calls MCP, like mcp-cli [1]", "excerpt": "That's a harness concern, not a protocol concern. For example, maki [0] allows that automatically for all tools > code_execution tool - uses monty to run an interpreter that has all other tools available as async functions. Maki uses it to filter / summarize / transform / pipe data to other tools as input, without it ever reaching and polluting the context window. Sandbox limited by time & memory. Failing that, you c", "context": "", "use_case": "", "switched_from": "", "story": "Stateless MCP has recaptured my interest"}, {"id": 763500720, "item_id": 47718795, "url": "https://news.ycombinator.com/item?id=47718795", "by": "senordevnyc", "date": "2026-04-10", "stance": "recommend", "quote": "I use this pattern with mcp-cli", "excerpt": "I use this pattern with mcp-cli, and I do that instead of a curl request for two reasons: 1) not leaking my creds into the agent session, and 2) so I can allowlist / denylist specific tools on an MCP server, which I can't do as easily if I give the agent an API token and curl.", "context": "", "use_case": "MCP tool access, allowlisting", "switched_from": "", "story": "I Still Prefer MCP over Skills"}, {"id": 763411600, "item_id": 47713225, "url": "https://news.ycombinator.com/item?id=47713225", "by": "senordevnyc", "date": "2026-04-09", "stance": "recommend", "quote": "used MCP-CLI to define all my MCP servers and wrap them in a CLI command for agent use.", "excerpt": "I love the idea of MCP, but it needs a progressive disclosure mechanism. A large MCP from a provider with hundreds or even thousands of tools can eat up a huge amount of your context window. Additionally, MCPs come in a bunch of different flavors in terms of transport and auth mechanisms, and not all harnesses support all those options well. I\u2019ve gone the other way, and used MCP-CLI to define all my MCP servers and w", "context": "", "use_case": "wrapping MCP servers for agents", "switched_from": "", "story": "I Still Prefer MCP over Skills"}, {"id": 755316464, "item_id": 47207279, "url": "https://news.ycombinator.com/item?id=47207279", "by": "wener", "date": "2026-03-01", "stance": "recommend", "quote": "Why not use mcp-cli mode, I event made a replica for that", "excerpt": "Why not use mcp-cli mode, I event made a replica for that https://github.com/wenerme/wode/tree/develop/packages/wener-mcp-cli", "context": "", "use_case": "", "switched_from": "", "story": "Stop Burning Your Context Window \u2013 How We Cut MCP Output by 98% in Claude Code"}, {"id": 745262609, "item_id": 46578913, "url": "https://news.ycombinator.com/item?id=46578913", "by": "jauntywundrkind", "date": "2026-01-11", "stance": "recommend", "quote": "I also ran into https://github.com/philschmid/mcp-cli this morning, which similarly makes a cli out of MCPs.", "excerpt": "I also ran into https://github.com/philschmid/mcp-cli this morning, which similarly makes a cli out of MCPs. I had been working a little on my own, but here we are! I see this as a very viable path to \"code mode\", to having ai write code instead of directly invoking tools. Having the AI write down is work allows nice refinement over time, iteration, in a way that it just calling all the tools directly doesnt yield up", "context": "", "use_case": "CLI wrapper for MCP servers", "switched_from": "", "story": "Show HN: mcpc \u2013 Universal command-line client for Model Context Protocol (MCP)"}]}], "caveats": [], "who": [], "tags": [], "use_cases": ["mcp tool access, allowlisting", "wrapping mcp servers for agents", "cli wrapper for mcp servers"], "compared": [], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=47712718", "title": "I Still Prefer MCP over Skills", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49131438", "title": "Stateless MCP has recaptured my interest", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47193064", "title": "Stop Burning Your Context Window \u2013 How We Cut MCP Output by 98% in Claude Code", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47157398", "title": "I made MCP cheaper in one command", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46513163", "title": "Show HN: mcpc \u2013 Universal command-line client for Model Context Protocol (MCP)", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {"recommend": 1}, "2026-02": {"compare": 1}, "2026-03": {"recommend": 1}, "2026-04": {"recommend": 1}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {"recommend": 1}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 786880849, "item_id": 49180053, "url": "https://news.ycombinator.com/item?id=49180053", "by": "nextaccountic", "date": "2026-08-05", "stance": "recommend", "quote": "have your agent use a CLI tool that calls MCP, like mcp-cli [1]", "excerpt": "That's a harness concern, not a protocol concern. For example, maki [0] allows that automatically for all tools > code_execution tool - uses monty to run an interpreter that has all other tools available as async functions. Maki uses it to filter / summarize / transform / pipe data to other tools as input, without it ever reaching and polluting the context window. Sandbox limited by time & memory. Failing that, you c", "context": "", "use_case": "", "switched_from": "", "story": "Stateless MCP has recaptured my interest"}, {"id": 763500720, "item_id": 47718795, "url": "https://news.ycombinator.com/item?id=47718795", "by": "senordevnyc", "date": "2026-04-10", "stance": "recommend", "quote": "I use this pattern with mcp-cli", "excerpt": "I use this pattern with mcp-cli, and I do that instead of a curl request for two reasons: 1) not leaking my creds into the agent session, and 2) so I can allowlist / denylist specific tools on an MCP server, which I can't do as easily if I give the agent an API token and curl.", "context": "", "use_case": "MCP tool access, allowlisting", "switched_from": "", "story": "I Still Prefer MCP over Skills"}, {"id": 763411600, "item_id": 47713225, "url": "https://news.ycombinator.com/item?id=47713225", "by": "senordevnyc", "date": "2026-04-09", "stance": "recommend", "quote": "used MCP-CLI to define all my MCP servers and wrap them in a CLI command for agent use.", "excerpt": "I love the idea of MCP, but it needs a progressive disclosure mechanism. A large MCP from a provider with hundreds or even thousands of tools can eat up a huge amount of your context window. Additionally, MCPs come in a bunch of different flavors in terms of transport and auth mechanisms, and not all harnesses support all those options well. I\u2019ve gone the other way, and used MCP-CLI to define all my MCP servers and w", "context": "", "use_case": "wrapping MCP servers for agents", "switched_from": "", "story": "I Still Prefer MCP over Skills"}, {"id": 755316464, "item_id": 47207279, "url": "https://news.ycombinator.com/item?id=47207279", "by": "wener", "date": "2026-03-01", "stance": "recommend", "quote": "Why not use mcp-cli mode, I event made a replica for that", "excerpt": "Why not use mcp-cli mode, I event made a replica for that https://github.com/wenerme/wode/tree/develop/packages/wener-mcp-cli", "context": "", "use_case": "", "switched_from": "", "story": "Stop Burning Your Context Window \u2013 How We Cut MCP Output by 98% in Claude Code"}, {"id": 754553376, "item_id": 47159586, "url": "https://news.ycombinator.com/item?id=47159586", "by": "22c", "date": "2026-02-25", "stance": "compare", "quote": "mcp-cli looks like a very similar thing", "excerpt": "Pretty sure I saw this one a couple of weeks back, or something very similar to it.. https://github.com/philschmid/mcp-cli Edit: Turns out was https://github.com/steipete/mcporter noted elsewhere in the thread, but mcp-cli looks like a very similar thing.", "context": "", "use_case": "", "switched_from": "", "story": "I made MCP cheaper in one command"}, {"id": 745262609, "item_id": 46578913, "url": "https://news.ycombinator.com/item?id=46578913", "by": "jauntywundrkind", "date": "2026-01-11", "stance": "recommend", "quote": "I also ran into https://github.com/philschmid/mcp-cli this morning, which similarly makes a cli out of MCPs.", "excerpt": "I also ran into https://github.com/philschmid/mcp-cli this morning, which similarly makes a cli out of MCPs. I had been working a little on my own, but here we are! I see this as a very viable path to \"code mode\", to having ai write code instead of directly invoking tools. Having the AI write down is work allows nice refinement over time, iteration, in a way that it just calling all the tools directly doesnt yield up", "context": "", "use_case": "CLI wrapper for MCP servers", "switched_from": "", "story": "Show HN: mcpc \u2013 Universal command-line client for Model Context Protocol (MCP)"}]}