Agent Registry overview

Agent Registry lets you register, discover, and govern agentic components, including AI agents, Model Context Protocol (MCP) servers and tools, endpoints, and standalone skills, across your Google Cloud environment. By consolidating these components into a single registry, you can help eliminate fragmented tool access, isolated data, and redundant integrations across your AI deployments.

You can view and manage registered components as resources in Agent Registry. For more information about Agent Registry resources, see Agent Registry data model.

Why use Agent Registry?

Agent Registry is structured around three primary goals to help you manage your agents, MCP servers, endpoints, and skills:

  • Accelerate development: discover and reuse existing agentic capabilities such as A2A skills, standalone skills, and MCP tools across your organization. You can query the registry to identify and use available capabilities, removing the need to create custom integrations for each new process.
  • Simplify integration: use standardized MCP or Agent2Agent (A2A) protocols to locate and connect to functional endpoints, and help reduce infrastructure management overhead.
  • Support governance: enforce security through network and access policies and boundaries across your agentic fleet. Other services can use the identifiers of your agentic components to define permissions and control which agents can access your data, including centralizing agent metadata across multiple Google Cloud projects for governance with Agent Gateway.

Use Agent Registry with Gemini Enterprise Agent Platform

Agent Registry is designed to work alongside other services in Agent Platform to secure and govern agent interactions at runtime.

In Agent Platform, Agent Registry maintains the authoritative registry of agents, MCP servers, tools, skills, and external endpoints that you need to govern, and generates the identifiers and resource names referenced by discovery clients and security policies.

Identity and Access Management (IAM) access policies bind agent principals to the target resources registered in Agent Registry. You can provision verifiable agent principals for workloads through Agent Identity and manage credentials for external tools through auth providers.

Agent Gateway uses your IAM and content security policies to determine where to enforce policies at runtime as the network enforcement point for agent traffic. Before routing requests between agents, MCP servers, or external endpoints, Agent Gateway queries Agent Registry and evaluates your configured IAM and content security policies.

Define the governance project for a central registry

In Agent Registry, a governance project is the Google Cloud project where you enable the Agent Registry API to centrally catalog, discover, and govern your agentic components. You run discovery queries, manage registry resources, and configure access and egress policies in this project.

Depending on your architecture, you can use a governance project in a single-project or cross-project configuration:

  • Single-project configuration: you deploy your AI workloads and enable Agent Registry in the same Google Cloud project. Agent Registry automatically registers supported workloads deployed in that project, and you can manually register custom components or external endpoints in the same project.
  • Cross-project configuration: you designate a central Google Cloud project as your governance project where Agent Registry and shared governance services such as Agent Gateway are enabled, while your AI workloads run in separate Google Cloud projects, on-premises environments, or external clouds. In Agent Registry, components hosted outside the governance project are referred to as remote components. Because automatic registration only discovers supported workloads deployed in the governance project, you manually register remote components in the central registry using Service resources. For more information, see Cross-project registration considerations.

What's next