Skip to main content
A2A (Agent-to-Agent) is an open standard for cross-framework agent communication, originally developed by Google and now governed by the Linux Foundation. It gives AI agents a common language for interoperability, regardless of which framework or vendor built them. Lyzr supports A2A natively. You can call agents from LangGraph, CrewAI, Semantic Kernel, or any A2A-compliant platform as sub-agents inside a Lyzr Manager Agent, and you can expose Lyzr agents to external A2A clients. For the full protocol specification and SDKs, see the official A2A documentation.

​
How A2A relates to MCP

A2A and Model Context Protocol (MCP) serve different layers of an agentic system:
ProtocolRole
MCPAgent-to-tool communication. Standardizes how an agent connects to APIs, databases, and resources.
A2AAgent-to-agent communication. Standardizes how agents delegate tasks and exchange results with each other.
They are complementary. An agent can use MCP to call its tools and A2A to coordinate with peer agents.

​
What A2A enables in Lyzr

  • Call a LangChain or CrewAI agent as a sub-agent inside a Lyzr Manager Agent
  • Call a Lyzr agent from an external A2A client or orchestration layer
  • Build multi-framework pipelines where each agent is built and maintained independently
Agents communicate through A2A without sharing internal memory, tools, or proprietary logic. Each agent exposes only what it is asked to return.

​
How A2A works

  1. The Lyzr Manager Agent sends a task request to an external agent via its A2A server URL.
  2. The external agent processes the input using its own tools and logic.
  3. The external agent returns a structured response.
  4. Lyzr uses the response directly or passes it to the next step in the orchestration.
The external agent must conform to the A2A protocol specification and be accessible via a public URL.

​
Connecting an A2A agent in Studio

In a Manager Agent’s Build tab:
  1. Scroll to the Managerial Agent section.
  2. Select + A2A (next to + Agent).
  3. Enter the A2A server URL of the external agent.
  4. Write a Managerial Context that tells the manager when to invoke this external agent.
For full setup instructions, see Manager Agent.

​
Further reading