# Google Google Clients

Source: https://userguide.qualytics.io/using-the-platform/mcp/connecting-external-ai-clients/google/

Connect Gemini and Gemini CLI to the Qualytics MCP server. Before you start, have a Personal API Token and your Qualytics MCP server URL ready. See [External AI Client Requirements](https://userguide.qualytics.io/using-the-platform/mcp/connecting-external-ai-clients/requirements/).

**Tab: Gemini**

Gemini adds the Qualytics MCP server as a **custom app**. Custom apps can only be added in the Gemini web app, and once added they also appear in the Gemini mobile app.

> **Info: Who can add a custom app**
>
> Custom apps are available on personal Google Accounts with an eligible Google AI subscription. They are not available on work or school accounts. If you do not see the option, check the eligibility rules in Google's Gemini Apps Help.

> **Info: Your Qualytics instance must be reachable from the internet**
>
> Gemini connects to custom apps from Google's cloud, not from your computer, so your Qualytics instance must be reachable over the internet through HTTPS.

1. Open Gemini in your browser at `gemini.google.com`.
2. Go to **Settings** > **Connected Apps**.
3. At the bottom of the list, select **Add a custom app**.
4. Paste your Qualytics MCP URL: `https://your-qualytics-instance.qualytics.io/api/mcp/`, then select **Next**. Leave any client ID and client secret empty, so Gemini registers its own client with Qualytics.
5. Review the security and privacy warning and accept it.
6. When Gemini opens the Qualytics authorization page, paste your Qualytics API token and approve the access.
7. Confirm that the Qualytics tools are listed, then save the app.

You can disconnect Qualytics at any time from **Settings** > **Connected Apps**.

**Tab: Gemini CLI**

1. Register the server for all your projects:

   ```bash
   gemini mcp add --transport http --scope user qualytics https://your-qualytics-instance.qualytics.io/api/mcp/
   ```

   Without `--scope user`, the server is saved only for the current project. You can also add it by hand to `~/.gemini/settings.json`, using the `httpUrl` key:

   ```json
   {
     "mcpServers": {
       "qualytics": {
         "httpUrl": "https://your-qualytics-instance.qualytics.io/api/mcp/"
       }
     }
   }
   ```
2. Start Gemini CLI. When it connects to Qualytics for the first time, it finds the authorization details, registers itself, and opens your browser. You can also start the sign-in with `/mcp auth qualytics`.
3. On the Qualytics authorization page, paste your Qualytics API token and approve the access.
4. Run `/mcp list` to confirm the server shows as `CONNECTED` with its tools.

Leave out the `oauth` and `headers` properties. Gemini CLI registers its own client with Qualytics, and Qualytics does not accept an API token in a header.

The browser sign-in does not work in a session without a browser, such as a remote SSH session or a container. Sign in from a machine that can open one.

> **Note: Antigravity CLI**
>
> For personal Google Accounts, Google replaced Gemini CLI with Antigravity CLI on June 18, 2026. This page covers Gemini CLI only.

> **Info: Official Documentation**
>
> These steps follow Google's guides for [Gemini custom apps](https://developers.google.com/connected-apps/mcp/dev-mode/usage) and [MCP servers in Gemini CLI](https://www.geminicli.com/docs/tools/mcp-server). If a menu or command in your version differs, check those pages.

If the connection fails, see [MCP Troubleshooting](https://userguide.qualytics.io/using-the-platform/mcp/troubleshooting/).

*Last updated: November 7, 2026.*