4 ms·
> This is absolutely necessary since you can (and will) use AI for a million different things the point is, is it necessary to create a new protocol?
by simianwords 8mo ago
> This is absolutely necessary since you can (and will) use AI for a million different things
the point is, is it necessary to create a new protocol?
- hannasanarion 8mo agoExactly this. I've made some MCP servers and attached tons of other people's MCP servers to my llms and I still don't understand why we can't just use OpenAPI. Why did we have to invent an entire new transport protocol for this, when the only stated purpose is documentation?
- CharlieDigital 8mo agoBy and large, it is a very simple protocol and if you build something with it, you will see that it is just a series of defined flows and message patterns. When running over streamable HTTP, it is more or less just a simple REST API over HTTP with JSON RPC payload format and known schema. Even the auth is just OAuth.
- paulddraper 8mo agoIt’s not a new protocol. It’s JSON-RPC plus OAuth. (Plus a couple bits around managing a local server lifecycle.)
- drdaeman 8mo agoWorld would be surely a saner place if instead of “MCP vs CLI” people would talk about “JSON-RPC vs execlp(3)”. Not accurate, but at least makes on think of the underlying semantics. Because, really, what matters is some DSL to discover and describe action invocations.