MCP + A2A: The Protocols Making AI Agents Actually Work Together
I presented this at the AI Engineer meetup in London. It is a short, practical overview of why agent interoperability matters now, and how two protocols, MCP & A2A, make it workable today.
Why watch
A crisp mental model you can share with your team. It shows the problem, places MCP and A2A in the stack, and walks through a concrete hiring workflow so you can map it to your own systems.
What you will learn
- Where MCP fits: tools, resources, prompts, sampling, and common transports
- Where A2A fits: agent cards, tasks, messages, artifacts
- Three architectures for recruitment automation and why MCP plus A2A scales
- How to cut N squared glue work by standardising layers
Talk context
Delivered live to practitioners at the AI Engineer meetup. The goal was to give teams a shared language for splitting access (MCP) from collaboration (A2A) so projects stop stalling on bespoke integrations.
Who this is for
Engineers and architects shipping agent systems in production. If you are tired of bespoke glue, this will help you line things up.
Subscribe
If this was useful, subscribe to the newsletter (and the new youtube channel) for deeper implementation notes, patterns, and code examples.
No spam, no sharing to third party. Only you and me.