Skip to main content
Follow these steps to connect Claude Desktop to your Qwairy GEO monitoring data.

​
Prerequisites

Before you begin, ensure you have:
  • A Qwairy Business plan or higher
  • Claude Desktop installed (download here)
  • At least one active brand with monitoring data

​
Step 1: Configure Claude Desktop

Open your Claude Desktop configuration file: 
open ~/Library/Application\ Support/Claude/claude_desktop_config.json
Add the Qwairy MCP server to your configuration: 
{
  "mcpServers": {
    "qwairy": {
      "url": "https://mcp.qwairy.co",
      "oauth": {
        "authorizationUrl": "https://auth.qwairy.co/authorize",
        "tokenUrl": "https://auth.qwairy.co/token",
        "scopes": ["read:brands", "read:visibility", "read:competitors", "read:sources", "read:prompts", "read:answers", "read:topics"]
      }
    }
  }
}

​
Step 2: Restart Claude Desktop

Close and reopen Claude Desktop to load the new configuration.

​
Step 3: Authorize the Connection

  1. In Claude Desktop, start a new conversation
  2. Claude will detect the Qwairy MCP server and prompt you to connect
  3. Click “Connect to Qwairy”
  4. You’ll be redirected to Qwairy to sign in
  5. Authorize the connection
  6. You’re now connected!
The authorization uses OAuth 2.1 with PKCE for security. Your credentials are never shared with Claude — only a secure access token.

​
Step 4: Start Querying Your Data

Try these example prompts: 
What brands am I monitoring?

Show me my GEO performance for the last 30 days

Who are my top competitors in AI responses?

Which sources cite my brand most often?

​
Troubleshooting

​
”Server not found” error

Ensure your claude_desktop_config.json is valid JSON. Use a JSON validator to check for syntax errors.

​
”Authentication failed” error

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

​
”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)

​
Rate Limits

The MCP server allows 60 requests per minute per connection. This is more than enough for interactive use, but automated scripts should implement appropriate delays.

​
Next Steps

Tools Reference

Learn what each tool does and its parameters

Example Conversations

See real-world usage examples