QuickSEO MCP Server

Connect any Model Context Protocol client — Claude Desktop, Claude Code, Cursor, or your own — to read your QuickSEO data and act on it. Pull AI visibility scores, Google Search Console rows, tracked prompts, and competitors directly into your agent workflows.

Introduction

The QuickSEO MCP server exposes your sites, AI visibility scans, Google Search Console performance, tracked prompts, and competitors through a single, agent-ready endpoint. Pick a starting point below or follow the page top to bottom for the full setup.

Server URL

Point your MCP client at this endpoint. All transports (HTTP + SSE) are supported.

https://quickseo.ai/api/mcp

Connect your agent

Pick the path for your client. All four trigger the same one-click OAuth flow on first use.

Claude Code

Run this in your terminal. On recent versions you can also use the /mcp slash command.

claude mcp add --transport http quickseo https://quickseo.ai/api/mcp

Claude Desktop

In Claude Desktop, open Customize → Connectors, click the + icon, choose Add custom connector, then fill in:

Name: QuickSEO
Remote MCP server URL: https://quickseo.ai/api/mcp
Click Add, then approve the OAuth prompt on first use.

Cursor

One-click install — opens Cursor and pre-fills the MCP server config.

Add to Cursor

Other MCP clients

For any MCP client that reads a JSON config (and doesn't yet support remote HTTP-transport servers natively), add this block to its config file. It uses mcp-remote as a local bridge.

{
  "mcpServers": {
    "quickseo": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://quickseo.ai/api/mcp"]
    }
  }
}

Authentication

The QuickSEO MCP server speaks OAuth 2.1 with Dynamic Client Registration and PKCE. Your MCP client registers itself the first time it connects, redirects you to the QuickSEO consent screen, and receives a short-lived bearer token bound to your user account.

You stay logged in via the QuickSEO browser session — there is no copy-pasting of API keys or personal access tokens. You can revoke any connection at any time from your account page.

Available tools

Seven tools cover the read and write surfaces of your QuickSEO data.

list_sites

List all sites the authenticated QuickSEO user owns. Returns each site UUID, URL, brand name, GSC property, and whether the site is active. Call this first to discover the siteId values you pass to the other tools.

get_site_overview

Return a combined overview for one site over the last 30 days: latest AI visibility scores (overall + per-model for ChatGPT, Claude, Gemini, Perplexity) and Google Search Console totals (clicks, impressions, CTR, average position).

get_search_analytics

Fetch Google Search Console rows for a site over a date range. Use dimensions to break down the result; defaults to DATE. Example: dimensions=["QUERY","PAGE"] returns clicks/impressions/CTR/position grouped by query+page.

get_ai_visibility

Return AI visibility scores for a site across the chosen period. Includes the full per-period series plus a latest summary (overall + ChatGPT, Claude, Gemini, Perplexity scores, total_prompts, mentioned_count).

list_prompts

List the AI prompts currently tracked for a site. These are the user-facing prompts that get run against ChatGPT, Claude, Gemini, and Perplexity for AI visibility scoring.

add_prompt

Add a new AI prompt to track for a site and trigger an immediate scan against ChatGPT, Claude, Gemini, and Perplexity. Subject to the user prompt-quota.

list_competitors

List competitor domains discovered (or manually tracked) for a site, with total citations, status, and first/last seen timestamps. Filter by status — tracked, suggested, or dismissed.

Suggested prompts

Paste any of these into your connected agent to see what QuickSEO can do. They use the read tools by default; the last one writes a new tracked prompt.

Quick snapshot
Using QuickSEO MCP, give me a one-paragraph health check on my site: AI visibility score per model (ChatGPT, Claude, Gemini, Perplexity), plus Google Search Console clicks, impressions, CTR, and average position over the last 30 days. Flag anything that looks off.
AI visibility deep dive
Using QuickSEO MCP, list every prompt I track for my site and tell me which AI models currently mention my brand for each one. Group the results by 'mentioned everywhere', 'mentioned by some', and 'never mentioned'. Then suggest 5 new prompts to track that I'm probably missing.
Competitor landscape
Using QuickSEO MCP, pull my tracked and suggested competitors with their citation counts and first/last seen dates. Which competitor is gaining the most across AI models in the last 30 days? Recommend one I should add to my tracked list.
GSC quick wins
Using QuickSEO MCP, pull Google Search Console data for the last 30 days grouped by QUERY and PAGE. Find queries with more than 200 impressions and CTR below 2%. For each, suggest one specific change to the page (title, meta description, or on-page copy) to lift CTR.
Branded vs non-branded
Using QuickSEO MCP, compare my branded vs non-branded AI visibility for the last 90 days. Which model indexes my brand best? Which is weakest on non-branded prompts? Give me 3 concrete actions to lift the weak surface.
Add a prompt and scan
Using QuickSEO MCP, add the prompt 'best AI SEO tool for SMBs' to my site and run a scan. When it finishes, tell me which models mentioned my brand, what they said, and which competitor domains were cited.
Weekly progress report
Using QuickSEO MCP, compare this week vs last week for both AI visibility (per model) and Google Search Console (clicks, impressions, CTR, position). Write a 5-bullet summary I can share with my team, ending with the single most important thing to focus on next week.

Rate limits

120 requests per minute per user, sliding 60-second window. When you exceed the limit the server responds with HTTP 429 and a Retry-After header.

Need a hand getting set up? Email support@quickseo.ai.