Connect Gemini Enterprise to C1

Google Gemini Enterprise calls the C1 MCP gateway as a tool source. Your users ask Gemini Enterprise a question, Gemini calls a C1 tool on their behalf, and C1 enforces your access policies against that person’s identity. Tool calls are attributed to individual users, not to a shared service account.

Activation required. AI access management must be enabled for your tenant before you can use it. To get started, contact the C1 support team for a walkthrough.

What you’ll do

Setup spans two products and three roles. Plan for a Google Cloud administrator with organization-level permissions to be available.

Stage	Where	Who
Get the MCP server URL	C1	C1 administrator
Enable APIs and adjust organization policy	Google Cloud	Google Cloud administrator
Create the data store and authorize	Gemini Enterprise	Gemini Enterprise administrator
Enable tools	Gemini Enterprise	Gemini Enterprise administrator

Several Google Cloud steps have gcloud equivalents, and this page gives both wherever one exists. The command line is faster and easier to repeat across environments, so use it where you can. Creating the data store and enabling tools have no API equivalent and must be done in the Google Cloud console.

Before you begin

Gather these before you start.

AI access management must be enabled for your tenant. See Enable AI access management.
A Google Cloud project with a Gemini Enterprise app already created.
The gcloud CLI, authenticated with gcloud auth login.
A Google Cloud administrator who can grant roles/orgpolicy.policyAdmin at the organization or folder level. Project Owner is not sufficient for the organization policy change in Allow custom MCP data connectors.
The beta component, which the optional gateway commands need:
gcloud components install beta
Install this before you start. Without it, gcloud beta commands stop at an interactive install prompt. In a script, that looks like a hang rather than an error.

Required roles

Grant these roles on the Google Cloud project.

Role	Why
`roles/serviceusage.serviceUsageAdmin`	Enable the required APIs
`roles/discoveryengine.admin`	Create the data store and authorize the connection
`roles/orgpolicy.policyAdmin`	Allow custom MCP data connectors. Must be granted at the organization or folder level
`roles/agentregistry.admin`	Register the server in Agent Registry. Only for Optional: Publish through Agent Registry
`roles/compute.networkAdmin` and `roles/networksecurity.admin`	Create the gateway and its policy. Only for the optional Agent Registry path

Get your C1 MCP server URL

Every C1 tenant has its own MCP server URL and its own OAuth endpoints.

In C1, open your user profile menu and select AI & API > AI connections.

Copy the MCP server URL at the top of the page. It looks like this:

https://<your-tenant>-mcp.conductor.one/v1

You now have the MCP server URL for your tenant. Your OAuth endpoints follow from your tenant subdomain. Confirm them against your tenant’s published metadata:

curl -s https://YOUR_TENANT-mcp.conductor.one/.well-known/oauth-authorization-server

You need three values from that response.

Value	For a tenant named `acme`
MCP server URL	`https://acme-mcp.conductor.one/v1`
Authorization URL	`https://acme.conductor.one/auth/v1/authorize`
Token URL	`https://acme.conductor.one/auth/v1/token`

Check your region requirements

Your Gemini Enterprise app location determines every other region you pick. Find it at the top of the Apps page in the Google Cloud console, next to Current location.

App location	Agent Gateway region	Agent Registry region
`global`	`us-central1`	`us-central1` or `global`
`us`	`us-central1`	`us-central1`
`eu`	`europe-west1`	`europe-west1`

Agent Registry does not support the us and eu multi-region locations. Use a specific region such as us-central1, or use global. These regions matter only if you follow Optional: Publish through Agent Registry. When regions do not line up, the server never appears in the data store list and no error explains why.

Enable the Google Cloud APIs

Enable the APIs that back Gemini Enterprise data connectors and their tools.

In the Google Cloud console, go to APIs & Services > Library.

Search for each API by name and select Enable.

From the command line:

