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

# Gemini Enterprise

> Connect Rippit to Gemini Enterprise as a custom MCP server.

## What to configure

Add Rippit in Gemini Enterprise as a **custom MCP server** with these settings:

| Setting             | Value                                    |
| ------------------- | ---------------------------------------- |
| MCP server URL      | `https://mcp.rippit.com/mcp`             |
| Transport           | Streamable HTTP                          |
| Authentication      | OAuth 2.0                                |
| Client ID           | `gemini-enterprise-mcp`                  |
| Client secret       | Leave blank                              |
| Authorization URL   | `https://app.rippit.com/oauth/authorize` |
| Token URL           | `https://app.rippit.com/oauth/token`     |
| Scopes              | `mcp offline_access`                     |
| Enable PKCE support | Enabled                                  |

Each user then signs in with their own Rippit account the first time they use it, and access is scoped to that user's Rippit permissions.

## Things to know

**Use the client ID above exactly as written.** Gemini Enterprise requires a client ID, and `gemini-enterprise-mcp` is a public client Rippit has already registered for it, including Gemini's callback URL. Generating your own client ID somewhere else, such as in Postman or an API testing tool, produces an `invalid_redirect_uri` error at sign-in, because that client is registered against a different callback URL than the one Gemini sends.

**No client secret is needed.** Rippit requires PKCE, and Gemini Enterprise does not send a client secret once PKCE is enabled. Leave the field blank.

**Allow Rippit's hostnames through egress controls.** Before you create the custom MCP server, your Google Cloud administrator needs to allow the `mcp.rippit.com` and `app.rippit.com` egress FQDNs, along with the other organization policy prerequisites in Google's [custom MCP server setup guide](https://docs.cloud.google.com/gemini/enterprise/docs/connectors/custom-mcp-server/set-up-custom-mcp-server).

**Enable the tools you want after setup.** Once the server is connected, reload the custom actions and enable the intended tool set. Gemini Enterprise allows at most 100 tools per agent.

For click-by-click steps in the Gemini Enterprise admin console, contact your Rippit point of contact.

## Next steps

* [What Rippit can do for AI assistants](/mcp-server/overview#what-rippit-can-do-for-ai-assistants)
* [Troubleshooting](/troubleshooting)