io.github.sudomichael/search-console-mcp

Google Search Console for any MCP client - 30-second login, no Google Cloud project. Read-only.

GitHub

No known CVEs

No license

Maintenance unknown

No commit data

Works with most clients

Transport: stdio

0 tools

Grade F

Edit this pageView history

Search Cloud

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-sudomichael-search-console-mcp": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-sudomichael-search-console-mcp)](https://mcppedia.org/s/io-github-sudomichael-search-console-mcp)

Read me

What io.github.sudomichael/search-console-mcp does

Google Search Console for any MCP client - 30-second login, no Google Cloud project. Read-only.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

15/100across 5 weighted dimensions

How we score →

0255075100

−85

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.sudomichael/search-console-mcp safe to use?: io.github.sudomichael/search-console-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.sudomichael/search-console-mcp?: io.github.sudomichael/search-console-mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.sudomichael/search-console-mcp?: io.github.sudomichael/search-console-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Similar servers

Others in search / cloud

View all →

Brave Search MCP Server98

Web and local search using Brave Search API

87.9k 2

Gpt Researcher95

An autonomous agent that conducts deep research on any data using any LLM providers

28.0k 5

Socraticode MCP Server95

MCP server for local codebase indexing, semantic search, and code dependency graphs.

3.1k 4

Modelcontextprotocol94

The official MCP server implementation for the Perplexity API Platform

2.4k 4

MCP Security Weekly

Get CVE alerts and security updates for io.github.sudomichael/search-console-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Google Search Console │ ▼ search-console-mcp ← runs on your machine, read-only │ ▼ Claude / Cursor / any MCP client │ ▼ "Why did my traffic drop?"

	This server	Typical GSC MCP setup
Setup	`npx … login`, sign in, done (~30s)	Create a Google Cloud project, enable the API, create OAuth credentials, download JSON, point config at it
Runtime	Node — `npx`, nothing to install	Python + uv/venv
Can it modify your site data?	Impossible — read-only scope by construction	Write scopes with destructive ops "disabled by default"
Analyses	5 built-in (checkup, cannibalization, striking distance, traffic drop, indexing audit)	Bring your own prompts

This server

Typical GSC MCP setup

Setup

npx … login, sign in, done (~30s)

Create a Google Cloud project, enable the API, create OAuth credentials, download JSON, point config at it

Runtime

Node — npx, nothing to install

Python + uv/venv

Can it modify your site data?

Impossible — read-only scope by construction

Write scopes with destructive ops "disabled by default"

Analyses

5 built-in (checkup, cannibalization, striking distance, traffic drop, indexing audit)

Bring your own prompts

What it feels like

You: Which of my pages are closest to page one? Claude: Three real opportunities, by impressions at stake: 1. /pricing — "scoreboard app pricing" sits at position 11.2 with 2,400 impressions/mo and almost no clicks. One position-group jump is worth ~90 clicks/mo. The title doesn't contain the query; start there. 2. /templates/trivia — position 12.8 on "trivia scoreboard", 1,100 impressions/mo. The page ranks but has no H2 matching the intent. 3. /blog/keep-score-online — position 9.4, already page one on some days. It's cannibalizing with /features — run cannibalization_check before touching it.

(Illustrative output — shape and numbers are what the tools return from your real data.)

Built-in SEO analysts

Five ready-made analyses ship as MCP prompts — slash-commands in clients that support them. Outcomes, not API calls:

Prompt	What you get
`seo_checkup`	Trend vs last month, biggest movers, and the top 3 moves worth making
`cannibalization_check`	Queries where two of your pages compete — which should win, and how to fix it
`striking_distance`	Queries sitting at position 5–15 — the fastest traffic you're not getting, with the fix per page
`traffic_drop`	When the drop started, which pages/queries lost, indexed-or-not, most likely cause
`indexing_audit`	Sitemap status + index inspection of your top pages, with plain-language fixes

Prompt

What you get

seo_checkup

Trend vs last month, biggest movers, and the top 3 moves worth making

cannibalization_check

Queries where two of your pages compete — which should win, and how to fix it

striking_distance

Queries sitting at position 5–15 — the fastest traffic you're not getting, with the fix per page

traffic_drop

When the drop started, which pages/queries lost, indexed-or-not, most likely cause

indexing_audit

Sitemap status + index inspection of your top pages, with plain-language fixes

Frequently Asked Questions

Is io.github.sudomichael/search-console-mcp safe to use?

io.github.sudomichael/search-console-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.sudomichael/search-console-mcp?

io.github.sudomichael/search-console-mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.

What AI clients work with io.github.sudomichael/search-console-mcp?

io.github.sudomichael/search-console-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Google Search Console │ ▼ search-console-mcp ← runs on your machine, read-only │ ▼ Claude / Cursor / any MCP client │ ▼ "Why did my traffic drop?"

	This server	Typical GSC MCP setup
Setup	`npx … login`, sign in, done (~30s)	Create a Google Cloud project, enable the API, create OAuth credentials, download JSON, point config at it
Runtime	Node — `npx`, nothing to install	Python + uv/venv
Can it modify your site data?	Impossible — read-only scope by construction	Write scopes with destructive ops "disabled by default"
Analyses	5 built-in (checkup, cannibalization, striking distance, traffic drop, indexing audit)	Bring your own prompts

This server

Typical GSC MCP setup

Setup

npx … login, sign in, done (~30s)

Create a Google Cloud project, enable the API, create OAuth credentials, download JSON, point config at it

Runtime

Node — npx, nothing to install

Python + uv/venv

Can it modify your site data?

Impossible — read-only scope by construction

Write scopes with destructive ops "disabled by default"

Analyses

5 built-in (checkup, cannibalization, striking distance, traffic drop, indexing audit)

Bring your own prompts

What it feels like

(Illustrative output — shape and numbers are what the tools return from your real data.)

Built-in SEO analysts

Five ready-made analyses ship as MCP prompts — slash-commands in clients that support them. Outcomes, not API calls:

Prompt	What you get
`seo_checkup`	Trend vs last month, biggest movers, and the top 3 moves worth making
`cannibalization_check`	Queries where two of your pages compete — which should win, and how to fix it
`striking_distance`	Queries sitting at position 5–15 — the fastest traffic you're not getting, with the fix per page
`traffic_drop`	When the drop started, which pages/queries lost, indexed-or-not, most likely cause
`indexing_audit`	Sitemap status + index inspection of your top pages, with plain-language fixes

Prompt

What you get

seo_checkup

Trend vs last month, biggest movers, and the top 3 moves worth making

cannibalization_check

Queries where two of your pages compete — which should win, and how to fix it

striking_distance

Queries sitting at position 5–15 — the fastest traffic you're not getting, with the fix per page

traffic_drop

When the drop started, which pages/queries lost, indexed-or-not, most likely cause

indexing_audit

Sitemap status + index inspection of your top pages, with plain-language fixes

io.github.sudomichael/search-console-mcp

Install in your client