How A2A relates to MCP
A2A and Model Context Protocol (MCP) serve different layers of an agentic system:
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
How A2A works
- The Lyzr Manager Agent sends a task request to an external agent via its A2A server URL.
- The external agent processes the input using its own tools and logic.
- The external agent returns a structured response.
- Lyzr uses the response directly or passes it to the next step in the orchestration.
Connecting an A2A agent in Studio
In a Manager Agent’s Build tab:- Scroll to the Managerial Agent section.
- Select + A2A (next to + Agent).
- Enter the A2A server URL of the external agent.
- Write a Managerial Context that tells the manager when to invoke this external agent.
Import an A2A agent into the Registry
Alongside calling an external agent from a Manager Agent, you can import an A2A agent into the Agent Registry as a standalone agent. An imported agent behaves like any other agent in your workspace. To import an agent, open the Agent Registry, open the New menu in the top right, and select Import (A2A). Enter the A2A server URL of the external agent, and Lyzr reads the server and imports the agent into the Registry automatically, where it appears under the External tab.
- The imported agent persists in the Registry until you delete it manually.
- Full trace visibility and monitoring are available for the imported agent.
- You can evaluate any two agents against each other, including an imported agent against a native one.
- The agent is available through its API endpoint and as an A2A server out of the box, with no extra setup.