Use Agent Registry with Gemini Enterprise

Use this path when your organization wants a central catalog of MCP servers and tools or Agent Gateway policies for Gemini Enterprise traffic. To load tools directly from Glean when you reload custom actions, follow the direct data store setup.

Register Gemini Tools

Agent Registry catalogs server endpoints and tool definitions. It does not run Glean's tools. For an external server, Agent Registry does not read the live tool list. Glean's Copy toolspec provides the snapshot to register.

Keep the Gemini Tools server to 10 or fewer tools and agents for this registration. Glean disables Copy toolspec above that count because Agent Registry retains only the first 10. The limit applies to this export, not the live server or the direct data store.

1. In the Glean Admin console, confirm the /managed/gemini server (Gemini Tools) is enabled. Copy its URL and click Copy toolspec under Gemini tool specification.
2. In Google Cloud, register the external MCP server. Enter the URL, paste the JSON into Tool specification, select the tools, and save. Choose a Registry location that supports manual registration; the us and eu multi-regions do not.

The toolspec contains no credentials. Copy it again after changing the server's tools or connecting new sources. Registration alone does not connect the server to a Gemini Enterprise app. You do not need Agent Gateway if you only want a Registry entry.

Import into a Gemini Enterprise app

Agent Gateway is required for this import. Follow Google's Gateway routing guide to associate the Registry with a Gateway in a compatible region and bind the Gateway to your Gemini Enterprise app. Binding routes all the app's traffic, including LLM calls, through Agent Gateway.

1. On Glean's Third-party OAuth page, create a static Gemini MCP client with the authorization code grant and redirect URL https://vertexaisearch.cloud.google.com/oauth-redirect. Select the required scopes and save the client ID and secret when you create it.
2. In your Gemini Enterprise app, add the server from Agent Registry. Select OAuth 2.0 and enter the Gemini Tools URL, Glean authorization and token URLs, and the client ID and secret.
3. To govern traffic to Glean, configure Agent Gateway egress policies.

Users still authorize Glean individually, and Glean applies their permissions to every result.