Skip to content
Bridge MCP and A2A v1.0: One Agent, Two Protocols — ContentBuffer guide

Bridge MCP and A2A v1.0: One Agent, Two Protocols

K
Kodetra Technologies··12 min read Intermediate

Summary

Build a Python agent that speaks A2A v1.0 outward and calls MCP tools inward.

On August 20, 2026, Google formally handed the Agent2Agent protocol to the Linux Foundation's Agentic AI Foundation, the same neutral home that already hosts Anthropic's Model Context Protocol. The foundation went from 49 founding members to more than 250 in under a year, with AWS, Anthropic, Google, Microsoft, OpenAI, Bloomberg and Cloudflare all signed on.

The headline is governance. The part that actually changes your code is quieter: A2A shipped v1.0, and v1.0 is not backwards compatible with the v0.2 tutorials that dominate search results. The well-known URL moved. The JSON-RPC method names changed. The kind discriminator on message parts is gone. If you copy a blog post from six months ago, your first request comes back -32601 Method not found.

Keep reading — it's free

Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.

Also get
or

Already a member? Sign in

Comments

Subscribe to join the conversation...

Be the first to comment