[LeonidBugaev]

To put it simple:

A2A is for communication between the agents. MCP is how agent communicate with its tools.

Important aspect of A2A, is that it has a notion of tasks, task rediness, and etc. E.g. you can give it a task and expect completely in few days, and get notified via webhook or polling it.

For the end users for sure A2A will cause a big confusing, and can replace a lot of current MCP usage.

[NickNaraghi]

If an agent could wrap itself in an MCP server, would that make A2A redundant?

[fengkx]

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...

[tuananh]

you mean wrap mcp server in itself?