Google Search Console (DigestSEO)

listing.by

Query Search Console analytics, inspect URLs, manage sitemaps and find SEO opportunities from your assistant using your own Google OAuth.

state.local.long (state.local.title)listing.badge.runs_withstate.key.long

listing.install

listing.local.explain

npx -y @digestseo/mcp-gsc

listing.local.needs listing.local.note

  • PORT listing.env.optional Local HTTP port used by the npm launcher.
  • GSC_ACCESS_MODE listing.env.optional Google/Search Console access mode for the local launcher. Use readonly for least privilege or readwrite for the six mutation tools.
  • MCP_GSC_STATE_DIR listing.env.optional Optional directory for persistent local Wrangler/KV/Durable Object/OAuth state. When omitted, the npm launcher uses its stable per-user…
  • GOOGLE_CLIENT_ID Google OAuth client ID for the local Worker.
  • GOOGLE_CLIENT_SECRET listing.env.secret Google OAuth client secret for the local Worker.
  • TOKEN_ENCRYPTION_KEY listing.env.secret Base64-encoded 32-byte key used to encrypt stored Google refresh tokens.
act.add_to a11y.new_tab

listing.share.h

listing.share.p_local

mcp.tc/i/google-search-console-digestseo

listing.about

Connects to the Google Search Console API so an assistant can list properties, query clicks, impressions, CTR and position, inspect indexed URLs, manage sitemaps, and surface quick wins, keyword cannibalization and content decay. It also covers Google's restricted Indexing API for eligible JobPosting and livestream URLs, and can produce a weekly digest.

Runs locally with npx @digestseo/mcp-gsc, which starts a loopback Streamable HTTP server on 127.0.0.1:8080/mcp, or can be self-hosted on Cloudflare Workers. You supply your own Google OAuth client ID and secret plus a token encryption key, then sign in with Google. A readonly access mode disables the six mutation tools.

listing.can

  • List Search Console properties and check permission levels
  • Query clicks, impressions, CTR and position by query, page, country or device
  • Compare search performance across two date ranges
  • Inspect indexing status of one or up to 10 URLs
  • List, submit, get and delete sitemaps
  • Find quick-win queries, cannibalization and content decay
  • Generate a weekly search performance digest
  • Add or remove properties unless readonly mode is set

listing.tools 23

  • server.capabilities

    List the server's tools and report local Google credential state.

  • sites.list

    List Search Console properties the connected account can access.

  • sites.get

    Get one property and the account's permission level.

  • analytics.query

    Impressions, clicks, CTR and position over a date range with breakdowns.

  • insights.page_queries

    List queries that produced impressions for one page URL.

  • insights.query_pages

    List pages that received impressions for one query.

  • urls.inspect

    URL Inspection report for the indexed version of a page.

  • urls.inspect_many

    Inspect indexed versions of up to 10 URLs.

  • sitemaps.list

    List submitted sitemaps with status and warning and error counts.

  • sites.add

    Add a Search Console property.

  • sites.delete

    Remove a Search Console property.

  • sitemaps.submit

    Submit a sitemap for a property.

listing.tools_more
  • sitemaps.delete

    Remove a submitted sitemap.

  • sitemaps.get

    Get status and details of a submitted sitemap.

  • insights.quick_wins

    Find high-impression query/page rows in the opportunity position range.

  • insights.cannibalization

    Find queries where multiple pages compete.

  • insights.content_decay

    Identify pages with the largest recent traffic declines.

  • indexing.request

    Request an Indexing API update for eligible JobPosting or livestream URLs.

  • indexing.remove

    Send a URL_DELETED notification for a previously eligible page.

  • indexing.status

    Read latest Indexing API notifications received for a URL.

  • indexing.list_pages

    List pages with Search Console impressions.

  • analytics.compare

    Compare search performance across two date ranges.

  • reports.weekly_digest

    Generate a weekly search performance digest with one recommended action.

listing.prov.mcpb_on

listing.prompts

  • Which queries brought the most clicks to my site last month?

  • Inspect these 5 URLs and tell me which are not indexed.

  • Find pages competing for the same search queries.

  • Compare my search performance this month against last month.

listing.setup.h

listing.setup.local

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio google-search-console-digestseo --env "GOOGLE_CLIENT_ID=<YOUR_GOOGLE_CLIENT_ID>" --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --env "TOKEN_ENCRYPTION_KEY=<YOUR_TOKEN_ENCRYPTION_KEY>" -- npx -y @digestseo/mcp-gsc
  1. Start Claude Code and type /mcp. google-search-console-digestseo should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "google-search-console-digestseo": {
      "command": "npx",
      "args": [
        "-y",
        "@digestseo/mcp-gsc"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "<YOUR_GOOGLE_CLIENT_ID>",
        "GOOGLE_CLIENT_SECRET": "<YOUR_GOOGLE_CLIENT_SECRET>",
        "TOKEN_ENCRYPTION_KEY": "<YOUR_TOKEN_ENCRYPTION_KEY>"
      }
    }
  }
}
  1. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Add to Cursor a11y.new_tab

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "google-search-console-digestseo": {
      "command": "npx",
      "args": [
        "-y",
        "@digestseo/mcp-gsc"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "<YOUR_GOOGLE_CLIENT_ID>",
        "GOOGLE_CLIENT_SECRET": "<YOUR_GOOGLE_CLIENT_SECRET>",
        "TOKEN_ENCRYPTION_KEY": "<YOUR_TOKEN_ENCRYPTION_KEY>"
      }
    }
  }
}

Needs Node.js on your computer. Replace the placeholders with your own values.

VS Code

Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:

.vscode/mcp.json
{
  "servers": {
    "google-search-console-digestseo": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@digestseo/mcp-gsc"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "<YOUR_GOOGLE_CLIENT_ID>",
        "GOOGLE_CLIENT_SECRET": "${input:google-client-secret}",
        "TOKEN_ENCRYPTION_KEY": "${input:token-encryption-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "google-client-secret",
      "description": "GOOGLE_CLIENT_SECRET",
      "password": true
    },
    {
      "type": "promptString",
      "id": "token-encryption-key",
      "description": "TOKEN_ENCRYPTION_KEY",
      "password": true
    }
  ]
}

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "google-search-console-digestseo": {
      "command": "npx",
      "args": [
        "-y",
        "@digestseo/mcp-gsc"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "<YOUR_GOOGLE_CLIENT_ID>",
        "GOOGLE_CLIENT_SECRET": "<YOUR_GOOGLE_CLIENT_SECRET>",
        "TOKEN_ENCRYPTION_KEY": "<YOUR_TOKEN_ENCRYPTION_KEY>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add google-search-console-digestseo --env "GOOGLE_CLIENT_ID=<YOUR_GOOGLE_CLIENT_ID>" --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --env "TOKEN_ENCRYPTION_KEY=<YOUR_TOKEN_ENCRYPTION_KEY>" -- npx -y @digestseo/mcp-gsc

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.google-search-console-digestseo]
command = "npx"
args = ["-y", "@digestseo/mcp-gsc"]
env = { GOOGLE_CLIENT_ID = "<YOUR_GOOGLE_CLIENT_ID>", GOOGLE_CLIENT_SECRET = "<YOUR_GOOGLE_CLIENT_SECRET>", TOKEN_ENCRYPTION_KEY = "<YOUR_TOKEN_ENCRYPTION_KEY>" }

Needs Node.js on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "GOOGLE_CLIENT_ID=<YOUR_GOOGLE_CLIENT_ID>" -e "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" -e "TOKEN_ENCRYPTION_KEY=<YOUR_TOKEN_ENCRYPTION_KEY>" google-search-console-digestseo npx -- -y @digestseo/mcp-gsc

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "google-search-console-digestseo": {
      "command": "npx",
      "args": [
        "-y",
        "@digestseo/mcp-gsc"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "<YOUR_GOOGLE_CLIENT_ID>",
        "GOOGLE_CLIENT_SECRET": "<YOUR_GOOGLE_CLIENT_SECRET>",
        "TOKEN_ENCRYPTION_KEY": "<YOUR_TOKEN_ENCRYPTION_KEY>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer. Replace the placeholders with your own values.

listing.faq

Can I paste mcp.tc/i/google-search-console-digestseo into my MCP client?

No. Google Search Console (DigestSEO) runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @digestseo/mcp-gsc.

Does Google Search Console (DigestSEO) need an API key?

Yes. It reads GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET and TOKEN_ENCRYPTION_KEY from its environment, and GOOGLE_CLIENT_SECRET and TOKEN_ENCRYPTION_KEY are secrets. Put the value in your client's config on your own machine, never in a shared file.

Is Google Search Console (DigestSEO) a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y @digestseo/mcp-gsc, which needs Node.js.

What can Google Search Console (DigestSEO) do?

It has 23 tools, including server.capabilities, sites.list and sites.get. You can list Search Console properties and check permission levels, query clicks, impressions, CTR and position by query, page, country or device and compare search performance across two date ranges.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Who wrote this page?

mcp.tc's robot read Google Search Console (DigestSEO)'s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead_local listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![Google Search Console (DigestSEO) on mcp.tc](https://mcp.tc/i/google-search-console-digestseo/badge.svg)](https://mcp.tc/i/google-search-console-digestseo)
HTML
<a href="https://mcp.tc/i/google-search-console-digestseo"><img src="https://mcp.tc/i/google-search-console-digestseo/badge.svg" alt="Google Search Console (DigestSEO) on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/google-search-console-digestseo.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/google-search-console-digestseo" title="Google Search Console (DigestSEO) on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json_local

https://mcp.tc/i/google-search-console-digestseo.json

listing.em.fields

listing.related

listing.more_in

  • GEO Tracker by DigestSEO

    DigestSEO (AKzar1el)

    state.local.label (state.local.title)

    Track which AI assistants cite your brand across seven AI search surfaces and compare against competitors, with data stored locally.

    mcp.tc/i/geo-tracker-by-digestseo

  • Web Validator by DigestSEO

    DigestSEO (AKzar1el)

    state.ok.label (state.ok.title)

    Audit public webpages and supplied markup for HTML, CSS, SEO, JSON-LD and link issues.

    mcp.tc/i/web-validator-by-digestseo

  • TrendPulse

    AKzar1el

    state.local.label (state.local.title)

    Search Google News and Google Trends for keyword, market, SEO and content research, with article extraction and growth metrics.

    mcp.tc/i/trendpulse

  • Google Search Console (mcp-gsc)

    Amin Foroutan

    state.local.label (state.local.title)

    Analyze Google Search Console performance, URL inspection, indexing and sitemaps through natural language.

    mcp.tc/i/search-console

  • Google Adsvf.sr

    Google

    state.local.label (state.local.title)

    Query Google Ads accounts with GAQL and inspect campaign data and performance metrics through the Google Ads API.

    mcp.tc/i/google-ads

  • Publora

    Marketing & SEO

    state.auth.label (state.auth.title)

    Schedule and publish social media posts to 10 platforms, including LinkedIn, X, Instagram, TikTok and YouTube.

    mcp.tc/i/publora

listing.disclaimer_checked