An A2A Server exposes one of your AI Agents (or a Team of agents) to other agent systems over the Agent-to-Agent (A2A) protocol, so external callers can discover its skills and send it requests through a standard agent card and messaging endpoint.
Overview
The A2A Servers screen is headed A2A Servers (with a count pill) — "Integrate External Agents using A2A protocol" — with a New A2A Server button. The table lists each server's A2A Server Name, Status (Live or Paused), Description, Agent (the exposed agent, with avatar), and Owner. Rows load 30 at a time, newest first, and clicking a row opens the server's configuration.
Before you've created any server, the screen shows an empty state: "Add your first A2A Server" — "Set up an A2A Server to integrate Agents or Workflows."
Creating a Server
Click New A2A Server to open the Add A2A Server dialog:
Field | Required | Details |
|---|---|---|
Name | Yes | Placeholder "Enter server name here". |
Description | No | Placeholder "Add a suitable description for your server". |
Select AI Agent or Team | Yes | "Expose your AI Agents / Team of AI Agents as A2A Agents." The agent (or team of agents) this server exposes. |
On save there's a brief pause while skills are generated, then you land in the new server's Skills section. The server starts Paused — deploy it from the header when ready.
What Happens Automatically
Saving a new server creates three things:
Created | Details |
|---|---|
API group | Named "A2A Server - <name>", at a URL path of |
Agent card | The A2A discovery document other agents read. Generated from your server's name and description with protocol version |
Skills | One per topic of the exposed agent, copied into the server's Skills section for you to refine. |
Editing a Server Later
Use Edit from the row menu or the server header's ⋯ menu. The Edit A2A Server dialog shows the same fields plus a warning:
Note: "Changes to this A2A server will override the existing configuration and may impact existing services." Swapping the exposed agent, in particular, changes what callers get.
Row Actions and Status
Live and Paused reflect whether the server is deployed. Live servers answer A2A requests; Paused servers don't. New servers start Paused — use Deploy in the server's header to go Live (and Undeploy to pause again). The row menu offers Edit and Delete, each shown only if you have that permission on the record. Deleting asks for confirmation and cannot be undone.