mcp-search-console

mcp-search-console is an MCP server for Claude Code from AminForou/mcp-gsc. Its token cost is not measured, scanned A, original, MIT.

A local connection to Google Search Console, a Google service that reports how a website appears in Google Search and how people reach it.

In plain words
What is it for?
It is for accessing website search performance data through the Model Context Protocol, a standard way for AI tools to connect to external services.
Why use it?
It gives an AI agent a way to work with Search Console data without manually copying reports, once the required credentials and settings are provided.

MCP server for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: listed in a Claude config.

Part of the mcp-search-console plugin — 4 skills, 1 MCP server shipped together

Good fit It is for accessing website search performance data through the Model Context Protocol, a standard way for AI tools to connect to external services.

Compare 6 mcp servers from other repositories ↓
Install with agentmods
npx agentmods add mcp/aminforou/mcp-gsc/mcp-search-console
About the project

mcp-gsc is an MCP server that connects Google Search Console, a service for inspecting website search performance, to AI assistants so users can ask questions about SEO data in natural language. SEO professionals use it to analyze their Google Search Console data, and the catalogue entries provide related skills, a plugin, an instruction, and MCP configuration.

AminForou/mcp-gsc · 1,517 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/AminForou/mcp-gsc

Made for: Claude Code.

Or install mcp-search-console, the plugin that ships this one along with the rest of its 4 skills, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mcp-search-console

README.md
[![agentmods](https://agentmods.dev/badge/mcp/aminforou/mcp-gsc/mcp-search-console/github.svg)](https://agentmods.dev/mcp/aminforou/mcp-gsc/mcp-search-console)
Your own site
<a href="https://agentmods.dev/mcp/aminforou/mcp-gsc/mcp-search-console"><img src="https://agentmods.dev/badge/mcp/aminforou/mcp-gsc/mcp-search-console/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mcp-search-console

Your own site · 80×15
<a href="https://agentmods.dev/mcp/aminforou/mcp-gsc/mcp-search-console"><img src="https://agentmods.dev/badge/mcp/aminforou/mcp-gsc/mcp-search-console.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

mcp-search-console scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

.mcp.json · 13 lines

What it actually says

{
  "mcp-search-console": {
    "command": "uvx",
    "args": [
      "mcp-search-console"
    ],
    "env": {
      "GSC_CREDENTIALS_PATH": "",
      "GSC_OAUTH_CLIENT_SECRETS_FILE": "",
      "GSC_DATA_STATE": "all"
    }
  }
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 13d ago First seen · 13 lines scan A 2d7d48835d82

Subscribe to this mod's changes

mcp-search-console is an MCP server published in the GitHub repository AminForou/mcp-gsc (1,517 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other mcp servers, from other repositories

search-console-mcp

Google Search Console + Bing + GA4 + AdSense — unified SEO intelligence for AI agents. Runs locally from the search-console-mcp npm package. Needs 3 environment variables to run.

saurabhsharma2u/search-console-mcp · not measured

screaming-frog-mcp

Headless MCP server for Screaming Frog SEO Spider — run crawls, export and analyze crawl data via the CLI, no GUI session required. Built for scheduled audits, CI, and AI agents. Runs locally from the screaming-frog-mcp Python package. Needs 1 environment variable to run.

bzsasson/screaming-frog-mcp · not measured

seo-audit-console

Technical SEO in Claude: GSC + crawl + DataForSEO - audit, market sizing, content recon. Runs locally from the @houtini/seo-audit-console npm package. Needs 9 environment variables to run.

houtini-ai/seo-audit · not measured

gsc

MCP server for Google Search Console & Indexing API — search analytics, sitemaps, URL inspection. Runs locally from the @mikusnuz/gsc-mcp npm package. Needs 4 environment variables to run.

mikusnuz/gsc-mcp · not measured

mcp

Track keyword rankings, research SEO opportunities, and manage bisibility projects with AI agents. Runs locally from the @bisibility/mcp npm package. Needs 5 environment variables to run.

CorgiCorner/bisibility-mcp · not measured

google-search-console-mcp

MCP server for Google Search Console: properties, sitemaps, search analytics and URL inspection. Runs locally from the @ni-c/google-search-console-mcp npm package. Needs 11 environment variables to run.

ni-c/google-search-console-mcp · not measured