gcloud services enable \
  discoveryengine.googleapis.com \
  connectors.googleapis.com \
  integrations.googleapis.com \
  secretmanager.googleapis.com \
  iam.googleapis.com \
  orgpolicy.googleapis.com \
  --project=YOUR_PROJECT_ID

To confirm which APIs are enabled:

gcloud services list --enabled --project=YOUR_PROJECT_ID

Your project can now create data connectors and expose their tool actions.

connectors.googleapis.com, integrations.googleapis.com, and secretmanager.googleapis.com back the tool actions a data connector exposes. Google’s setup documentation does not list them, and tool discovery fails without them.

Allow custom MCP data connectors

Google Cloud blocks custom MCP data connectors by default. Creating the data store fails at the final step until an administrator turns the constraint off:

Operation denied by org policy on resource '...':
["constraints/discoveryengine.managed.disableCustomMcpServerConnector":
"This constraint, when enforced, restricts the creation of data connectors
that use a custom MCP server as their data source."]

Save this as policy.yaml:

name: projects/YOUR_PROJECT_ID/policies/discoveryengine.managed.disableCustomMcpServerConnector
spec:
  rules:
    - enforce: false

Then apply it:

gcloud org-policies set-policy policy.yaml

Confirm the change took effect:

gcloud org-policies describe \
  discoveryengine.managed.disableCustomMcpServerConnector \
  --project=YOUR_PROJECT_ID --effective

The effective policy reports enforce: false, and your project can create custom MCP data connectors.

Allow several minutes for the policy to propagate. Until it does, the console returns the same denial message, so a failure right after you apply the policy does not mean the policy is wrong. Setting this policy requires roles/orgpolicy.policyAdmin at the organization or folder level.

Your organization may also restrict which external hosts a data connector can reach. If so, allow the two hostnames your tenant uses, <your-tenant>-mcp.conductor.one and <your-tenant>.conductor.one. Use hostnames only, not full URLs.

Get the OAuth client ID

Gemini Enterprise authenticates each user to C1 with the OAuth 2.0 authorization code flow. It needs an OAuth client that already exists, because it does not register itself the way Claude Code and Cursor do. C1 publishes a client metadata document for Gemini Enterprise. Use its URL as the client ID:

https://<your-tenant>.conductor.one/auth/v1/client-metadata/gemini-enterprise

This client has no secret, so nothing expires and nothing needs rotating. Configure it once and it keeps working. Do not create a client through C1’s dynamic registration endpoint for this integration: those secrets expire one hour after they are issued, and re-registering does not extend the expiry.

Create the data store

Connect the C1 MCP gateway to your Gemini Enterprise app.

The data connector name generates an ID that cannot be changed later. Decide the name before you begin this procedure.

In the Google Cloud console, open Gemini Enterprise and select your app.

Select Connected data stores > New data store.

In Select a data source, search for Custom MCP.

Select Add MCP server on the Custom MCP Server card.

For Select your authentication method, choose OAuth 2.0.

Complete the authentication fields:

Field	Value
MCP Server URL	`https://<your-tenant>-mcp.conductor.one/v1`
Authorization URL	`https://<your-tenant>.conductor.one/auth/v1/authorize`
Authorization URL Parameters	`&resource=https://<your-tenant>-mcp.conductor.one/v1`
Token URL	`https://<your-tenant>.conductor.one/auth/v1/token`
Client ID	`https://<your-tenant>.conductor.one/auth/v1/client-metadata/gemini-enterprise`
Client Secret	Leave empty
Scopes	`openid profile email offline_access`
Enable PKCE Support	Selected
Use HTTP Basic Authentication	Cleared

Select Verify Auth. A window opens for you to sign in through your identity provider and authorize the connection.

Select Continue.

Enter a Data connector name.

Select Create.

The form shows Successfully logged in after you authorize, and the connector reaches the Active state a minute or two after you create it. Four details on that form are easy to get wrong:

Clear Use HTTP Basic Authentication. It is selected by default. Leaving it selected sends the client ID and secret in an Authorization header, which does not work for a client that has no secret.
Leave Client Secret empty. The field is optional even though Client ID, Authorization URL, and Token URL are marked required.
Include offline_access in the scopes. Without it C1 issues no refresh token, and users reauthorize every time their access token expires.
Set Authorization URL Parameters. C1 binds tokens to a specific resource, so the resource parameter scopes the issued token to your MCP endpoint.

Enable the tools

Gemini Enterprise imports every tool in a disabled state. Turn on the ones you want available to users.

Wait for the connector state to reach Active before you start. The reload fails while the connector is still creating.

Open the data store and select the Actions tab.

Select Reload custom actions. Gemini Enterprise queries your MCP server for its current tool list.

Select the tools to expose.

Select Enable actions.

The tools you selected are now available to users in your Gemini Enterprise app. Google recommends enabling no more than 100 actions per data store.

Verify the Gemini Enterprise connection

Tool discovery runs before authentication is proven, so seeing tools listed does not confirm your credentials are correct. You confirm the setup only when a user successfully calls a C1 tool.

Open your Gemini Enterprise app as an end user and ask a question that needs a C1 tool, such as “Who has access to Salesforce?”

Authorize the connection when prompted. Sign in through your identity provider and approve.

As that same user in C1, open the user profile menu and select AI & API > AI connections. The Gemini Enterprise connection appears. Administrators can see connections for everyone under AI access management > AI clients.

In C1, go to Settings > System log and filter on activity_name starts with "mcp_". Tool calls appear as mcp_tool_call events attributed to the individual user.

The connection is working, and every tool call is attributed to the user who made it.

Optional: Publish through Agent Registry

Agent Registry gives your organization a catalog of approved MCP servers, and Agent Gateway applies policy to agent traffic. Neither is required to connect Gemini Enterprise to C1, and the setup in the previous sections works without them. Add them when you want the C1 gateway to appear in a shared catalog alongside your other approved servers.

Gemini Enterprise supports only Agent-to-Anywhere (egress) mode. Google’s documentation states that traffic between Gemini Enterprise agents and their data connectors does not trigger Agent Gateway policy enforcement, so treat this path as catalog publishing rather than traffic governance.

Enable the additional APIs

Agent Registry and Agent Gateway need networking and platform APIs beyond the ones you already enabled.

gcloud services enable \
  agentregistry.googleapis.com \
  networkservices.googleapis.com \
  networksecurity.googleapis.com \
  compute.googleapis.com \
  dns.googleapis.com \
  iap.googleapis.com \
  aiplatform.googleapis.com \
  modelarmor.googleapis.com \
  --project=YOUR_PROJECT_ID

iap.googleapis.com is missing from Google’s published list of required APIs, and the authorization extension fails without it.

Register the server

Describe the tools you want catalogued in a toolspec.json file. Each tool needs name, description, and inputSchema, and the file is limited to 10 KB.

{
  "tools": [
    {
      "name": "find_api_objects",
      "description": "Query C1 objects by identifiers, search text, or filters.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "object_type": { "type": "string" },
          "query": { "type": "string" }
        },
        "required": ["object_type"]
      },
      "annotations": {
        "title": "Find API Objects",
        "readOnlyHint": true,
        "idempotentHint": true
      }
    }
  ]
}

