Open Protocols with the Strands Agents SDK

This article explores how open agent protocols work together in the Strands Agents SDK, using a grocery delivery concierge example to demonstrate standardized boundaries between agent components.

• Model Context Protocol (MCP) standardizes how agents access external tools, data, and context through a shared interface
• Agent2Agent (A2A) enables agents to discover and delegate specialized tasks to peer agents while maintaining task ownership
• AG-UI defines a standard event vocabulary for streaming agent progress, state updates, and interactive components to user interfaces
• x402 provides HTTP-native micropayment support for agents to access premium data and services with automatic payment handling
• Strands SDK integrates MCP and A2A directly; AG-UI and x402 are available through complementary community packages
• Protocols compose together: MCP for tools, A2A for delegation, AG-UI for UI, x402 for payments
• Each protocol moves a specific responsibility out of the agent loop into infrastructure designed for that concern

By adopting open standards instead of proprietary protocols, Strands enables agents to evolve as the ecosystem changes while reducing custom integration code.