Looks similar to most other mid-level remote procedure call protocols, from XMLRPC to CORBA. The usual sync, async, poll, progress test problems apply. Things I'd expected to see and didn't:

- Client to server: "tell me what you can do". This has always been hard, but in the LLM era, it could potentially work, because a textural response would work.

- Similarly, being able to ask "How do I..." might be feasible now. It should be possible to talk to a new server and automatically figure out how to use it.

- "How much is this going to cost me?" Plus some way to set a cost limit on a query.

Given their anti-trust struggles, if Google for some reason dominates AI, they'd not want people to bring up anti-competitive behavior as a reason for that. Adopting open standards, especially open standards conceived outside Google is good for everyone including Google. They're well placed - from research to hardware to software and data.

They'll also want the industry to rapidly move forward and connect data to AI. MCP has momemtum.

I'm kind glad that the industry is distracted by vibe-coding, "tools" and MCP.

It's so clearly a dead-end. It gives freethinking developers and innovators time to focus on the next generation of software.

It doesn't really matter what it is as there are many equally good implementations, but whoever sets up the framework first and cements usage is likely to guarantee dominance for the foreseeable future. Probably into AGI and post.

Model Context Protocol seems good enough to me.

Related, discussion on A2A from the other day:

https://news.ycombinator.com/item?id=43631381

"The Agent2Agent Protocol (A2A)", 279 comments