inputSchema is required on every tool, even though Google’s published example omits it. Without it, registration fails with invalid MCP tool spec content: tools.0: inputSchema is required.

gcloud agent-registry services create c1-mcp-gateway \
  --project=YOUR_PROJECT_ID \
  --location=us-central1 \
  --display-name="C1 MCP Gateway" \
  --mcp-server-spec-type=tool-spec \
  --mcp-server-spec-content="$(cat toolspec.json)" \
  --interfaces="url=https://YOUR_TENANT-mcp.conductor.one/v1,protocolBinding=jsonrpc"

Agent Registry catalogs the server and projects it as a read-only entry that consumers can discover.

Create the gateway

The gateway routes and governs outbound agent traffic for the registry you just populated. Save this as gateway.yaml:

name: c1-agent-gateway
protocols:
  - MCP
googleManaged:
  governedAccessPath: AGENT_TO_ANYWHERE
registries:
  - //agentregistry.googleapis.com/projects/YOUR_PROJECT_ID/locations/us-central1

Then import it:

gcloud network-services agent-gateways import c1-agent-gateway \
  --source=gateway.yaml \
  --location=us-central1 \
  --project=YOUR_PROJECT_ID

The gateway takes a minute or two to create.

The registries value must start with //agentregistry.googleapis.com/. A plain projects/.../locations/... path is rejected with does not match the pattern. There is no separate registry resource to create, because the registry is implicit for each project and location.

