Connect Interchange to Gemini Enterprise

Gemini Enterprise lets a workspace admin add a remote MCP server as a Connected App, making its tools available to that tenant’s Gemini Enterprise users. This is a tenant-admin action inside Google’s console — Google does not review or approve the connection, so there is no submission process to wait on. This guide covers the admin-side setup only.

Only a Gemini Enterprise admin for your workspace can add a Connected App. If you don’t have admin access, send this page to whoever administers Gemini Enterprise for your organization.

Before you start

You need:

Gemini Enterprise admin access for your Google Workspace or Google Cloud organization; and
an Interchange buyer or seller account.

1. Add Interchange as a Connected App

In the Gemini Enterprise admin console, open Connected Apps (or Apps and integrations, depending on your console version).
Select Add app → Custom MCP server.
Complete the form:

Field	What to enter
MCP server URL	`https://api.interchange.io/mcp/buyer` for a buying tenant, `https://api.interchange.io/mcp/storefront` for a storefront-operator tenant.
Name	A name your users will recognize, for example `Interchange`.
Description	A short, accurate description of the tool. Gemini Enterprise uses this text — along with each discovered tool’s own description — for AI routing, i.e. deciding when to call Interchange versus another connected app. A vague or promotional description makes routing worse, not better.
Authorization URL	`https://api.interchange.io/authorize`
Token URL	`https://api.interchange.io/auth/token`
Client ID	See Authenticate below.
Client secret	Leave blank. Interchange issues only public OAuth clients (`token_endpoint_auth_method: none`) — there is no secret to enter, including through the manual fallback in Authenticate. If your console’s form requires a non-empty value here, that specific console build cannot be configured against Interchange yet; contact Interchange support rather than entering a placeholder.
Scopes	`openid profile email`

Gemini Enterprise’s custom MCP connector requires Streamable HTTP. Interchange’s remote MCP endpoint is Streamable HTTP, so no adapter is needed.

Authenticate

Interchange supports OAuth 2.0 authorization-code sign-in with PKCE, including dynamic client registration (DCR) so a compliant host can register itself rather than needing a pre-issued client ID (see Authentication → MCP OAuth resource binding). If Gemini Enterprise’s form requires a Client ID up front rather than discovering one automatically, register a static client first:

curl -X POST https://api.interchange.io/auth/register \
  -H "Content-Type: application/json" \
  -d '{
    "client_name": "Gemini Enterprise - <your workspace name>",
    "redirect_uris": ["<the redirect URI Gemini Enterprise displays in its Connected App form>"]
  }'

Copy the returned client_id into the console’s Client ID field, leave Client secret blank (the registered client is public, not confidential — this manual path issues the same kind of secret-less client DCR would have), and complete sign-in with the Interchange account the app should act as.

2. Enable tools

Gemini Enterprise discovers Interchange’s tool catalog after the Connected App is authorized, then lists them for the admin to enable individually. Every discovered tool starts off — a tool is not usable by Gemini Enterprise users until an admin explicitly turns it on, even though the server advertised it.

Gemini Enterprise currently caps a single tenant at 100 enabled actions across all of its Connected Apps combined, not per app. Interchange’s tool catalog can approach or exceed that budget once you account for every other connected app in your tenant. Enable the tools your users actually need — the discovery, campaign-setup, and campaign-management workflows are the common starting set — rather than enabling everything by default, so there’s headroom left for your other connected apps.

Next steps

Ask a Gemini Enterprise user to try a read, for example “list my advertisers” or “show my storefront’s current inventory,” and confirm the result before enabling additional tools. For the full tool catalog available over these endpoints, see Available MCP Tools.

Start building

Core Concepts

Buyer operations

Seller operations

Cross-Cutting Reference

Buyer API reference

Seller API reference

Release Notes

Connect Interchange to Gemini Enterprise

Before you start

1. Add Interchange as a Connected App

Authenticate

2. Enable tools

Next steps

​Before you start

​1. Add Interchange as a Connected App

​Authenticate

​2. Enable tools

​Next steps

Before you start

1. Add Interchange as a Connected App

Authenticate

2. Enable tools

Next steps