Skip to content

Comment on Show HN: Mcp2cli – One CLI for every API, 96-99% fewer tokens than native MCP

Comments

How would the LLM exactly discover such unknown CLI commands?

I've got a qdrant based approach that I'm working on that solves that here: https://github.com/day50-dev/infinite-mcp

Essentially I've cloned thousands of mcp servers, used the readmes and the star rating to respond to the qdrant query (star ratings as a boost score have been an attack vector, yes I know, it's an incomplete product [1]), then presents it as a JSON response with "one-shots" which this author calls clis.

I think I became discouraged from working on it and moved on because my results weren't that great but search is hard and I shouldn't give up.

I'll get back on it seeing how good this tool is getting traction.

[1] There needs to be a legitimacy post-filter so that github user micr0s0ft or what-have-you doesn't go to to the top - I'm sure there's some best-of-practice ways of doing this and I shouldn't invent my own (which would involve seeing if the repo appears on non-UGC sites I guess?!) but I haven't looked into it

Skills or tell it the --list command would be my guess.

Skills is the right abstraction.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.