Skip to main content
The Qwairy MCP Server lets AI assistants access your GEO monitoring data directly. Ask questions about your brand’s AI visibility in natural language and get instant insights — from any MCP-compatible client.

What is MCP?

The Model Context Protocol (MCP) is an open standard that allows AI assistants to securely connect to external data sources. With Qwairy’s MCP server, you can:
  • Query your GEO performance — “How is my brand performing across AI providers?”
  • Analyze competitors — “Who are my top competitors in AI responses?”
  • Track sources — “Which domains cite my brand most often?”
  • Monitor prompts — “Show me recent AI responses for my monitored queries”

Supported Clients

Qwairy’s MCP server works with any client that supports the Model Context Protocol:

Claude Desktop / Claude.ai

Via Connectors settings

ChatGPT

Via Connectors (Pro/Team/Enterprise)

Cursor

Built-in MCP support

Claude Code

One-command CLI setup

VS Code / Copilot

Via MCP extension

Windsurf

Built-in MCP support
Any MCP-compatible client can connect using the server URL https://mcp.qwairy.co. See Getting Started for setup instructions.

Quick Example

Once connected, you can have conversations like:
You: What’s my brand’s GEO score this month? AI Assistant: Your brand “Acme Corp” has a GEO score of 72/100. Here’s the breakdown:
  • Mention Rate: 45% (brand mentioned in 45% of AI responses)
  • Source Rate: 28% (your domain cited in 28% of responses)
  • Share of Voice: 38% (vs competitors)
  • Sentiment: 78/100

Available Tools

The MCP server provides 41 tools across 10 categories:
CategoryToolsDescription
Discoverylist_brands, get_overviewList brands, get cockpit overview with scores and trends
Performanceget_brand_performance, get_visibility_trend, get_sentiment_trend, get_provider_breakdown, get_keyword_triggers, get_topicsGEO scores, trends, provider and keyword analysis
Competitorsget_competitors, get_competitor_evolution, get_competitor_comparison, get_competitor_positionRankings, trends, head-to-head, deep-dive
Prompts & Responsesget_prompts, get_prompt_answers, get_answers, get_answer_details, get_prompt_signalsBrowse prompts, AI responses, attack/defend signals
Sourcesget_source_domains, get_source_urls, get_source_profile, get_backlink_opportunitiesCited domains, URLs, source deep-dive, backlink outreach
Strategicget_content_opportunities, get_brand_perception, get_perception_history, get_technical_status, get_site_diagnostics, get_actionsPerception SWOT, technical SEO, per-page diagnostics, Action Center
Vertical Insightsget_shopping_insights, get_social_insights, get_local_insights, get_query_fan_out, get_sponsored_contentShopping, social, local, web search queries, sponsored content
Measureget_search_console_metrics, get_bing_metrics, get_referrer_analytics, get_ai_revenue, get_crawler_activity, get_page_performanceSearch Console, Bing, AI traffic and revenue, crawler activity
Deep-Diveget_page_presence, get_matrixOn-page presence, visibility matrix
Documentationsearch_documentationSearch Qwairy product docs, guides, and GEO strategies
The Measure tools require the read:measure scope and a connected integration (Google Search Console, Bing, or Google Analytics). See Measure Tools.

Requirements

  • Qwairy Starter plan or higher
  • Any MCP-compatible AI client (Claude, Cursor, VS Code, Windsurf…)
  • Active monitored brands with GEO data

Next Steps

Getting Started

Set up the MCP connection in 2 minutes

OAuth Setup

How authentication works

Discovery Tools

List your monitored brands

Performance Tools

GEO scores and topic metrics

Competitor Tools

Analyze competitive landscape

Response Tools

Browse prompts and AI responses

Source Tools

Track cited domains and URLs

Strategic Tools

Actions, perception, technical status

Insight Tools

Shopping, social, local, queries

Measure Tools

Search Console, AI traffic, revenue, crawlers

Deep-Dive Tools

Page presence, matrix, profiles

Documentation Tool

Search product docs and GEO guides

Examples

Real conversation examples