Gemini Enterprise can use your organization's Airlock MCP endpoint as a custom MCP server. Every tool call goes through your policies, approvals and audit trail, and each person signs in as themselves.
Airlock ships a built-in client ID for Gemini Enterprise, so there is nothing to register first and nothing that expires. Google's form asks for about ten values; this page gives the exact value for each one.
Before you start
- A Google Cloud admin for your Gemini Enterprise instance. Adding an MCP server needs the Discovery Engine Editor role (
roles/discoveryengine.editor) on the project. - Your organization's MCP URL. Open Settings → Account in the Control Room; your endpoint is shown there, ready to copy. It has the form
https://mcp.air-lock.ai/org/<org-slug>. - Gemini Enterprise allowed under Allowed AI clients. It is on by default. An Airlock admin can check under Settings → Security → Allowed AI clients.
Add the MCP server
- In the Google Cloud console, open Gemini Enterprise.
- In the navigation menu, select Data stores, then Create data store.
- Search for the custom MCP server connector, select it, and choose to add an MCP server.
- Under authentication, choose OAuth 2.0 and fill in the fields below, in the order Google shows them.
Check these before you continue:
- Enable PKCE Support must be ticked. Airlock requires PKCE on every sign-in, and without it the Airlock page refuses the request.
- Use HTTP Basic Authentication must be unticked. Google ticks it by default.
- Client Secret must be empty. The Gemini Enterprise client has no secret, and Airlock refuses a sign-in that presents one.
- Check the MCP Server URL character by character. Google does not let you change it after the data store is created; a mistyped URL means creating a new data store.
Copy the client ID whole. It is the same for every Airlock organization and it never changes.
Verify and finish
- Select Verify Auth. A pop-up opens on Airlock's sign-in page.
- Sign in with your Airlock account, using the same method you use for the Control Room.
- The consent screen names the app Gemini Enterprise and shows
vertexaisearch.cloud.google.comas the return address. Approve the connection. The pop-up closes and Google shows the check as passed. - Choose a location and a name for the data connector, and create it.
Verify Auth only proves the connection works; it does not connect anyone's account. Every person who uses the connector, the admin included, authorizes it once in the Gemini Enterprise web app (under Connectors, or when their first prompt needs Airlock) and signs in to Airlock there. Until the admin has done that, Reload custom actions cannot list Airlock's tools. Access tokens last 8 hours and refresh on their own, so people are not asked again during a normal working session.
Controlling who can connect
Gemini Enterprise appears under Settings → Security → Allowed AI clients with the same on/off switch and group scope as every other client. Turning it off stops new Gemini Enterprise sign-ins for the whole organization, even if Google's callback address is also in your approved redirect URIs; a group scope limits sign-ins to members of the selected groups. Both are checked at sign-in only, so people already connected keep their access until their session ends. See Controlling which AI clients may connect.