The Agent2Agent Protocol (A2A)
developers.googleblog.com
The Agent2Agent Protocol (A2A)
1–10 of 293 posts
Re: The Agent2Agent Protocol (A2A)
#2Re: The Agent2Agent Protocol (A2A)
#3I have to say, the endorsements at the end somehow made this seem worse…
Re: The Agent2Agent Protocol (A2A)
#4Re: The Agent2Agent Protocol (A2A)
#5Re: The Agent2Agent Protocol (A2A)
#6on it's face this kind of seems dumb. aren't agents supposed to be adaptable enough to handle any protocol?
Re: The Agent2Agent Protocol (A2A)
#7I think they are trying to ride the MCP hype as well with their own implementation that is also meh. MCP itself is also an over-engineered implementation of AI plugins by OpenAI. Obviously the end game is control over a standard which can act as a strategic tool for boosting valuations or even better product positioning.
The better approach is to simply use open standards that already exists but I guess this is just not sexy.
Re: The Agent2Agent Protocol (A2A)
#8on it's face this kind of seems dumb. aren't agents supposed to be adaptable enough to handle any protocol?
Re: The Agent2Agent Protocol (A2A)
#9A "server" sample: https://github.com/google/A2A/tree/main/samples/js/src/serve...
So it looks like the point is that it keeps the connection/context open for multiple interactions vs. MCP, which is more like pure request-response?