Connect Dapper to Gemini Enterprise

For teams using Gemini with Google Workspace accounts. Your admin connects Dapper once; then each team member authorizes their own Dapper account.

MCP endpoint

https://api.dapperglobal.com/mcp

Before you start

Account: A Workspace account with team admin rights in Gemini Enterprise. Each team member also needs their own active Dapper account.
Plan: Gemini Enterprise. On Business you configure it at business.gemini.google; on Standard and Plus, in the Google Cloud console. Custom MCP connections are in Preview (Pre-GA) on both.
Where it works: In the Gemini Enterprise web app and in your team's agents, wherever your organization has Gemini Enterprise.
Permissions: On Business, team admin. On Standard and Plus, the Discovery Engine Editor role to create the data store and Organization Policy Administrator for the policy in the first step.

Step by step

Register Gemini Enterprise with Dapper

Gemini Enterprise doesn't register OAuth clients on its own: it asks for a client ID and client secret. You get them with a single call to Dapper's client registration — no support ticket needed. Run this once and keep client_id and client_secret from the response; the secret is not shown again.

curl -s https://api.dapperglobal.com/mcp/register \
  -H 'Content-Type: application/json' \
  -d '{
    "client_name": "Gemini Enterprise",
    "redirect_uris": ["https://vertexaisearch.cloud.google.com/oauth-redirect"],
    "grant_types": ["authorization_code", "refresh_token"],
    "token_endpoint_auth_method": "client_secret_post",
    "scope": "mcp:read offline_access"
  }'

# -> {"client_id": "...", "client_secret": "...", ...}

2
Open Connected apps
Go to business.gemini.google, click Settings & help, choose your team, and go to Manage team → Connected apps.
3
Add the server
Click Add MCP Server. Under MCP info, set Server URL to the Dapper endpoint and Name to Dapper. Click Next.
```
https://api.dapperglobal.com/mcp
```
4
Set up OAuth
Under Authentication settings, choose OAuth 2.0 and fill in the fields. The scopes have to be exactly the ones registered in step 1: Dapper rejects a scope the client wasn't registered with. If the form offers Enable PKCE Support, turn it on — Dapper requires PKCE.
Authorization URL
https://api.dapperglobal.com/mcp/authorize
Token URL
https://api.dapperglobal.com/mcp/token
Authorization URL Parameters
Empty
Client ID
The client_id from step 1
Client Secret
The client_secret from step 1
Scopes
mcp:read offline_access
5
Verify
Click Verify Auth: Dapper's sign-in opens. Log in and approve. Then click Continue.
6
Create the connector
Under Configure your data connector, pick a location in the Multi-region field, name the connector, and click Add.
7
Turn it on for the team
The connector is created switched off. Enable it in the connectors list so your team can see it.
8
Ask something
Each person authorizes their Dapper account the first time they use it. Try: “Find open public consultations from ANEEL about electricity distribution.”

Troubleshooting

The server won't connect: Gemini Enterprise only accepts Streamable HTTP transport. Dapper's endpoint already uses it, so check that the URL ends in /mcp.
Verify Auth fails: it's almost always the scopes (they must match the step 1 registration), the redirect URL (the registration must include https://vertexaisearch.cloud.google.com/oauth-redirect) or PKCE left off.
“Client ID not found”: the step 1 registration is deleted after a year without use. Repeat step 1 and update Client ID and Client Secret on the connector.
The team can't see Dapper: the connector is created switched off; enable it in the connectors list.

Another way in

Standard and Plus (Google Cloud console)

Same values as the table in step 4 (and you still need the step 1 registration); only where you enter them changes:

Check the organization policy. Gemini Enterprise blocks custom MCP connectors by default. In IAM & Admin → Organization Policies, select your project (not the organization), find “Disable custom MCP server connector for Gemini Enterprise”, override the parent's policy with a rule set to Off, and save.
If your organization restricts outbound traffic, add api.dapperglobal.com to the allowed egress FQDNs.
Create the data store. In the console, open Gemini Enterprise → Data stores → Create data store, search for Custom MCP Server (Preview), and enter the URL, OAuth credentials and location with the same values. Turn on Enable PKCE Support.
Connect it to your app. Attach the data store to your Gemini Enterprise app and authorize the connection.

Google's documentation

Steps taken from Google's documentation (linked above) in October 2026, not yet with our own screenshots. If a menu moved, the endpoint at the top of this page stays the same.