Skip to main content
Qwairy works as a custom connector in Claude on claude.ai and in Claude Desktop. Once it is connected, you can ask Claude questions about your brands and Claude reads the answers from Qwairy. The connection is read-only. You do not need a terminal, an API key, or a claude_desktop_config.json file.

​
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.
  • A Claude plan that allows custom connectors. The free plan allows one custom connector.
  • On Claude Team and Enterprise, an authorized organization owner must add Qwairy once for the organization (see the note in the steps below). Members then connect with their own Qwairy account.

​
Connect Qwairy to Claude

1

Open your Claude connectors

Open Customize > Connectors in Claude. Some versions show this under Settings > Connectors.
2

Add Qwairy

Click Add or + Add, then Add custom connector. If Claude shows a Custom menu, choose Web.Enter these values:Use this exact URL, without appending /mcp.
On Team and Enterprise, an organization owner adds Qwairy under Organization settings > Connectors > Add > Custom > Web with the same values. Members then open Customize > Connectors, find Qwairy, and click Connect.
3

Choose the OAuth client

Continue to the authentication settings. Use OAuth and choose Sign in now when offered.If an OAuth client setting appears, choose Register automatically, even if Use Claude’s published identity (Recommended) is preselected. Qwairy only accepts client IDs registered through its own registration endpoint, so you do not need Use your own OAuth client either. Finish adding the connector.
4

Authorize Qwairy

Click Connect if sign-in has not started. Sign in with the Qwairy account that has access to your brands, review the requested access, and approve it. Return to Claude after authorization.
5

Enable Qwairy in your conversation

Open a conversation, click + next to the message box, then Connectors, and enable Qwairy for that conversation.

​
Check that the connection works

Send this message in the conversation where you enabled Qwairy:
Claude should call Qwairy’s list_brands tool and display the accessible brands. Approve the tool call if Claude asks. A general answer about Qwairy without a tool call does not confirm the connection. Then choose a returned brand and ask for its performance over a specific period.

​
Troubleshooting

​
Claude does not show Add custom connector

On Claude Team and Enterprise, an authorized organization owner must first add Qwairy under Organization settings > Connectors. Members then open their own Customize > Connectors, find Qwairy, and click Connect with their own Qwairy account. Enterprise can also delegate connector management through a custom role. On a personal account, check Claude’s custom connector availability and limits. The free plan allows one custom connector.

​
Qwairy is connected, but Claude does not use it

Enable Qwairy under + > Connectors in the current conversation, then send the verification message above. Adding a connector to your account and enabling it in a conversation are separate steps.

​
Claude asks for a client ID or reports invalid_client

Return to the connector’s OAuth settings and select Register automatically. If Use Claude’s published identity is selected, Qwairy may reject the client because it was not registered through Qwairy’s registration endpoint. Do not enter your Qwairy password, a REST API key, or a personal token in the client ID or client secret fields.

​
Authorization fails or shows the wrong brands

Sign in with the Qwairy account that has access to your brands, and check that its team is on a Starter plan or higher. To start over, remove the connector, add it again, and authorize with the correct account. For other errors, see general troubleshooting.

​
Official documentation

Claude’s interface labels and plan restrictions are maintained by Anthropic. See Get started with custom connectors using remote MCP. Procedure checked against Anthropic’s documentation on October 22, 2026.

​
Next steps