[shrisukhani]

Thanks!

And yeah MCP is super promising. We announced this on X and LinkedIn yesterday and the response has been really good. A lot of people with a bunch of use cases.

One surprising thing is there’s also a bunch of semi/non-technical people using our MCP server and the installation experience for them rn just absolutely sucks.

I think once auth and 1-click install are solved, MCP could become the standard way to integrate tools with LLMs

[_pdp_]

The MCP protocol is really not that good. The stateful nature of it makes it only suitable as a local desktop RPC pipe - certainly not something that will work well on mobile nor anything anyone would like to try to run maintain in a server-to-serve context.

It is fine if that is the scope. It is also understandable why Anthropic chose to use a stateful protocol where stateless HTTP would be more than enough. They are catering for the default transport layer which is stdio based where state needs to be established.

There are also other aspects of it that are simply unnecessarily complex and resource intensive for no good reasons.

[pkkkzip]

what do you suggest instead of MCP ?

[_pdp_]

Well OpenAPI. You don't need some wired debugging tools nobody knows how to use, a stateful protocol that is hard to troubleshoot, etc. There is plenty of support already built into standard HTTP services and Swagger - abundance of tools and documentation too and what we call function calling is basically JSON Schema which is at the core of swagger definitions.

MCP is trying to reinvent OpenAPI but in the wrong way.

[pkkkzip]

doesnt seem like a good equivalent

[_pdp_]

Why not? It is easy and widely available. It has support for many development tools, from browsers to rest clients, intercepting proxies, and more.

I guess it is not exciting because nobody can put their name on it.