MCP & Agent-to-Agent Protocols
Understand the protocols that connect AI agents to tools and to each other: MCP internals, building and securing servers, A2A agent cards and tasks, and how the two fit together, with a real server driven over JSON-RPC.
Syllabus
Why Agents Need Protocols
- The Integration Problem
- MCP, A2A and Function Calling: Who Does What
- Hosts, Clients, Servers and Peer Agents
- When You Do and Do Not Need Protocols
Inside MCP: Messages, Lifecycle and Primitives
- JSON-RPC 2.0 in Five Minutes
- The Initialize Handshake and Capabilities
- Server Primitives: Tools, Resources, Prompts
- Transports: stdio and Streamable HTTP
- Client Features: Sampling, Roots, Elicitation, Pagination
Building Good MCP Servers
- Your First Server With the Python SDK
- Designing Tools the Model Can Use
- Errors, Validation and Recoverable Failures
- Testing and Inspecting MCP Servers
MCP Clients, Hosts and Remote Servers
Security for Tool-Using Agents
- Trusting Servers: Supply Chain and Tool Poisoning
- Prompt Injection Through Tool Results
- Least Privilege, Allow-Lists and Human Approval
- Sandboxing, Secrets and Audit Logging
Agent2Agent (A2A): Agents Working Together
- Why Agent-to-Agent Communication
- The Agent Card: Discovery
- Tasks, Messages, Parts and Artifacts
- Discovery, Routing and Delegation
- Streaming, Push Notifications and Security in A2A
MCP and A2A Together
- A Reference Architecture
- Testing and Observing Multi-Agent Systems
- Governance: Registries, Versions and Ownership
- Protocols Evolve: Staying Current