Agent Registry organizes your AI ecosystem into standardized resources so
that you can register, discover, and govern agents, MCP servers, endpoints, and
skills across a single project or a
[management boundary](https://docs.cloud.google.com/agent-registry/boundaries-and-topology.md.txt). Understanding
how Agent Registry separates writable `Service` resources from read-only
discovery resources, scopes resources across projects, and supports automatic
and manual registration helps you design and govern your registry.

To get started, see [Set up Agent Registry](https://docs.cloud.google.com/agent-registry/setup.md.txt). For more
information about the Agent Registry API, see the
[API reference documentation](https://docs.cloud.google.com/agent-registry/apis.md.txt).

## Agentic components

Agent Registry lets you register, discover, and govern the following types of
agentic components:

- **Agents**: autonomous AI actors that carry out specific tasks, invoke tools, and collaborate with other agents.
- **MCP servers** : programs that implement the [Model Context Protocol (MCP)](https://docs.cloud.google.com/mcp/overview.md.txt#how-mcp-works) to expose standardized data resources and tools. Tools are deterministic functions exposed by an MCP server that agents can invoke to perform specific actions.
- **Endpoints**: target URLs, typically REST APIs, accessed by an agent. By abstracting these destinations into manageable resources, Agent Registry lets you centrally govern which external APIs your agents can access.
- **Skills** : modular capabilities that extend what an agent can do. Standalone skills are packages of instructions and optional scripts governed directly in the registry. A2A skills are capability descriptions on an agent's Agent Card that tell other agents when and how to communicate with it. For more information, see [Skills architecture](https://docs.cloud.google.com/agent-registry/skills-architecture.md.txt).

## Service resources and discovery resources

How Agent Registry represents a component depends on its component type and
registration model. For more information about component lifecycles and
discovery, see
[Component lifecycle and discovery](https://docs.cloud.google.com/agent-registry/component-lifecycle-and-discovery.md.txt).

### Agents, MCP servers, and endpoints

Regardless of whether an agent, an MCP server, or an endpoint is registered
automatically or manually, Agent Registry represents it as a read-only
`Agent`, `McpServer`, or `Endpoint` discovery resource. Consumers, such as
orchestrator agents, client applications, and developers, use these discovery
resources to list, search, and view registered components.

For [automatically registered](https://docs.cloud.google.com/agent-registry/data-model.md.txt#automatic-registration) components,
Agent Registry ingests metadata directly from supported runtimes and creates
the discovery resource without a `Service` resource.

When you [manually register](https://docs.cloud.google.com/agent-registry/data-model.md.txt#manual-registration) an agent, an MCP server, or
an endpoint, Agent Registry separates management operations from component
discovery by creating the following items:

- **A writable `Service` resource** : stores the component's metadata, including the type of agentic component, its interface URL, description, protocol binding, and capability specification. You create, update, or delete the `Service` resource for management operations such as updating metadata or unregistering the component, without modifying or deleting the underlying deployment.
- **A discovery resource** : when you create or update a `Service` resource, Agent Registry reads the metadata and automatically creates or updates an `Agent`, `McpServer`, or `Endpoint` discovery resource that represents the component in your registry.

The specification flags you use when creating a `Service` resource determine the
resulting read-only resource collection:

| Flags | Resource collection | Use case | Valid values |
|---|---|---|---|
| `--agent-spec-type` `--agent-spec-content` | `Agent` resource in `agents` collection | Remote A2A-compliant or standard REST agents | `a2a-agent-card`, `no-spec` |
| `--endpoint-spec-type` `--endpoint-spec-content` | `Endpoint` resource in `endpoints` collection | External target REST APIs or service URLs | `no-spec` |
| `--mcp-server-spec-type` `--mcp-server-spec-content` | `McpServer` resource in `mcp-servers` collection | External Model Context Protocol (MCP) servers | `tool-spec`, `no-spec` |

These flag pairs are mutually exclusive; specifying flags from more than one
pair returns an error. If you specify the flag pair for the wrong component
type, Agent Registry creates the discovery resource in the collection that
matches the flag you specified. For example, passing `--agent-spec-type=no-spec`
when registering an endpoint creates an `Agent` resource instead of an
`Endpoint` resource, so type-specific queries and governance policies won't
apply as expected.

### Standalone skills

Standalone [skills](https://docs.cloud.google.com/agent-registry/skills-architecture.md.txt) don't use separate
`Service` resources. Instead, you register, version, and query skills directly
using top-level `Skill` resources, child `SkillRevision` resources, and
`Publisher` resources.

Security issues detected during skill scanning are exposed as read-only
`Finding` resources. For more information, see [Scan skills for security issues](https://docs.cloud.google.com/agent-registry/scan-skills.md.txt).

## Cross-project data model

> [!WARNING]
>
> **Preview**
>
>
> This product or feature is
>
> subject to the "Pre-GA Offerings Terms" in the General Service Terms section
> of the [Service Specific
> Terms](https://docs.cloud.google.com/terms/service-terms#1).
>
> Pre-GA products and features are available "as is" and might have limited support.
>
> For more information, see the
> [launch stage descriptions](https://cloud.google.com/products/#product-launch-stages).

When you configure a
[management boundary](https://docs.cloud.google.com/agent-registry/boundaries-and-topology.md.txt),
Agent Registry centralizes discovery and governance across all member projects
from your
[management project](https://docs.cloud.google.com/agent-registry/boundaries-and-topology.md.txt#management-project).

When you query, list, or search for resources from the management project,
Agent Registry applies the following scoping rules to provide a consolidated
catalog without duplicating resources or creating endpoint collisions:

| Resource category | Scope in a management boundary | Description |
|---|---|---|
| **Auto-discovered resources** | Aggregated from member projects | Agents and MCP servers automatically discovered in member projects are aggregated into the management project view when you list them or search for them in a location on the management project. When you view, list, or search for an agent or MCP server, you can specify either the management project ID or the member project ID in the request. The [resource name](https://docs.cloud.google.com/agent-registry/identity-and-identifiers.md.txt#resource-names) preserves the ID that Agent Registry assigns to the component and uses the project specified in the request. |
| **Manually registered resources** | Scoped to the project where they are created | Custom agents, external MCP servers, and endpoints manually registered as `Service` resources are scoped to the project in which they are created. Create them in the management project to make them visible across the management boundary, or in a member project to keep them visible only within that single project. |
| **Bindings** | Scoped to the project where they are created | `Binding` resources are scoped to the project in which they are created. Create them in the management project for boundary-wide visibility, or in a member project for single-project visibility. |
| **Standalone skills and publishers** | Scoped to the project where they are created | Custom standalone `Skill`, `SkillRevision`, `Publisher`, and `Finding` resources are scoped to the project in which they are created and aren't aggregated from member projects into the management project. Google-managed standalone skills are discoverable across all projects automatically when you set up Agent Registry. |
| **AI applications** | Scoped to the project where they are created | Read-only `AiApplication` resources and their linked component views are scoped to the project and location where the application was created. |

## Supported products and components

Agent Registry categorizes supported products and components by how they are
registered: automatically or manually.

### Automatic registration

Agent Registry automatically discovers and ingests supported
Google Cloud workloads deployed within your project or across
member projects in your management boundary. For agents that implement the open
Agent2Agent (A2A) protocol, the registry automatically extracts their A2A skills
and capabilities from their Agent Card. Google-managed standalone skills are
also discoverable across all projects when you set up Agent Registry.

The following table lists the products and components that Agent Registry
registers automatically:

| Component type | Supported products |
|---|---|
| **Agents** | - [Agent Runtime on Gemini Enterprise Agent Platform](https://docs.cloud.google.com/agent-registry/automatic-registration.md.txt#agent-engine) - [Google Workspace](https://docs.cloud.google.com/agent-registry/automatic-registration.md.txt#built-in-agents) - [Gemini Enterprise](https://docs.cloud.google.com/agent-registry/automatic-registration.md.txt#built-in-agents) - [Google Kubernetes Engine (GKE)](https://docs.cloud.google.com/agent-registry/automatic-registration.md.txt#gke) deployments including a specific functional type label - [Cloud Run](https://docs.cloud.google.com/agent-registry/automatic-registration.md.txt#cloud-run) workloads configured with a specific functional type flag |
| **MCP servers** | - [Google and Google Cloud remote MCP servers](https://docs.cloud.google.com/mcp/supported-products.md.txt) - [GKE](https://docs.cloud.google.com/agent-registry/register-mcp-servers.md.txt#gke-mcp) deployments including a specific functional type label - [Cloud Run](https://docs.cloud.google.com/agent-registry/register-mcp-servers.md.txt#cloud-run-mcp) services configured with a specific functional type flag |
| **Skills** | [Google-managed skills](https://github.com/google/skills/tree/main) are discoverable from all projects |

### Manual registration

*Remote* components are agents, MCP servers, or endpoints hosted outside your
[governance project](https://docs.cloud.google.com/agent-registry/overview.md.txt#governance-project) or
[management boundary](https://docs.cloud.google.com/agent-registry/boundaries-and-topology.md.txt), such as in
separate Google Cloud projects without a boundary, on-premises
infrastructure, or external clouds. You manually register those remote
components in the governance project using a `Service` resource. You also use a
`Service` resource to manually register components on unsupported runtimes or
for agents that don't implement the A2A protocol. For custom standalone skills,
you use a `Skill` resource.

The following table lists the products and components that you register
manually:

| Component type | Supported resources |
|---|---|
| **Agents** | [Remote agents](https://docs.cloud.google.com/agent-registry/manual-registration.md.txt) deployed on Compute Engine, GKE, Cloud Run, on-premises systems, or external clouds |
| **MCP servers** | [Custom agentic components on unsupported runtimes or external MCP servers](https://docs.cloud.google.com/agent-registry/register-mcp-servers.md.txt#register-external-servers) |
| **Endpoints** | External target REST APIs or service URLs governed as endpoints |
| **Skills** | [Your own standalone skills](https://docs.cloud.google.com/agent-registry/register-skills.md.txt) authored by your organization |

## What's next

- Learn about [Identity and identifiers](https://docs.cloud.google.com/agent-registry/identity-and-identifiers.md.txt).
- Learn about [Component lifecycle and discovery](https://docs.cloud.google.com/agent-registry/component-lifecycle-and-discovery.md.txt).
- Learn about [cross-project boundaries](https://docs.cloud.google.com/agent-registry/boundaries-and-topology.md.txt).
- Learn about [Skills architecture](https://docs.cloud.google.com/agent-registry/skills-architecture.md.txt).
- [Set up Agent Registry](https://docs.cloud.google.com/agent-registry/setup.md.txt).