QueryScope MCP

An AI SEO agent that integrates with your IDE to analyze your repository, identify buyer search intent, and track performance via Google Search Console. It allows agents to propose SEO strategies, execute specific optimization moves, and measure results against historical data without manual exports.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-26Operated by QueryScope

MCP endpoint (Streamable HTTP)

https://mcp.queryscope.dev/mcp

Vendor documentation

What you can do with it

Analyze repository content to identify high-value buyer search queries
Track keyword rankings and performance metrics from Google Search Console
Propose and execute specific on-page SEO changes
Measure the impact of SEO changes over time using historical data

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http queryscope-mcp https://mcp.queryscope.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add queryscope-mcp --url https://mcp.queryscope.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable queryscope-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "queryscope-mcp": {
      "url": "https://mcp.queryscope.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "queryscope-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.queryscope.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start queryscope-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "queryscope-mcp": {
      "type": "http",
      "url": "https://mcp.queryscope.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http queryscope-mcp https://mcp.queryscope.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "queryscope-mcp": {
      "url": "https://mcp.queryscope.dev/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "queryscope-mcp": {
      "serverUrl": "https://mcp.queryscope.dev/mcp"
    }
  }
}

Ground your agent in cited data

QueryScope MCP gives your agent tools. Koskamo gives it reviewed, cited facts to check its answers against. Add it as a second MCP server; public reads need no API key.

Connect Koskamo Browse datasets

See all 1,042

Do you run QueryScope MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing