---
title: "MCP · gscdump"
canonical_url: "https://gscdump.com/mcp"
last_updated: "2026-09-13T07:40:21.195Z"
meta:
  description: "gscdump syncs Google Search Console continuously and preserves every day past Google's 16-month window. Connect ChatGPT, Claude, or Codex over MCP with OAuth."
  "og:description": "gscdump syncs Google Search Console continuously and preserves every day past Google's 16-month window. Connect ChatGPT, Claude, or Codex over MCP with OAuth."
  "og:title": "MCP · gscdump"
---

# Your Search Console history, over MCP.

gscdump syncs your Search Console record continuously. Connect with OAuth, then ask ChatGPT or Claude about the whole record.

[**Join the waitlist **](https://gscdump.com/#get-access) [**Read the setup guide **](https://gscdump.com/learn-google-search-console/ai-agents/mcp-server)

Settings → Apps → Create

```
Name
gscdump

MCP server URL
https://gscdump.com/mcp

Authentication
OAuth
```

Use developer mode. Workspace plans can require admin approval.

## What your agent can ask

12 tools

The seven analytics reads answer from your preserved record, sitemap listings come from the synced sitemap tables, and URL inspection calls Google at request time. Each tool publishes its input schema, so the client picks the matching call from a plain question.

<dl>

<dt>list-sites</dt>
<dd>Your connected sites, each with sync status and the oldest and newest dates synced.</dd>

<dt>list-sitemaps</dt>
<dd>Sitemaps for a site: URL counts, errors, warnings, and last-download timestamps.</dd>

<dt>get-analytics</dt>
<dd>Totals for clicks, impressions, CTR, and position over a date range, with an optional daily series.</dd>

<dt>get-keywords</dt>
<dd>Aggregated performance per query.</dd>

<dt>get-keyword-details</dt>
<dd>One keyword in depth: totals, daily series, and the pages that rank for it.</dd>

<dt>get-pages</dt>
<dd>Aggregated performance per URL.</dd>

<dt>get-page-details</dt>
<dd>One page in depth: totals, daily series, and the keywords it ranks for.</dd>

<dt>get-countries</dt>
<dd>Performance broken down by country.</dd>

<dt>get-devices</dt>
<dd>Performance broken down by device: mobile, desktop, tablet.</dd>

<dt>inspect-url</dt>
<dd>Google's indexed snapshot of a URL: verdict, coverage state, canonical signals, last crawl time. Counts against Google's 2,000 inspections per site per day.</dd>

<dt>run-report</dt>
<dd>Composed analysis reports that fan out across multiple analyzers. Cached by input hash, regenerated on demand.</dd>

<dt>gsc-discover-hourly</dt>
<dd>Hourly Discover clicks, impressions, and position per URL for one calendar day, on sites with hourly Discover sync enabled.</dd></dl>

## Hosted and local

### **The platform **

gscdump.com runs the sync and holds the record in open formats. OAuth links each MCP client to your gscdump account. Legacy clients can still send an API key.

https://gscdump.com/mcp

### **The local twin **

The CLI writes exports to your disk. Its stdio MCP server queries Google with the selected authentication. Local mode calls Google directly. Cloud mode uses your platform connection.

```
npx @gscdump/cli init
npx @gscdump/cli mcp --mode local
```

ChatGPT, Claude, and Claude Code can use OAuth. Cursor and Codex can use the API key fallback. The local server uses stdio.

## What the agent can trust

An agent should be able to tell, from the response alone, whether to trust it. The server states what it knows:

<dl>

<dt>meta.dataRange</dt>
<dd>Every analytics answer carries the site's sync status and the synced date window the numbers cover.</dd>

<dt>gscdump.com/retry</dt>
<dd>Every failed call states whether an identical retry can succeed, as a structured hint in the result's <code>_meta</code> and in prose. Transient backpressure comes with a wait in seconds; a broken query says so plainly instead of inviting a retry loop.</dd>

<dt>lastDownloaded</dt>
<dd>Sitemap rows carry their download timestamps, error and warning counts, and the last error, so stale reads as stale.</dd>

<dt>lastCrawlTime</dt>
<dd>URL inspection returns Google's indexed snapshot, dated by when Google last crawled the page rather than presented as live.</dd></dl>

Capture time ships today on the sitemap and inspection surfaces above; analytics answers carry their synced window instead. A Site covers the exact registered host, so its analytics can exclude traffic shown by a broader Search Console property. Apply a matching host filter when comparing totals. Source limits and sync coverage can also cause differences.

## Questions

Private beta. Join the waitlist.

Signups open gradually during beta. Leave your email on the home page and an invite follows when a slot opens.

[**Join the waitlist **](https://gscdump.com/#get-access) [**Install the CLI **](https://www.npmjs.com/package/@gscdump/cli)

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.