A2A

(I work on a2a) Thank you for the feedback? Would you consider writing up an issue on our github with some more specifics? https://github.com/google/a2a A2A is being developed in the open with the community. You are finding some early details that we are looking into and will be addressing. We have many partners who will be contributing and want this to be a truly open, collaborative endeavor. We acknowledge this is a little different than dropping a polished '1.0' version in github on day 1. But that is intentional :)

Hi there! If you load the CLI demo in the github repo (https://github.com/google/A2A/tree/main/samples/python/hosts...) you can see what the A2A servers are returning. Take a look!

I have the same problem come out in my mind. What if I wrap the agent as a tool in MCP? Since the agents I got from the 'A2A' protocol is passed as tools to another Agent... https://github.com/google/A2A/blob/72a70c2f98ffdb9bd543a57c8...

or adopt Google's. Which is an open standard that is Apache licensed[1]. That's no moat for Google. At best it's a drainage ditch. [1]: https://github.com/google/A2A

Some very quick initial thoughts - the json spec has some similarities to mcp: https://google.github.io/A2A/#/documentation?id=agent-card - there's an agent card that describes capabilities that google wants websites to host at https://DOMAIN/.well-known/agent.json according to https://google.github.io/A2A/#/topics/agent_discovery so crawlers can scrape to discover agents. The jsonrpc calls look similar-ish to mcp tool calls except the inputs and outputs look closer to the inputs/outputs from calling an LLM (ie messages, artifacts, etc.). The JS server example that they give is interesting https://github.com/google/A2A/tree/main/samples/js/src/serve... - they're using a generator to send sse events back to the caller - a little weird to expose as the API instead of just doing what express allows you to do after setting up an sse connectio

> A2A is an open protocol that complements Anthropic's Model Context Protocol (MCP), which provides helpful tools and context to agents. A "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?

Link to repo: https://github.com/google/A2A Docs: https://google.github.io/A2A/#/documentation I 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.