Distribution / Distributing connectors to Gemini
Distributing connectors to Gemini
Find out which Gemini product an organization uses, then connect it to a Speakeasy project gateway: once for a whole Gemini Enterprise team or app, or per person in Gemini CLI.
Google sells several products named Gemini, and each handles custom MCP connectors differently. In some, an administrator adds a connector once for everyone. In others, each person adds it, and in one, custom connectors aren’t available yet.
In every product that supports custom connectors, distribute the project gateway URL. One connector reaches every MCP server in the project that each person can access, and each person signs in with their own Speakeasy account. Copy the URL from the project gateway page in the Speakeasy dashboard. It has this form:
https://<organization-host>/mcp/gateway/<organization-slug>/projects/<project-slug>Choose a product to see how to distribute connectors to it.
Gemini in Google Workspace
Section titled “Gemini in Google Workspace”Custom connectors aren’t available for work accounts yet. Google currently offers them only on personal Google accounts. The Gemini Apps help page for custom apps says:
For now, this feature isn’t available if you sign in with a work or school Google Account.
The Google Workspace Admin console has no setting that turns custom connectors on. Under Apps > Google Workspace Marketplace apps, administrators can only turn Google’s own partner connectors on or off.
Don’t ask people to add the connector from personal Google accounts. It works, but it moves company data outside the organization’s Workspace controls.
Until Google supports custom connectors on work accounts, use one of these:
- Gemini Enterprise. A separate license that lets an administrator add the connector once for everyone. See Gemini Enterprise Business edition or Gemini Enterprise Standard, Plus, and Frontline.
- Gemini CLI. Works today with any Google account, for people who work in a terminal. See Gemini CLI.
Gemini Enterprise Business edition
Section titled “Gemini Enterprise Business edition”A team administrator adds the connector once in the Gemini Enterprise app, then turns it on for the team. Google marks custom MCP connections in Business edition as Pre-GA.
Register Gemini with the gateway
Section titled “Register Gemini with the gateway”Paste the project gateway URL below to generate a curl command that registers Gemini as an OAuth client of the gateway. Run it in a terminal to get the client ID and secret.
Add the connector
Section titled “Add the connector”- Sign in at business.gemini.google as a team administrator.
- Click Settings & help, select the team, and open Manage team > Connected apps.
- Click Add MCP Server.
- Under MCP info, enter the project gateway URL as the Server URL and a Name such as
Speakeasy, then click Next. - Under Authentication settings, choose OAuth 2.0 and fill in the following fields.
| Field | Value |
|---|---|
| Authorization URL | The project gateway URL followed by /authorize. |
| Token URL | The project gateway URL followed by /token. |
| Client ID | The client_id from the command response. |
| Client Secret | The client_secret from the command response. |
| Scopes | Leave empty. The gateway does not advertise or require OAuth scopes. |
| Authorization URL Parameters | Leave empty. |
- Click Verify Auth and sign in to Speakeasy. On the consent page, choose Progressive under Tool discovery, then click Continue.
- Under Configure your data connector, choose a Multi-region location and enter a connector name, then click Add.
- Turn the connection on. Google adds it turned off, and it stays hidden from the team until an administrator turns it on.
Verify
Section titled “Verify”Sign in to business.gemini.google as a team member and ask Gemini to use the connector:
Use the Speakeasy connector to call list_servers and show the servers I can access.Each person signs in to Speakeasy the first time Gemini uses the connector. Upstream services may also ask each person to connect an account.
Gemini Enterprise Standard, Plus, and Frontline
Section titled “Gemini Enterprise Standard, Plus, and Frontline”A Google Cloud administrator adds the connector once to a Gemini Enterprise app, as a custom MCP data store in the Google Cloud console. Everyone with access to that app can then use it. Google calls a custom MCP connector a data store, and calls MCP tools actions.
Before starting
Section titled “Before starting”- A Gemini Enterprise app in Google Cloud. Create the app before configuring its connector.
- The Discovery Engine Editor role (
roles/discoveryengine.editor) to create the data store. - An organization-policy administrator who can allow custom MCP connectors if they are blocked.
Allow custom MCP connectors
Section titled “Allow custom MCP connectors”Have a Google Cloud organization-policy administrator allow custom MCP connectors in the app’s project. Set enforcement Off for constraints/discoveryengine.managed.disableCustomMcpServerConnector with a project-scoped override.
Where data-source or egress policies apply, allow custom_mcp and the gateway, authorization, and token endpoint domains. Google’s organization policy instructions cover the enforcement conditions.
Register Gemini with the gateway
Section titled “Register Gemini with the gateway”Paste the project gateway URL below to generate a curl command that registers Gemini as an OAuth client of the gateway. Run it in a terminal to get the client ID and secret.
Create the data store
Section titled “Create the data store”- In Google Cloud > Gemini Enterprise > Apps, select the app.
- Open Connected Data Stores > New data store.
- Search for Custom MCP Server, then click Add MCP server.
- Select OAuth 2.0 and fill in the following fields.
| Field | Value |
|---|---|
| MCP Server URL | The project gateway URL. |
| Authorization URL | The project gateway URL followed by /authorize. |
| Token URL | The project gateway URL followed by /token. |
| Client ID | The client_id from the command response. |
| Client Secret | The client_secret from the command response. |
| Scopes | Leave empty. The gateway does not advertise or require OAuth scopes. |
| Authorization URL Parameters | Leave empty. |
| Enable PKCE Support | Turn on. Speakeasy requires S256 PKCE. |
| Use HTTP Basic Authentication | Leave on. Registration uses client_secret_basic. |
- Click Verify Auth. Sign in to Speakeasy, choose Progressive under Tool discovery on the consent page, and select the servers Gemini should use.
- Continue through the connector settings, choose its location and name, and click Create.
- Wait for the data store state to become Active.
Enable the gateway actions
Section titled “Enable the gateway actions”- Open the data store and click Actions > Reload custom actions. Complete authentication if prompted.
- Select all five actions:
list_servers,describe_server,describe_tools,execute_tool, andconnection_status. - Click Enable actions.
These actions let Gemini discover servers, read tool schemas, call tools, and check pending account connections. Google recommends enabling no more than 100 actions at a time. Progressive discovery uses five, however many servers the project has.
Verify
Section titled “Verify”Open the user-facing URL of the app that owns the data store, sign in as an intended user, and start a new conversation:
Use the Speakeasy MCP connector to call list_servers and show the servers I can access.Pick a server from the result, ask Gemini to describe its tools, then ask for a harmless read-only operation, such as listing open issues. A tool call that returns recognizable live data verifies the connection.
If a server needs an upstream account, ask Gemini to call connection_status, open the returned link, connect the account, and retry.
Frontline users only get agents that an administrator provisions for them. Check that the agents assigned to Frontline users can use the data store.
Gemini CLI
Section titled “Gemini CLI”Gemini CLI reads MCP servers from each person’s settings.json file, so there is no administrator console. Each person adds the gateway once:
gemini mcp add --transport http --scope user \ speakeasy \ 'https://<organization-host>/mcp/gateway/<organization-slug>/projects/<project-slug>'Then start Gemini CLI and sign in to Speakeasy:
/mcp auth speakeasyRun /mcp to check that the speakeasy server is connected and lists its tools.