gsc-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
gsc-mcp
MCP server for Google Search Console and IndexNow — manage search indexing programmatically instead of driving a browser.
Image:
ghcr.io/robertdwhite/gsc-mcp, built by CI in this repo.Transport: MCP streamable HTTP at
/mcp, bearer-gated byMCP_TOKEN./healthzis open.
Tools
Tool | Does |
| Credential check; reports the service-account email |
| Search Console properties |
| Get FILE/META ownership token |
| Complete verification — the service account becomes an owner |
| Grant a human Google account access (UI + API) |
| Sitemap management with indexed-count stats |
| Clicks/impressions/CTR/position by query, page, country, device, date |
| Per-URL index status, last crawl, canonical |
| Push URLs to Bing/DuckDuckGo/Yandex — works with no Google setup |
Related MCP server: Google Search Console MCP Server
One-time Google setup (human, ~5 minutes)
In Google Cloud Console, create/reuse a project and enable Google Search Console API and Site Verification API.
Create a service account (no roles needed) and a JSON key.
Put the key JSON in the
GSC_SA_JSONenv var (in-cluster: thegsc-mcp-envsecret).
Then, via tools: add_site → verification_token (place the token on the
site) → verify_site → the service account is a verified owner and every
other tool works. add_owner grants your personal account the same property.
Config (env)
Var | Meaning |
| Bearer token required on |
| Service-account key JSON (the raw JSON string). |
| Optional defaults for |
| Listen port (default 8080). |
Deploy
Manifests live in
whitehouse-rke2 under
apps/ai/gsc-mcp (endpoint https://gsc-mcp.internal.white.fm/mcp, tailnet
only).
Connecting clients
The server speaks MCP streamable HTTP at /mcp and expects
Authorization: Bearer <MCP_TOKEN>. Anything below works from any machine
that can reach the endpoint (for the house deploy: tailnet/LAN only).
Claude Code
claude mcp add --transport http gsc https://gsc-mcp.internal.white.fm/mcp \
--header "Authorization: Bearer <MCP_TOKEN>"Or directly in ~/.claude.json:
"mcpServers": {
"gsc": {
"type": "http",
"url": "https://gsc-mcp.internal.white.fm/mcp",
"headers": { "Authorization": "Bearer <MCP_TOKEN>" }
}
}Claude Desktop
The custom-connector UI expects OAuth; this server uses a static bearer, so
bridge it with mcp-remote in
claude_desktop_config.json (needs Node):
"mcpServers": {
"gsc": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://gsc-mcp.internal.white.fm/mcp",
"--transport", "http-only",
"--header", "Authorization: Bearer <MCP_TOKEN>"]
}
}Codex (ChatGPT app / Codex CLI)
Codex configures MCP servers as stdio commands — use the same bridge in
~/.codex/config.toml:
[mcp_servers.gsc]
command = "npx"
args = ["-y", "mcp-remote", "https://gsc-mcp.internal.white.fm/mcp",
"--transport", "http-only",
"--header", "Authorization: Bearer <MCP_TOKEN>"]
startup_timeout_sec = 60Restart the app after editing.
Hermes (or any YAML-config MCP client)
mcp_servers:
gsc:
url: https://gsc-mcp.internal.white.fm/mcp
headers:
Authorization: Bearer ${GSC_MCP_TOKEN}Sanity check without a client
curl -s https://gsc-mcp.internal.white.fm/healthz # -> ok (no auth)
curl -s -o /dev/null -w '%{http_code}\n' -X POST \
https://gsc-mcp.internal.white.fm/mcp # -> 401 (auth gate works)Note: claude.ai web connectors cannot reach a tailnet-only endpoint; expose
an external route first if you need it there.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Google Search Console, Bing, Yandex and IndexNow for AI assistants, with live SEO analyses.
Google Search Console for AI assistants: traffic, rankings, indexing and page checks. Read-only.
Google Search Console, GA4 and Bing Webmaster data for SEO and AI-search work. 20 read-only tools.
Google Search Console in your AI: overview, opportunities, index gaps, page checks, long history.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google Search Console via MCP, offering search analytics, performance summaries, URL inspection, sitemap management, and property listing for SEO workflows.262 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables interacting with Google Search Console via natural language, supporting search analytics, URL inspection, sitemap management, and site listing.25-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google SearchConsole tools and services through a unified API.2MIT
- AlicenseAqualityDmaintenanceEnables automation of Google Search Console tasks, including retrieving search analytics, managing sitemaps and site properties, and inspecting URLs for index status and crawl information.9MIT