As a company builds more agents, tools, and MCP servers, nobody can find them, so teams rebuild what already exists. Registry is a shared, searchable catalog: people publish their agents and tools, an approver vets them, and then anyone, a developer or even another agent, can search and reuse them.
New to these words? Read chapter 02 "Key terms" (MCP, A2A, tool, agent). Note: in preview.Registry is a managed catalog where your organization publishes its agents, tools, MCP servers, and skills, so they can be found and reused instead of rebuilt. An approval step keeps the catalog clean: only vetted entries show up in search. Both people and agents can search it.
An admin makes a catalog and sets the login (IAM or JWT) and whether approval is automatic.
A publisher adds an entry describing an agent, tool, MCP server, or skill.
A curator approves or rejects it (or it auto-approves). Draft to Pending to Approved.
Anyone searches and finds only Approved entries, then reuses them.
Deprecate an entry when it is no longer used, so it drops out of search.
Tool servers, checked against the MCP schema.
A2A agents, with their agent card.
Reusable agent skills, with documentation.
Anything else, with your own metadata.