News for hackers. Stuff that matters.
Re:MCP Is Dead; Long Live MCP by simianwords on Saturday March 14, 2026 @05:17PM (#47381268)
> 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?

Re:MCP Is Dead; Long Live MCP by hannasanarion on Saturday March 14, 2026 @05:38PM (#47381492)
Exactly 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?

Re:MCP Is Dead; Long Live MCP by CharlieDigital on Saturday March 14, 2026 @05:40PM (#47381515)
By 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.

Re:MCP Is Dead; Long Live MCP by paulddraper on Saturday March 14, 2026 @05:58PM (#47381680)
It’s not a new protocol.

It’s JSON-RPC plus OAuth.

(Plus a couple bits around managing a local server lifecycle.)

Re:MCP Is Dead; Long Live MCP by drdaeman on Saturday March 14, 2026 @06:55PM (#47382167)
World 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.