5 Comments
User's avatar
Devesh's avatar

MCP is the only one of the three that looks load-bearing in production right now. A2A and ACP feel like specs for a multi-agent world that hasn’t shown up. Discovery and agent cards start mattering once agents from different vendors have to negotiate with each other, and most setups are still one orchestrator calling tools. Are you seeing A2A used anywhere real yet?

そんちゃー君 🔰🏖️🌴's avatar

現状のAIエージェントの乱立する状況を無理やり3つに分類してパッケージ化しようとした結果、技術的な定義が崩壊している

James Bell's avatar

ACP was merged into A2A a year ago - unless I’m missing something I don’t see why they’re being presented as alternate options

Josh Green's avatar

Clear breakdown of a confusing space. One angle I would add from the self-hosting side, once you are wiring agents together with these protocols the bottleneck quietly moves to how many models you can actualy serve at once on your own hardware. A chatty multi-agent setup can fan out into a lot of concurrent inference, and that is where a second GPU and batched serving earn their keep versus a single card.

AI For Normal People's avatar

Great architectural breakdown. Standardizing agent-to-agent communication protocols feels like the early days of establishing HTTP for the web. Getting this right is going to be the difference between fragmented, siloed automation and a truly interoperable AI ecosystem.