Connect Gemini

Which Gemini product?

MCP server URL

https://mcp.syncrange.com/mcp

Gemini Enterprise requires Streamable HTTP (this URL). Do not use an SSE-only endpoint.

Gemini Enterprise (chat UI)

This is the path for chatting with SyncRange tools inside a Gemini Enterprise app. An admin with permission to create data stores (e.g. Discovery Engine Editor) configures the connector once; each user then authorizes in the chat UI.

1. Create a Custom MCP Server data store

1. In Gemini Enterprise / Google Cloud console, create a data store and choose Custom MCP Server (preview feature — exact navigation may say “Data stores” → “Create”).
2. Set MCP Server URL to https://mcp.syncrange.com/mcp.
3. Choose OAuth authentication and fill in SyncRange’s authorization server:

2. Attach the data store to your Gemini Enterprise app

1. Open your Gemini Enterprise App.
2. Go to Connected data sources (or equivalent).
3. Add the SyncRange custom MCP data store you just created.

3. Authorize in the Gemini Enterprise chat UI

1. Open the Gemini Enterprise web app for that project.
2. In the chat input area, open the connectors / tools control (often a stacked-layers or similar icon next to the composer).
3. Find the SyncRange connector. If it shows Authorize, click it and complete SyncRange sign-in: pick your team, review scopes, and approve.
4. Ensure the connector toggle is on for the conversation.
5. Ask a question such as: "What were my Shopify sales last month?"

Gemini CLI (personal / developer)

If you use Gemini from the terminal, connect SyncRange with a manual bearer token (same pattern as Cursor).

1. Create a SyncRange token

   Follow Create a manual token and choose Gemini as the client label. Copy the <prefix>.<secret> value once.

2. Add the server with the Gemini CLI

   gemini mcp add --transport http \
     --header "Authorization: Bearer <prefix>.<secret>" \
     syncrange https://mcp.syncrange.com/mcp

3. Or edit settings.json

   Add (or merge) this under mcpServers in your user or project Gemini settings:

   {
     "mcpServers": {
       "syncrange": {
         "httpUrl": "https://mcp.syncrange.com/mcp",
         "headers": {
           "Authorization": "Bearer <prefix>.<secret>"
         }
       }
     }
   }

   Use httpUrl for SyncRange’s Streamable HTTP endpoint (not the SSE-style url field).

4. Chat in the CLI

   Start Gemini CLI and ask about your connected sources. Confirm SyncRange tools are listed/available in the session if your CLI version shows MCP status.

Full token safety notes and generic JSON examples: CLI & local clients.

After you connect

• OAuth (Enterprise) and manual tokens both appear under SyncRange Connections → AI Assistants.
• Revoke there to disable access immediately.
• Treat bearer tokens like passwords — never commit them to git.

Troubleshooting