# Anthropic Anthropic Clients

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

Connect Claude Desktop and Claude Code 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: Claude Desktop**

Claude adds the Qualytics MCP server as a **custom connector**. The steps are the same in Claude Desktop and in Claude on the web, and the connector is available in both once it is added.

> **Info: Your Qualytics instance must be reachable from the internet**
>
> Claude connects to custom connectors from Anthropic's cloud, not from your computer. If your Qualytics instance is only reachable inside a private network, see Anthropic's guidance on MCP tunnels in the [official documentation](https://claude.com/docs/connectors/custom).

**On a Free, Pro, Max, or Ultra plan**

You add the connector to your own account. The Free plan allows one custom connector.

1. Go to **Customize** > **Connectors**.
2. Click **Add custom connector**.
3. Enter a name, such as `Qualytics`, and the **MCP server URL**: `https://your-qualytics-instance.qualytics.io/api/mcp/`.
4. Leave the OAuth client ID and secret empty. If the dialog asks how people sign in, choose **Sign in now**, and for **OAuth client**, choose **Register automatically**.
5. Click **Add**.
6. When Claude opens the Qualytics authorization page in your browser, paste your Qualytics API token and approve the access.

**On a Team or Enterprise plan**

An Owner adds the connector once for the organization, and each member then connects with their own Qualytics API token. On Enterprise plans, a member whose custom role can manage the organization's libraries can also add it.

1. As an Owner, go to **Organization settings** > **Connectors**.
2. Select **Add**, then **Custom**. If Claude asks for the connector type, choose **Web**.
3. Enter the **MCP server URL**: `https://your-qualytics-instance.qualytics.io/api/mcp/`. Leave the OAuth client ID and secret empty.
4. Click **Add**.
5. Each member goes to **Customize** > **Connectors**, finds the Qualytics connector with the **Custom** label, and clicks **Connect**.
6. On the Qualytics authorization page, the member pastes their own Qualytics API token and approves the access.

**Use Qualytics in a chat**

Click **+** in the chat input, select **Connectors**, and turn the Qualytics connector on for that conversation. Review each tool approval request before you allow it, and use **Always allow** only for tools you trust.

Authentication settings cannot be changed after the connector is added. To change them, remove the connector and add it again.

**Tab: Claude Code**

Claude Code adds the Qualytics MCP server from the command line.

1. Register the server with the HTTP transport:

   ```bash
   claude mcp add --transport http qualytics https://your-qualytics-instance.qualytics.io/api/mcp/
   ```
2. Start Claude Code and run `/mcp`. Select the Qualytics server and follow the browser sign-in. You can also run `claude mcp login qualytics` from your shell.
3. On the Qualytics authorization page, paste your Qualytics API token and approve the access. Claude Code stores and refreshes the MCP tokens on its own.
4. Run `claude mcp list` to confirm the server shows as connected.

Do not add an `Authorization` header with your API token. Qualytics only accepts the browser authorization.

**Choose where the server is saved**

Add `--scope` to the `claude mcp add` command to choose where the configuration lives.

| Scope | Available in | Saved in |
| --- | --- | --- |
| `local` (default) | The current project, for you only | Your user configuration, under that project |
| `project` | The current project, for everyone who clones it | A `.mcp.json` file in the project root |
| `user` | All your projects | Your user configuration |

A project-scoped server holds only the URL, never a token, so each person authorizes with their own API token. Claude Code asks each person to approve a project-scoped server before it uses it.

> **Info: Official Documentation**
>
> These steps follow Anthropic's guides for [custom connectors](https://claude.com/docs/connectors/custom) and [MCP in Claude Code](https://code.claude.com/docs/en/mcp). 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.*