This document contains frequently asked questions about connecting to TapClicks using MCP (Model Context Protocol), including Claude and Gemini CLI. For step-by-step setup instructions, see How to Connect to TapClicks via Model Context Protocol (MCP).
What should I do if the authorization pop-up does not appear?
What should I do if I get an error saying "Invalid Client ID or Secret"?
What should I do if I get an error saying "MCP Access is not available for your instance"?
What should I do if I get an error saying "MCP Access is not available for your user"?
Why did Claude connect successfully but does not seem to have my data?
What should I do if the pop-up appears but closes without completing?
Why do I not see TapClicks in the list of integrations?
Why do some Gemini CLI list results fail with a JSON validation error?
What should I do if my Gemini CLI connection breaks after my login expires?
Why are some Gemini CLI issues not TapClicks' to fix?
What should I do if the authorization pop-up does not appear?
Try disabling your pop-up blocker for claude.ai, then repeat the steps in the "Add the MCP Connection in Claude" section of How to Connect to TapClicks via Model Context Protocol (MCP).
What should I do if I get an error saying "Invalid Client ID or Secret"?
Go back to TapClicks and double-check that you copied the credentials correctly, with no extra spaces at the beginning or end.
What should I do if I get an error saying "MCP Access is not available for your instance"?
Check with TapClicks support or your TapClicks contact to verify that your instance has had the feature enabled. This feature may only be available on particular platform packages.
What should I do if I get an error saying "MCP Access is not available for your user"?
Roles determine who can access the MCP server. Check with your TapClicks administrator to confirm your role includes access to the MCP.
Why did Claude connect successfully but does not seem to have my data?
Make sure you approved all the requested permissions during the authorization step. Also remember that the data available in the MCP is secured by your Data Profile. You may need your administrator to grant access to additional data sources, metrics, and attributes.
What should I do if the pop-up appears but closes without completing?
This can happen if the authorization timed out. Start again from step 6 in the "Add the MCP Connection in Claude" section of How to Connect to TapClicks via Model Context Protocol (MCP). Make sure you are signed in to TapClicks in the same browser before beginning.
Why do I not see TapClicks in the list of integrations?
This integration may not yet be available on your current Claude plan, or your organization's administrator may have restricted it. Contact your administrator, reach out to Anthropic support, or try connecting using the instructions for custom connectors.
Why do some Gemini CLI list results fail with a JSON validation error?
This is a limitation in Gemini CLI itself, not a defect in TapClicks' MCP server. TapClicks' server is tested against the official MCP specification and responds correctly and consistently; this issue occurs within Gemini CLI and is outside TapClicks' ability to fix directly.
You may see an error mentioning structuredContent or "expected record, received array." This is a known limitation in how Gemini CLI parses certain tool responses that come back as a list rather than a single object, and it affects other, unrelated MCP servers in the same way, not just TapClicks.
TapClicks' MCP server returns data in the standard format defined by the MCP specification. The failure happens entirely inside Gemini CLI's own response parsing, before your query result would reach you. There is no fix available on TapClicks' end; try upgrading to the latest version of Gemini CLI, since this may already be resolved in a newer release.
What should I do if my Gemini CLI connection breaks after my login expires?
If Gemini CLI is left running for a while, you may find that /mcp still lists your TapClicks connection as available, but queries start failing. Gemini CLI may also try to reconnect on its own and immediately fail with an error such as "No client ID provided and dynamic registration not supported," sometimes followed by a crash.
This happens because Gemini CLI has two different ways of authenticating: one where you run /mcp auth tapclicks yourself, and a separate, automatic one it tries to use silently in the background when it notices your login has expired. The automatic method does not use the Client ID and Client Secret you configured; it only works with services that support self-registering new applications on the fly, which TapClicks intentionally does not support (see "Add the MCP Connection in Gemini CLI" in How to Connect to TapClicks via Model Context Protocol (MCP)).
Workaround: do not wait for Gemini CLI to reconnect on its own.
- Check /mcp periodically before trusting an important answer. If it does not show a clean ready status, the session has gone stale.
- Run /mcp auth tapclicks manually as soon as this is noticed, rather than letting Gemini CLI try to recover silently.
- If Gemini CLI crashes, restart it and run /mcp auth tapclicks again.
To use a different AI assistant integration with TapClicks in the meantime, see the "Connect via Claude" section of How to Connect to TapClicks via Model Context Protocol (MCP).
Why are some Gemini CLI issues not TapClicks' to fix?
MCP is an open, client-agnostic protocol. TapClicks' server does not know or care whether it is talking to Claude, Gemini CLI, or any other compliant client, and it responds identically to all of them, following the published specification. When something breaks only for one specific client and works fine for others, that is a strong signal the issue lives in that client's own code, not in TapClicks' server.
TapClicks Support can help with TapClicks login and permission issues, getting OAuth credentials set up, confirming the MCP module is enabled on an instance, and anything where TapClicks' response looks genuinely wrong or inconsistent. Issues inside Gemini CLI or any other third-party AI tool need to be reported to that tool's vendor.