Gemini Enterprise MCP Setup
Connect TollBit to Gemini Enterprise as a custom MCP server
TollBit connects to Gemini Enterprise as a custom MCP server. Once it's set up, your users can ask Gemini to search publisher content, check prices, buy articles and query TollBit analytics, signed in with their own TollBit account. This guide follows Google's Set up your custom MCP server connection, with the values TollBit needs.
Setup takes about ten minutes, in three steps:
- Register Gemini Enterprise with TollBit, with one command.
- Add TollBit as a custom MCP server in Gemini Enterprise.
- Tell TollBit your client ID, and let your users know it's available.
Before You Start
- Team administrator access to Gemini Enterprise at business.gemini.google.
- A terminal with
curl(macOS, Linux, or Windows 10 and later), or Windows PowerShell. - Your users don't need a TollBit account to start: they can connect as a guest and sign in later.
Step 1: Register Gemini Enterprise With TollBit
Run this command once. Replace <Your company> with your company's name, so you and TollBit can recognize the registration. It creates an OAuth client for your Gemini Enterprise and returns its credentials.
curl -s https://oauth.tollbit.com/oauth2/register \
-H 'Content-Type: application/json' \
-d '{
"client_name": "Gemini Enterprise - <Your company>",
"redirect_uris": ["https://vertexaisearch.cloud.google.com/oauth-redirect"],
"token_endpoint_auth_method": "client_secret_basic"
}'$body = @{
client_name = "Gemini Enterprise - <Your company>"
redirect_uris = @("https://vertexaisearch.cloud.google.com/oauth-redirect")
token_endpoint_auth_method = "client_secret_basic"
} | ConvertTo-Json
Invoke-RestMethod -Method Post -Uri "https://oauth.tollbit.com/oauth2/register" `
-ContentType "application/json" -Body $bodyThe response contains these values:
| Value | What to Do With It |
|---|---|
client_id | Enter it in Gemini Enterprise in step 2, and send it to TollBit in step 3. |
client_secret | Enter it in Gemini Enterprise in step 2. Treat it like a password: don't email it or share it. |
registration_access_token | Not needed. Don't share it; you can discard it. |
Step 2: Add TollBit to Gemini Enterprise
- Sign in to Gemini Enterprise at business.gemini.google and click Settings & help.
- Select your team, then go to Manage team → Connected apps, and click Add MCP Server.
- Under MCP info, enter the server URL and name below, and click Next.
- Under Authentication settings, choose OAuth 2.0 and enter the values below. Click Verify Auth: it opens TollBit's sign-in page, where you can sign in or continue as a guest. Then click Continue.
- Under Configure your data connector, choose a Multi-region location and a data connector name, and click Add.
- Enable the connection. It's off by default, and your team can't see TollBit until you turn it on.
| Field | Value |
|---|---|
| Server URL | https://mcp.tollbit.com/mcp |
| Name | TollBit |
| Authorization URL | https://oauth.tollbit.com/oauth2/auth |
| Token URL | https://oauth.tollbit.com/oauth2/token |
| Authorization URL Parameters | Leave empty. |
| Client ID | client_id from step 1. |
| Client Secret | client_secret from step 1. |
| Scopes | openid offline_access tollbit:discover tollbit:analytics tollbit:spend |
Step 3: Finish Up
- Send TollBit your client ID, not the secret, to [email protected] or your TollBit contact. It lets TollBit match the registration to your company if you need help or want access removed.
- Tell your users TollBit is available in Gemini, and what they'll see the first time they use it (below).
What Your Users Will See
The first time a user uses TollBit, Gemini asks them to connect. TollBit's sign-in page offers two choices:
- Sign in with their TollBit account. They can search, check prices, buy content and use analytics, and they approve TollBit's access on a consent screen.
- Continue as guest. They can search and check prices. Buying content and analytics need an account: when a tool needs one, the user reconnects TollBit in Gemini and chooses Sign in.
Each user signs in separately, so a user's TollBit access is limited to their own account.
Rotating or Removing Access
To rotate the client secret or remove TollBit's access, email [email protected] with your client ID.
Troubleshooting
| Problem | What to Do |
|---|---|
| Users connect, but TollBit's tools fail | Have the user disconnect and reconnect TollBit. If it still fails, email [email protected]. |
invalid_client on Verify Auth | Check the client ID and secret were copied in full. If they were, run the step 1 command again with client_secret_post in place of client_secret_basic, and use the new values. |
| Redirect URL error | The registration must use https://vertexaisearch.cloud.google.com/oauth-redirect exactly. Register again with the command in step 1. |
| Registration command returns an error | Check the command was copied in full, including the quotes. If it still fails, send the error text to [email protected]. |
Updated about 18 hours ago