thellimist

From use case point of view

skills are unstructured. MCP is structured.

You don't want stripe skill. You want stripe MCP of CLI to interact with. When stripe does an update you want to have it.

I didn't go into technical details or anything. Just laid the most important use case that skills cannot be sufficient

Does anyone else similar outputs?

fixed - github.com/thellimist/clihub

If you read my posts before 2023, it's same style.

I guess my thinking way is similar to LLMs, has clear structure.

I used to have more grammar issues, that LLMs fix, but the high level outline etc. are actually how I think about it. If it's not, I modify it

Rust doesn't compile different machines well. So choose Go

I did - I have my almost a dozen CLIs that are custom built that I'm using. Very reliable.

It still needs to do discovery (--help etc.), always gets the job done

did you check the token usage comparison between cmcp and cli?

This is cool!

I was actually thinking if I should support daemons just to support playwright. Now I don't have a use case for it

FYI the blog has direct comparison to Anthropic’s Tool Search.

Regardless, most MCPs are dumping. I know Cloudflare MCP is amazing but other 1000 useful MCPs are not.

I actually want to combine this and CLIHub into a directory where someone can download all the official MCPs or CLIs (or MCP to CLIs) with a single command

I don't prefer to use online skills where half has malware

Official MCPs are trusted. Official MCPs CLIs are trusted.

I was happy with playwright like MCPs that require the daemon so didn't convert them to CLIs.

My use cases are almost all 3rd party integrations.

Have you seen any improvements converting on MCPs that require persistency into CLI?