Bind the gateway to your app

Creating the gateway is not enough. Each Gemini Enterprise app must point at it explicitly. Until you do this, the data store list shows a Configure Agent Gateway prompt and no registered servers appear.

In your Gemini Enterprise app, go to Security > Configuration.

Under Agent Gateway configuration, enter the gateway resource name:

projects/<your-project-id>/locations/us-central1/agentGateways/c1-agent-gateway

Select Save.

From the command line:

curl -X PATCH \
  -H "Authorization: Bearer $(gcloud auth print-access-token)" \
  -H "Content-Type: application/json" \
  -H "X-Goog-User-Project: YOUR_PROJECT_ID" \
  -d '{"agentGatewaySetting":{"defaultEgressAgentGateway":{"name":"projects/YOUR_PROJECT_ID/locations/us-central1/agentGateways/c1-agent-gateway"}}}' \
  "https://discoveryengine.googleapis.com/v1/projects/YOUR_PROJECT_ID/locations/global/collections/default_collection/engines/YOUR_ENGINE_ID?updateMask=agentGatewaySetting.defaultEgressAgentGateway.name"

The console reports Agent gateway configuration saved, and the C1 MCP Gateway card then appears under MCP servers when you create a data store.

Troubleshoot Gemini Enterprise connection errors

Symptom	Cause	Fix
`Operation denied by org policy ... disableCustomMcpServerConnector`	The organization policy blocks custom MCP data connectors.	Turn the constraint off and wait for propagation. See Allow custom MCP data connectors.
We encountered some problems during authentication	The redirect URI in the client metadata document does not match what Gemini Enterprise sent.	Use the C1-published client ID from Get the OAuth client ID.
Failed to reload custom actions	The connector is still creating, or the tool actions APIs are not enabled.	Wait for the connector state to reach Active, then confirm `connectors.googleapis.com`, `integrations.googleapis.com`, and `secretmanager.googleapis.com` are enabled.
Authorization works, then breaks about an hour later	The client was created through dynamic registration, and its secret expired.	Use the C1-published client ID. See Get the OAuth client ID.
Users reauthorize constantly	`offline_access` is missing from the scopes, so C1 issues no refresh token.	Add `offline_access` and have users reconnect.
`401` from the MCP server	The token is missing or not bound to the right resource.	Set Authorization URL Parameters to `&resource=https://<your-tenant>-mcp.conductor.one/v1`.
The form rejects an empty Client Secret	Use HTTP Basic Authentication is still selected.	Clear that checkbox. See Create the data store.
C1 MCP Gateway does not appear under MCP servers	The gateway is not bound to the app, or the regions do not line up.	See Bind the gateway to your app and Check your region requirements.
A `gcloud beta` command appears to hang	The `beta` component is not installed and the CLI is waiting at an install prompt.	Run `gcloud components install beta`, or add `--quiet`.

Gemini Enterprise integration limitations

These constraints come from Gemini Enterprise and Google Cloud.

