[rgbrgb]

This is cool. I was skeptical of MCP's until I made one recently. They're essentially the exact same as 1) giving your agent a CLI tool or REST API and 2) pointing it there in an AGENT.md/CLAUDE.md. Agents are great at using built-for-human CLI tools and IMO they don't need anything purpose-built for agents. The key difference, which ends up being a usability win for non-technical users, is that the MCP bundles 1 and 2 - harnesses inject the MCP tool descriptions on every session after install. Of course, that's also why you need to be careful about context bloat when using/building them

[nijave]

Yeah MCPs are easier to distribute.

In my experience, they also work better with dumber models than CLIs (which saves money)

[pzullo]

+1 !! Thanks for putting it so clearly, also CLIs and REST have their space in some applications, I think MCP is a way to organize them and distribute them better

[estetlinus]

I don’t like that non-technical users has to keep context bloat in mind. That should be ”solved” on the developer end. How would they now it’s bloated if they treat MCPs like regular software? I 100% agree on designing things for humans, and you’ll get the AI-agents for free. I am surprised no one seems to have figured that out yet.

[nsonha]

Isn't it solved with Tool Search? I have not heard people complaining about MCP context bloat for like a quarter already.

[estetlinus]

TBF, I haven’t heard much about MCPs at all lately. I thought it was one of those “install once -> make LinkedIn post on how MCPs will change the world -> ugh MCP crashes with wierd error -> abandon” things. Could be wrong.