> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qwairy.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Qwairy to Claude Code

> Yes. Add Qwairy to Claude Code as a remote HTTP server with one command, then sign in with OAuth. Use https://mcp.qwairy.co as the server URL.

Qwairy works with Claude Code as a remote HTTP MCP server. You add the server from a terminal, sign in with OAuth, and ask Claude Code questions about your brands. The connection is read-only.

## Before you start

* Access to a Qwairy team on a **Starter plan or higher**. You can connect before monitoring has run. Queries return data once a live brand has generated responses.
* Claude Code installed and signed in
* A browser for the OAuth sign-in, on the same machine or on another one (see Troubleshooting for remote machines).

## Connect Qwairy to Claude Code

**1. Add the server**

Run this command in a terminal. `--scope user` makes Qwairy available in all your projects.

```bash theme={null}
claude mcp add --transport http qwairy --scope user https://mcp.qwairy.co
```

Use the root URL, without appending `/mcp`. Without `--scope user`, Claude Code stores the server for the current project only.

**2. Sign in with OAuth**

Open Claude Code and run `/mcp`, select **qwairy**, and choose **Authenticate**. Claude Code opens your browser. Sign in with the Qwairy account that has access to your brands and approve the access.

From the terminal, you can also run:

```bash theme={null}
claude mcp login qwairy
```

**3. Confirm the server status**

```bash theme={null}
claude mcp get qwairy
```

The output shows the server URL, the HTTP transport, and its status.

## Check that the connection works

In Claude Code, send:

```text theme={null}
Use Qwairy to list the brands I can access.
```

Claude Code should call Qwairy's `list_brands` tool and display the accessible brands. Approve the tool call if it asks. A general answer without a tool call does not confirm the connection.

## Troubleshooting

### The server needs authentication

Run `/mcp` in Claude Code, select **qwairy**, and choose **Authenticate**. Complete the sign-in in the browser, then run `claude mcp get qwairy` again.

### The server is not found or fails to connect

Check that the URL is `https://mcp.qwairy.co` without `/mcp`. To start over, remove the server and add it again:

```bash theme={null}
claude mcp remove qwairy
```

### You work on a machine without a browser

Run `claude mcp login qwairy --no-browser`, open the printed URL in a browser on any machine, sign in and approve the access, then paste the full callback URL back into the terminal.

For non-interactive use, such as scripts or CI, create a Personal Access Token under [**Team Management > MCP Server**](https://www.qwairy.co/dashboard/team/mcp) and pass it as a bearer header. Replace the placeholder with your token and keep it out of shared files and shell history.

```bash theme={null}
claude mcp add --transport http qwairy --scope user https://mcp.qwairy.co --header "Authorization: Bearer qw-usr-REPLACE_WITH_YOUR_TOKEN"
```

### Qwairy tools do not appear after a scope change

Scopes are never expanded on an already-issued token. Remove the server, add it again, and authorize it to pick up new scopes such as `read:measure`. See [OAuth authentication](/mcp/oauth.md).

## Official documentation

Command options, scopes, and management commands are maintained by Anthropic. See [Connect Claude Code to tools via MCP](https://code.claude.com/docs/en/mcp).

Procedure checked against Anthropic's documentation on October 22, 2026.

## Next steps

* [Tools reference](/mcp/tools/discovery.md): what each Qwairy tool does
* [Example conversations](/mcp/examples/getting-started.md): prompts to try
* [All supported clients](/mcp/getting-started.md#choose-a-client)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.