Google Search Console (DigestSEO)
MCP server by DigestSEO (AKzar1el)
Query Search Console analytics, inspect URLs, manage sitemaps and find SEO opportunities from your assistant using your own Google OAuth.
Install Google Search Console (DigestSEO)
Runs on your machine. Your client starts it with this command:
Needs Node.js on your computer. The setup steps below show where the command goes in each client.
PORToptional Local HTTP port used by the npm launcher.GSC_ACCESS_MODEoptional Google/Search Console access mode for the local launcher. Use readonly for least privilege or readwrite for the six mutation tools.MCP_GSC_STATE_DIRoptional Optional directory for persistent local Wrangler/KV/Durable Object/OAuth state. When omitted, the npm launcher uses its stable per-user…GOOGLE_CLIENT_IDGoogle OAuth client ID for the local Worker.GOOGLE_CLIENT_SECRETsecret Google OAuth client secret for the local Worker.TOKEN_ENCRYPTION_KEYsecret Base64-encoded 32-byte key used to encrypt stored Google refresh tokens.
Share this server
Opens this page, with the install command and setup steps.
mcp.tc/i/google-search-console-digestseoAbout
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.
What you can do
- 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
Tools 23
server.capabilitiesList the server's tools and report local Google credential state.
sites.listList Search Console properties the connected account can access.
sites.getGet one property and the account's permission level.
analytics.queryImpressions, clicks, CTR and position over a date range with breakdowns.
insights.page_queriesList queries that produced impressions for one page URL.
insights.query_pagesList pages that received impressions for one query.
urls.inspectURL Inspection report for the indexed version of a page.
urls.inspect_manyInspect indexed versions of up to 10 URLs.
sitemaps.listList submitted sitemaps with status and warning and error counts.
sites.addAdd a Search Console property.
sites.deleteRemove a Search Console property.
sitemaps.submitSubmit a sitemap for a property.
Show 11 more tools
sitemaps.deleteRemove a submitted sitemap.
sitemaps.getGet status and details of a submitted sitemap.
insights.quick_winsFind high-impression query/page rows in the opportunity position range.
insights.cannibalizationFind queries where multiple pages compete.
insights.content_decayIdentify pages with the largest recent traffic declines.
indexing.requestRequest an Indexing API update for eligible JobPosting or livestream URLs.
indexing.removeSend a URL_DELETED notification for a previously eligible page.
indexing.statusRead latest Indexing API notifications received for a URL.
indexing.list_pagesList pages with Search Console impressions.
analytics.compareCompare search performance across two date ranges.
reports.weekly_digestGenerate a weekly search performance digest with one recommended action.
From the package’s own manifest, not a live connection, on 4 Oct 2026.
Example 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.
Set up
Every client starts Google Search Console (DigestSEO) on your machine with the same command. Pick yours; the page remembers your choice.
Claude Code
- 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- 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
- Open Settings → Developer → Edit Config. It opens
claude_desktop_config.json. Add:
{
"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>"
}
}
}
}- 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 (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"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:
{
"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
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"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>"
}
}
}
}- 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-gscOr edit ~/.codex/config.toml directly:
[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-gscThis 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.
Embed
Show Google Search Console (DigestSEO) in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/google-search-console-digestseo)<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>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/google-search-console-digestseo.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<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>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/google-search-console-digestseo.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Google Search Console (DigestSEO) card to your site.
Add the mcp.tc card for Google Search Console (DigestSEO), an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/google-search-console-digestseo.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="google-search-console-digestseo"><a href="https://mcp.tc/i/google-search-console-digestseo">Google Search Console (DigestSEO) on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/google-search-console-digestseo)
```
Reference: https://mcp.tc/embedChange history
We read the tool list in this server’s bundle manifest on GitHub every 3 hours and record what changes. Last read 18 Nov 2026, 05:31 UTC.
Follow Google Search Console (DigestSEO) and we’ll email you when something changes.
-
New version 0.4.41 (was 0.4.40). Read from npm.
-
1 tool changed.
Details, 11 Nov 2026, 05:46 UTC
Changed 1
urls.inspect_manydescriptionBeforeInspect Google's indexed versions of up to 10 URLs
with bounded concurrency of 3while preserving one URL Inspection quota unit per URL and input-order results. This does not run live URL tests.AfterInspect Google's indexed versions of up to 10 URLs sequentially while preserving one URL Inspection quota unit per URL and input-order results. This does not run live URL tests.
-
New version 0.4.39 (was 0.4.38). Read from npm.
-
1 tool changed.
Details, 25 Oct 2026, 02:37 UTC
Changed 1
indexing.requestdescriptionBeforeRequest an eligible JobPosting or livestream URL update through Google's restricted Indexing API; this is not a general webpage submission tool.
Google'sdefault publish quotais for onboarding/testing, ongoing usage requires approval,andsubmissions are spam-screened.AfterRequest an eligible JobPosting or livestream URL update through Google's restricted Indexing API; this is not a general webpage submission tool. Google documents a default limit of 200 publish requests/day/project shared by updates and removals; eligibility, quota limits and spam policies still apply.
-
New version 0.4.37 (was 0.4.36). Read from npm.
-
Tracking started: 23 tools.
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 values 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.
Does mcp.tc track changes to Google Search Console (DigestSEO)?
Yes. We follow the tool list in Google Search Console (DigestSEO)’s bundle manifest, and its History tab shows each change we find, plus new versions and edits by its owner. Follow the listing to get an email when it changes.
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.
mcp.tc isn’t affiliated with DigestSEO (AKzar1el). This page was built from Google Search Console (DigestSEO)’s public metadata, last checked on 4 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.