Skip to main content
Qwairy works with MCP clients that support remote servers over Streamable HTTP. Find your client in the table below, open its page for the setup steps, and share that page with teammates who ask whether their assistant is compatible. All clients use the same server URL:
Use the root URL, without appending /mcp. OAuth-capable clients discover Qwairy’s OAuth 2.1 flow from this endpoint. Depending on the client, authorization starts automatically, on first use, or after an explicit sign-in command. For headless clients that cannot complete interactive OAuth, create a Personal Access Token under Team Management > MCP Server. Prefer OAuth whenever the client supports it.
Client interfaces change independently of Qwairy. The stable inputs are the server URL and OAuth. Each client page states the date its procedure was checked against the vendor’s documentation.

​
Prerequisites

  • Access to an active Qwairy team on a Starter plan or higher, including paid Agency plans
  • A client that supports remote MCP servers over Streamable HTTP
  • To query monitoring data: at least one accessible active brand with generated responses
Some clients add their own plan or administrator requirements. Each client page lists them under Before you start.

​
Choose a client

A connection is user-scoped: it reaches every MCP-eligible workspace you can access. Each brand-scoped tool call resolves one brand in one team.

​
Authorize the connection

After you add the server, your client starts the OAuth flow:
  1. A browser window opens with the Qwairy sign-in page
  2. Sign in with your Qwairy account
  3. Authorize the connection
  4. You’re redirected back to the client: the connection is active
Your credentials are never shared with the AI client. Authentication uses OAuth 2.1 with PKCE: only a secure, scoped access token is exchanged. Learn more about OAuth.
Qwairy registers OAuth clients automatically through its dynamic registration endpoint, so you never enter a client ID or client secret yourself. If your client offers a choice, select automatic registration.

​
Check that the connection works

Send this message in a conversation where Qwairy is enabled:
The assistant should call Qwairy’s list_brands tool and display the accessible brands. Approve the tool call if the client 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.

​
Query your data

Try these example prompts:

​
Troubleshooting

Client-specific problems, such as a missing menu or an organization policy, are covered on the page of each client in the table above.

​
”Server not found” error

  • Use the root endpoint https://mcp.qwairy.co; do not append /mcp
  • Check that your config file is valid JSON
  • Restart your AI client after editing the config

​
”Authentication failed” error

  1. Check that you have a Starter plan or higher
  2. Ensure you’re signing in with the correct Qwairy account
  3. Try disconnecting and reconnecting

​
The client asks for a client ID or reports invalid_client

Choose automatic client registration if the client offers it. Do not enter your Qwairy password, a REST API key, or a personal token in the client ID or client secret fields. Qwairy accepts only client IDs registered through https://auth.qwairy.co/register.

​
”No data returned”

Make sure you have:
  • At least one brand with status “Live”
  • Monitoring enabled with generated responses
  • Recent data (within the last 30 days by default)

​
Client doesn’t support remote MCP?

Prefer a client with native Streamable HTTP and OAuth support. If your organization approves a bridge, pin its version and follow that client’s documented OAuth callback procedure. See Connect another client.

​
Rate limits

The MCP server currently allows 300 requests per minute and 3,000 requests per day per access token. HTTP 429 responses expose X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset for the per-minute window; successful responses do not expose quota headers. The JSON error message’s retry delay is derived from that same per-minute reset. Apply exponential backoff, and if requests remain limited after the reset, stop automated retries and resume later because the daily cap may be exhausted. These service limits can evolve; treat the documented values as current policy and 429 headers as burst-window guidance, not a complete daily-quota signal.

​
Measurement tools and scopes

Tools that read off-AI analytics (Search Console, Bing, referrer traffic, AI revenue, crawler activity) live under the Measure category and require the read:measure scope. If you connected before this scope existed, disconnect and reconnect to pick it up: scopes are never expanded silently on an already-issued token. See Measure Tools.

​
Next steps

Tools Reference

Learn what each tool does and its parameters

Example Conversations

See real-world usage examples

Combine with Other Tools

Connect Qwairy with your SEO, CMS, and project management tools

OAuth Setup

How authentication works under the hood