Before you begin: To connect an MCP client to TapClicks, you will need an active TapClicks account with the MCP module enabled, a web browser (Chrome or Edge recommended), and an OAuth Client ID and Client Secret from TapClicks, see the section below if you are not sure where to find these. You will also need one of the supported MCP clients: Claude or Gemini CLI. See the Connect via Claude or Connect via Gemini CLI section below for client-specific requirements.
Overview
MCP (Model Context Protocol) is a secure way to connect AI assistants and tools you already use, such as Claude or Gemini CLI, to TapClicks. Once connected, these tools can read and interact with your TapClicks data on your behalf, saving you time and reducing the need to copy-paste information back and forth.
This article walks you through connecting TapClicks via MCP to Claude or Gemini CLI. Choose the section below that matches the client you use. The steps typically take about 10–15 minutes to complete.
Control Data Access With Data Profiles
Before you connect an MCP client to TapClicks, consider what data the connection should be able to access. Data Profiles are a permission layer that group users by data access level, letting you control which data sources, dashboards, and metrics are visible through the connection.
If you want your MCP client to see only specific data sources or dashboards, assign the TapClicks user account associated with your OAuth credentials to a Data Profile with the appropriate permissions before you continue. For more information, see Setting up a Data Profile.
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. |
Connect via Claude
Before you begin: To connect Claude to TapClicks, you will need a Claude account (Pro, Team, or Enterprise) that supports MCP connections, since Claude only supports MCP connections on Desktop clients.
If you are not sure which Claude plan you have, click your profile icon in the top-right corner of Claude. If you see Manage Subscription, you are logged in and can check your plan there. You must at least be on the Pro plan to create MCP connections.
Add the MCP connection in Claude
1] Open Claude and sign in if you have not already.
2] Click your profile icon in the top-left corner of the screen.
3] Select Settings from the dropdown menu.
4] In the Settings menu, click Connectors in the left sidebar.
5] In the top-right corner of the page, click Add.
6] From the dropdown menu, click the Add custom connector button.
7] Name the connector (we recommend calling it "TapClicks").
8] In the Remote MCP server URL field, enter your <TapClicks URL>/server/api/mcp - for instance, https://mytapclicks.tapclicks.com/server/api/mcp. If you have advanced custom branding, use your customized URL.
9] Expand the entry form to add the OAuth credentials. Enter:
- Client ID: Paste the Client ID you copied in the Get Your OAuth Credentials from TapClicks section above
- Client Secret: Paste the Client Secret you copied in the Get Your OAuth Credentials from TapClicks section above
10] Click Add.
Authorize the connection (sign in to TapClicks)
11] Click the Connect button for the connection you just created.
12] A pop-up window (or new browser tab) will appear, taking you to a TapClicks login or authorization page.
13] Log in to TapClicks using your username and password.
14] You will be shown a screen asking you to approve the connection. Click Accept.
15] You will be returned to Claude automatically. You should see a confirmation message that the connection was successful.
16] You can now click Configure to see the list of available tools.
| Note: All the tools are set to Needs Approval by default. Once you are familiar with the tools, you may set these to Always Approved as needed. |
Test the connection
17] Start a new conversation in Claude.
18] Try a simple request related to TapClicks, such as:
- "Show me data sources from TapClicks."
- "What is in my TapClicks dashboard today?"
19] Claude should respond by requesting access to the tools to pull real information from your TapClicks account.
If it works, you are all set. If not, refer to FAQs - Model Context Protocol (MCP).
How to disconnect TapClicks
1] In Claude, go to Settings, then Connectors.
2] Find TapClicks in your connected integrations (or the name of your custom connector).
3] Click Disconnect or Remove.
| Note: If you want to disconnect the MCP for all users, you can also go to TapClicks's Platform Settings > MCP Access and revoke the Claude app there to fully remove access from both sides if you do not plan to use the MCP again. This removes access for all users, so be careful about revoking key access. |
Connect via Gemini CLI
Before you begin: To connect Gemini CLI to TapClicks, you will need Gemini CLI installed and the MCP module enabled on your TapClicks instance. If you are not sure whether the MCP module is enabled, contact TapClicks Support; otherwise, you may see a "You do not have permission to access MCP resources" error. Gemini CLI's MCP support is available on business or paid-tier licenses; check with Google to confirm which Gemini CLI options are available for your account type.
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.
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 the Known issues section below, or contact TapClicks Support 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 TapClicks Support 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 TapClicks Support 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 the third-party AI client you are using.
This article applies to Claude.ai (Pro, Team, and Enterprise plans) and Gemini CLI on supported licenses.