Gemini Enterprise supports egress (Agent-to-Anywhere) mode only.
MCP servers must use StreamableHTTP transport. Server-sent events are not supported.
VPC Service Controls and Private Service Connect are not supported for custom MCP data stores.
The MCP server needs a certificate from a publicly trusted authority. Self-signed certificates are rejected.
A gateway supports at most 5,000 registered resources.

Frequently asked questions about connecting Gemini Enterprise

Does a shared client ID mean Gemini Enterprise sees everyone's data?

No. The client ID identifies Gemini Enterprise as an application, not as a user. Every person authorizes individually through your identity provider and receives their own token. C1 evaluates each tool call against that person’s access profiles, and their activity appears under their own identity in the system log.

Why is the Client Secret field empty?

The client is a public OAuth client with no secret. Client ID Metadata Document clients cannot use shared secrets, so C1 ignores the field. Security comes from the authorization code flow with PKCE, which you turn on with Enable PKCE Support.

Do I need Agent Gateway?

No. Connecting Gemini Enterprise to C1 works without it. Agent Gateway and Agent Registry publish the C1 gateway in a shared catalog of approved servers. Google’s documentation notes that Gemini Enterprise data connector traffic does not trigger Agent Gateway policy enforcement, so adding it does not change how tool calls are governed. C1 governs the tool calls.

How do I cut off access in a hurry?

In C1, open AI access management > AI clients, find the Gemini Enterprise client, and use the kill switch. It revokes all tokens for that client immediately. See Manage AI clients.

Can I see what tools Gemini Enterprise called?

Yes. C1 records every MCP session and tool call in the system log. Filter on activity_name starts with "mcp_" to see sessions and calls, each attributed to the user who made them. See Audit AI tool usage.

These pages cover the C1 side of the integration.

Manage AI clients covers lifecycle states, the kill switch, and allowed client types.
Connect to the C1 MCP covers the same gateway from desktop AI assistants.
AI access management covers the access profiles and toolsets that decide what each user’s tools can do.
Audit AI tool usage covers reviewing MCP activity in the system log.

Overview

C1 MCP

Workforce & app access

AI agent governance

Risk & intelligence

Cloud infrastructure access

Platform & administration

Connect Gemini Enterprise to C1

What you’ll do

Before you begin

Required roles

Get your C1 MCP server URL

Check your region requirements

Enable the Google Cloud APIs

Allow custom MCP data connectors

Get the OAuth client ID

Create the data store

Enable the tools

Verify the Gemini Enterprise connection

Optional: Publish through Agent Registry

Enable the additional APIs

Register the server

Create the gateway

Bind the gateway to your app

Troubleshoot Gemini Enterprise connection errors

Gemini Enterprise integration limitations

Frequently asked questions about connecting Gemini Enterprise

​What you’ll do

​Before you begin

​Required roles

​Get your C1 MCP server URL

​Check your region requirements

​Enable the Google Cloud APIs

​Allow custom MCP data connectors

​Get the OAuth client ID

​Create the data store

​Enable the tools

​Verify the Gemini Enterprise connection

​Optional: Publish through Agent Registry

​Enable the additional APIs

​Register the server

​Create the gateway

​Bind the gateway to your app

​Troubleshoot Gemini Enterprise connection errors

​Gemini Enterprise integration limitations

​Frequently asked questions about connecting Gemini Enterprise

​Pages related to governing AI tool access

What you’ll do

Before you begin

Required roles

Get your C1 MCP server URL

Check your region requirements

Enable the Google Cloud APIs

Allow custom MCP data connectors

Get the OAuth client ID

Create the data store

Enable the tools

Verify the Gemini Enterprise connection

Optional: Publish through Agent Registry

Enable the additional APIs

Register the server

Create the gateway

Bind the gateway to your app

Troubleshoot Gemini Enterprise connection errors

Gemini Enterprise integration limitations

Frequently asked questions about connecting Gemini Enterprise

Pages related to governing AI tool access