Skip to main content
Qwairy works with any MCP client that supports remote servers over Streamable HTTP. Use OAuth when the client supports it, and a Personal Access Token when it cannot complete an interactive sign-in. 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.
  • A client with native Streamable HTTP support
  • For OAuth: a client that supports OAuth 2.1 with PKCE (S256) and dynamic client registration

​
Connect your client

1

Enter the server URL

Add a remote MCP server using the Streamable HTTP transport and this URL, without appending /mcp:
2

Choose the authentication

For OAuth, let the client discover the flow from the server URL and choose automatic client registration. Qwairy registers the client for you, so you do not enter a client ID or client secret. Sign in with the Qwairy account that has access to your brands and approve the access.For headless clients such as automation platforms, scripts, and custom agents, create a Personal Access Token under Team Management > MCP Server and send it as a bearer header:
Keep the token secret and revoke it from the same page when you no longer need it.
If a client only supports stdio, choose a maintained HTTP bridge that your organization has reviewed. Pin an approved package and version instead of executing an unpinned package at runtime. Bridge configuration and OAuth callback support are client-specific.

​
Check that the connection works

In a conversation where Qwairy is enabled, send:
The assistant should call Qwairy’s list_brands tool and display the accessible brands. For a script, call tools/list first and confirm that the Qwairy tools are returned.

​
Troubleshooting

​
The client cannot reach the server

Check that the transport is Streamable HTTP, that the URL is https://mcp.qwairy.co without /mcp, and that your network allows outbound HTTPS.

​
The client asks for a client ID or secret

Choose automatic client registration if the client offers it. You do not need to enter a client ID or client secret. If the client cannot register automatically, use a Personal Access Token instead. See OAuth authentication for the endpoints and the manual registration flow.

​
Authorization fails

Check that the token or account belongs to a team on a Starter plan or higher and that the token was not revoked. See general troubleshooting.

​
Official documentation

Configuration is specific to each client. See your client’s documentation for how to add a remote MCP server, and the Model Context Protocol specification for the transport. Procedure checked against vendor documentation on August 28, 2026.

​
Next steps