> ## Documentation Index
> Fetch the complete documentation index at: https://docs.interchange.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Interchange to Gemini Enterprise

> Add the Interchange MCP server as a Connected App in Gemini Enterprise — a per-tenant admin action with no review from Google.

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.

<Info>
  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.
</Info>

## 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

1. In the Gemini Enterprise admin console, open **Connected Apps** (or
   **Apps and integrations**, depending on your console version).
2. Select **Add app** → **Custom MCP server**.
3. 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](#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](#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`                                                                                                                                                                                                                                                                                                                                                                                  |

<Warning>
  Gemini Enterprise's custom MCP connector requires **Streamable HTTP**.
  Interchange's remote MCP endpoint is Streamable HTTP, so no adapter is
  needed.
</Warning>

## 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](/v2/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:

```bash theme={null}
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.

<Note>
  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.
</Note>

## 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](/v2/setup/built-for-agents#available-mcp-tools).