How to Connect to Gemini CLI via Model Context Protocol (MCP) – TapClicks

Before you begin: To connect Gemini CLI to TapClicks, you will need Gemini CLI installed, with MCP support available on business or paid-tier licenses. You will also need an active TapClicks account with the MCP module enabled, and an OAuth Client ID and Client Secret from TapClicks.

If you are not sure which Gemini CLI license you have, check with Google to confirm which options are available for your account type. You must be on a business or paid-tier license to use MCP with Gemini CLI.

For an overview of MCP and how Data Profiles control what data Gemini CLI can access through this connection, see Model Context Protocol (MCP) Overview.

Get Your OAuth Credentials from TapClicks

1] Log in to TapClicks and, on the Admin menu, click Platform Settings.

2] From the available tabs, select the Application tab.

3] Scroll down to the MCP Keys/Credentials section.

4] Click Show to see the Client ID and Client Secret.

5] Copy your Client ID and Client Secret and save them somewhere safe (like a notes app). You will need them in the next section.

Note: Your Client Secret is like a password, so treat it carefully. Do not share it in email or chat. TapClicks will typically only show it to you once, so copy it before closing the page.

Add the MCP Connection in Gemini CLI

1] Install Gemini CLI by following the official installation instructions for your platform, then confirm it is working by running the following command in a terminal:

gemini --version

2] Open (or create) your Gemini CLI settings file at ~/.gemini/settings.json. If the file already exists, edit it rather than replacing it, so you do not lose any other settings already in there.

3] Add an entry for TapClicks under mcpServers, replacing the placeholders with your own values:

{
  "mcpServers": {
    "tapclicks": {
      "httpUrl": "https://YOUR-INSTANCE-DOMAIN/server/api/mcp",
      "oauth": {
        "enabled": true,
        "clientId": "YOUR_CLIENT_ID",
        "clientSecret": "YOUR_CLIENT_SECRET",
        "authorizationUrl": "https://YOUR-INSTANCE-DOMAIN/server/api/mcp/authorize",
        "tokenUrl": "https://YOUR-INSTANCE-DOMAIN/server/api/mcp/token"
      }
    }
  }
}

Note: Gemini CLI can normally auto-discover the authorizationUrl and tokenUrl values, but including them directly avoids a known auto-discovery issue in Gemini CLI, so we recommend always adding them.

4] If you already have other MCP servers configured, add "tapclicks" as another entry inside the existing mcpServers object rather than overwriting the whole file. You can rename "tapclicks" to whatever label you prefer.

Authorize the Connection (Sign In to TapClicks)

5] Start Gemini CLI, then run:

/mcp auth tapclicks

Note: You may see an error such as "Failed to handle automatic OAuth for server 'tapclicks': No client ID provided and dynamic registration not supported." This is expected and can be ignored; the connection still completes successfully.

6] This opens your browser to your TapClicks login page. Log in using your username and password.

7] Approve access when prompted. You will be redirected back to Gemini CLI, which will confirm authentication.

Note: If the MCP module is not enabled on your TapClicks instance, you may see a "You do not have permission to access MCP resources" error. If this happens, contact your Customer Success Manager or customercare@tapclicks.com to confirm the module is enabled.

Test the Connection

8] Run:

/mcp

You should see a status indicating that the tapclicks connection is ready, along with the number of available tools.

9] If the connection shows as disconnected instead, see FAQs - Model Context Protocol (MCP), or contact your Customer Success Manager or customercare@tapclicks.com with the exact error shown.

10] Try a request such as:

"List my TapClicks clients."
"Show me available data sources."

How to Disconnect Gemini CLI

1] Contact your Customer Success Manager or customercare@tapclicks.com to revoke the OAuth credentials issued for your Gemini CLI connection. This immediately cuts off that integration's access without affecting your normal TapClicks login.

2] Remove the tapclicks entry from your ~/.gemini/settings.json file to stop Gemini CLI from attempting to connect locally.

Need More Help?

If you run into issues, contact your Customer Success Manager or customercare@tapclicks.com with the exact error message, your instance domain, and the step in this guide you were on. This helps us determine quickly whether it is a TapClicks configuration issue or an issue with Gemini CLI.

Gemini CLI Documentation

This article applies to Gemini CLI on supported licenses.