---
title: "Google Search Console MCP Server"
description: "Connect AI assistants to your GSC data with Model Context Protocol. Compare GSC MCP servers and set up gscdump for Claude Desktop, Cursor, and Claude Code."
canonical_url: "https://gscdump.com/learn-google-search-console/ai-agents/mcp-server"
last_updated: "2026-04-30T06:38:20.284Z"
---

Model Context Protocol (MCP) lets AI assistants access live data during conversations. For SEO workflows, this means Claude can query your GSC data, analyze trends, and identify opportunities, without copy-pasting CSV exports.

## What is MCP

MCP is an open protocol created by Anthropic that connects AI assistants to external data sources and tools. Think of it as a universal adapter: one MCP server works with Claude Desktop, Cursor, Claude Code, or any MCP-compatible client.

Unlike function calling APIs (where you rebuild integrations per provider), MCP servers work everywhere. Unlike RAG systems (which only provide context), MCP enables both data access and actions: AI can read GSC data and trigger indexing API calls.

**MCP adoption in 2026:**

- **1,000+ public servers** available as of early 2025 ([cdata.com MCP directory](https://www.cdata.com/mcp/))
- **4% of all public GitHub commits** are authored by Claude Code as of February 2026 ([semianalysis.com report](https://www.semianalysis.com/p/claude-code-is-the-inflection-point))
- **Tipping point year**: 2026 marks the shift from experimental pilots to enterprise-wide standardization (cdata.com)
- **Industry backing**: Anthropic, OpenAI, Google, and Microsoft have all standardized around MCP as the core interface for AI integration.

## Why MCP for SEO

Traditional GSC workflows:

1. Export CSV from GSC
2. Open in spreadsheet
3. Filter/pivot/analyze
4. Repeat for each question

MCP workflow:

1. Ask Claude: "Which pages lost impressions this month?"
2. Claude queries GSC directly
3. Get instant analysis with context

MCP servers enable:

- **Real-time data access** during AI conversations
- **Multi-step analysis** without context switching
- **Automated workflows** (sync, analyze, notify)
- **Historical aggregation** when paired with storage

## GSC MCP Servers Compared

All public GSC MCP servers share the same limitations: 25k row limit (GSC API restriction), manual OAuth/service account setup, no persistent storage, and self-hosted only.

<table>
<thead>
  <tr>
    <th>
      Repo
    </th>
    
    <th>
      Stars
    </th>
    
    <th>
      Key Limitation
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <a href="https://github.com/AminForou/mcp-gsc" rel="nofollow">
        AminForou/mcp-gsc
      </a>
    </td>
    
    <td>
      203
    </td>
    
    <td>
      Python 3.11+, manual OAuth, 25k limit
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://github.com/ahonn/mcp-server-gsc" rel="nofollow">
        ahonn/mcp-server-gsc
      </a>
    </td>
    
    <td>
      96
    </td>
    
    <td>
      Manual service account, 25k limit
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://github.com/Shin-sibainu/google-search-console-mcp-server" rel="nofollow">
        Shin-sibainu/google-search-console-mcp-server
      </a>
    </td>
    
    <td>
      26
    </td>
    
    <td>
      2k QPD URL inspection, 25k limit
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://github.com/surendranb/google-search-console-mcp" rel="nofollow">
        surendranb/google-search-console-mcp
      </a>
    </td>
    
    <td>
      22
    </td>
    
    <td>
      Manual credentials, 25k limit
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        gscdump
      </strong>
    </td>
    
    <td>
      -
    </td>
    
    <td>
      <strong>
        No row limit, permanent storage, hosted
      </strong>
    </td>
  </tr>
</tbody>
</table>

### gscdump MCP Advantages

gscdump is the only MCP server that stores GSC data permanently, removing the 25k row limit and enabling:

- **Unlimited historical queries** across months/years
- **Pre-aggregated data** for instant responses
- **Indexing API integration** (check status, submit URLs)
- **Hosted solution** with OAuth, no credentials to manage
- **Multi-site support** in one MCP server

Technical differences:

- Other servers: Query GSC API → return max 25k rows → forget data
- gscdump: Sync GSC data daily → store in D1 → query unlimited rows → remember history

## Setup: Claude Desktop

Add gscdump MCP server to `claude_desktop_config.json`:

**macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`**Windows:** `%APPDATA%\Claude\claude_desktop_config.json`

```json
{
  "mcpServers": {
    "gscdump": {
      "url": "https://gscdump.com/mcp"
    }
  }
}
```

Restart Claude Desktop. You'll see a 🔌 icon in the bottom-right corner when MCP is connected.

## Setup: Cursor

Add to Cursor's MCP settings:

1. Open Cursor Settings → Features → Model Context Protocol
2. Add new server:

  - Name: `gscdump`
  - URL: `https://gscdump.com/mcp`
3. Restart Cursor

Or edit `~/.cursor/mcp.json` directly:

```json
{
  "servers": {
    "gscdump": {
      "url": "https://gscdump.com/mcp"
    }
  }
}
```

## Setup: Claude Code

Claude Code reads MCP servers from `.mcp.json` in your project root:

```json
{
  "servers": {
    "gscdump": {
      "url": "https://gscdump.com/mcp"
    }
  }
}
```

Commit this file to share MCP access with your team.

## Connecting Your GSC Account

First time using gscdump:

1. Ask Claude: "Show my GSC sites"
2. Claude calls MCP, redirects you to OAuth flow
3. Sign in with Google (gscdump.com handles tokens)
4. Return to Claude: your sites are now available

gscdump stores OAuth tokens securely and refreshes them automatically. No service account JSON files, no credential management.

gscdump stores OAuth tokens securely and refreshes them automatically. No service account JSON files, no credential management.

## Example Prompts

### Basic Queries

**"Show my GSC sites"**

```md
Show my GSC sites
```

Lists all sites in your account with verification status.

**"Which pages got the most clicks last month?"**

```md
Which pages got the most clicks last month?
```

Queries synced data, returns top pages sorted by clicks.

**"Show keyword trends for 'mcp server' over 90 days"**

```md
Show keyword trends for 'mcp server' over 90 days
```

Aggregates historical data, shows position/clicks over time.

### Analysis Prompts

**"Find pages that lost impressions this month"**

```md
Find pages that lost impressions this month
```

Compares current vs previous period, identifies declining pages.

**"Which keywords rank 4-15 with high impressions?"**

```md
Which keywords rank 4-15 with high impressions?
```

Surfaces "striking distance" opportunities for optimization.

**"Show device breakdown for /blog/mcp-guide"**

```md
Show device breakdown for /blog/mcp-guide
```

Returns mobile vs desktop performance for specific URL.

### Indexing API

**"Check indexing status for /new-article"**

```md
Check indexing status for /new-article
```

Queries Google's URL Inspection API via MCP.

**"Submit /products/new-widget for indexing"**

```md
Submit /products/new-widget for indexing
```

Sends indexing request through MCP server.

**"Get last 10 indexing requests"**

```md
Get last 10 indexing requests
```

Shows recent submission history.

## MCP vs RAG

RAG (Retrieval-Augmented Generation) embeds static content for context. MCP provides real-time data access and actions.

**RAG limitations:**

- Stale data (embeddings generated once)
- No actions (read-only context)
- Manual updates required

**MCP advantages:**

- Live data (queries current state)
- Actions enabled (submit URLs, trigger syncs)
- Automatic updates (data refreshes daily)

As [airbyte.com's AI strategy](https://airbyte.com/blog/ai-agents-mcp) puts it: "MCP lets AI read AND do, not just read." For SEO, this means Claude can both analyze your GSC data and submit URLs for indexing in the same conversation.

## MCP vs Function Calling

Function calling requires rebuilding integrations for each AI provider. MCP works everywhere.

**Function calling:**

- Provider-specific (OpenAI functions != Claude tools)
- Rebuild for each AI vendor
- Tight coupling to provider APIs

**MCP:**

- Provider-agnostic (one server, all clients)
- Works with Claude, GPT-5, or custom apps
- Decoupled architecture

MCP servers are future-proof: when GPT-5 adds MCP support, your gscdump integration works immediately.

## Privacy & Data Storage

gscdump stores GSC data in isolated per-user databases:

- **OAuth tokens** encrypted with AES-256
- **GSC data** stored in Cloudflare D1 (SQLite)
- **Per-user isolation** (one database per Google account)
- **GDPR compliant** (right to deletion)

MCP queries hit your isolated database, not shared tables. Your data never mixes with other users.

## Limitations

**GSC API restrictions:**

- 2-3 day data lag (Google's reporting delay)
- 16-month retention (older data disappears)
- URL inspection limited to verified sites

**gscdump syncing:**

- Daily sync (not real-time intraday updates)
- Requires OAuth (no service account support yet)
- Free tier limited to 5 sites

## Developer Resources

**MCP Specification:**[https://spec.modelcontextprotocol.io](https://spec.modelcontextprotocol.io)

**gscdump API Docs:**[https://gscdump.com/docs/api](https://gscdump.com/docs/api)

**Example Integrations:**

- [Claude Desktop setup guide](https://gscdump.com/docs/mcp/claude-desktop)
- [Cursor integration](https://gscdump.com/docs/mcp/cursor)
- [Claude Code workflow examples](https://gscdump.com/docs/mcp/claude-code)

## Next Steps

1. [Set up gscdump MCP](/docs/mcp/setup) in your preferred editor
2. Connect your GSC account via OAuth
3. Try example prompts to explore your data
4. Build custom workflows with Claude Code

MCP transforms GSC from a reporting tool into an AI-queryable data source. Your SEO analysis is now a conversation.

## Related Articles

- [Claude Code for SEO](/learn-google-search-console/ai-agents/claude-code-seo) - Specific prompts and workflows for SEO with Claude Code
- [AI SEO Workflows](/learn-google-search-console/ai-agents/seo-workflows) - Automated analysis patterns with MCP
- [GSC API Authentication](/learn-google-search-console/api/authentication) - OAuth and credential management for the GSC API
- [GSC API Rate Limits](/learn-google-search-console/api/rate-limits) - Understanding API quotas and pagination
