MCP server for Google Search Console that lets Claude list properties, inspect indexing status, query search analytics, compare performance periods, audit sitemaps, and manage Search Console resources with guarded destructive tools.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
5 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes.
Disclosure: MIT-licensed open-source server with README links to a separate paid hosted offering. This entry covers the source-backed self-run MCP package, not the hosted commercial product.
{
"mcpServers": {
"gscServer": {
"command": "uvx",
"args": ["mcp-search-console"],
"env": {
"GSC_OAUTH_CLIENT_SECRETS_FILE": "<absolute-path-to-client-secrets-json>",
"GSC_DATA_STATE": "all"
}
}
}
}Google Search Console MCP Server connects Claude to Google Search Console data. It exposes tools for capability discovery, property listing, search analytics, period comparison, page/query analysis, URL inspection, indexing audits, sitemap review, and guarded Search Console management operations.
Use it when an SEO, developer, or content team wants Claude to analyze Search Console properties through OAuth or a service account while keeping credentials in a local MCP configuration.
These sources were reviewed on 2026-06-06. Prefer the live repository, README, license, Python package metadata, server source, MCP config, dependency list, Dockerfile, tests, and plugin manifest for current setup and behavior.
GSC_DATA_STATE.Enable the Google Search Console API, create OAuth desktop credentials or a service account, and grant access to the target Search Console properties.
OAuth configuration:
{
"mcpServers": {
"gscServer": {
"command": "uvx",
"args": ["mcp-search-console"],
"env": {
"GSC_OAUTH_CLIENT_SECRETS_FILE": "<absolute-path-to-client-secrets-json>",
"GSC_DATA_STATE": "all"
}
}
}
}
Service account configuration:
{
"mcpServers": {
"gscServer": {
"command": "uvx",
"args": ["mcp-search-console"],
"env": {
"GSC_CREDENTIALS_PATH": "<absolute-path-to-service-account-json>",
"GSC_SKIP_OAUTH": "true",
"GSC_ALLOW_DESTRUCTIVE": "false"
}
}
}
}
After configuration, call get_capabilities and list_properties before using
analytics or URL inspection tools.
Search Console data can reveal site strategy, private URLs, search demand, page performance, crawl status, and technical SEO issues. Keep OAuth credentials, service account keys, cached tokens, property URLs, query exports, page-level reports, sitemap URLs, and URL inspection results out of public logs and screenshots.
Destructive operations are disabled by default. Leave GSC_ALLOW_DESTRUCTIVE
set to false for analysis-only workflows, and require explicit review before
adding or deleting Search Console properties or deleting sitemaps.
No AminForou/mcp-gsc, Google Search Console MCP, Search Console MCP server,
GSC MCP, or matching source URL entry was found in content/mcp or README.md.
Existing Google Workspace and Google Analytics entries do not cover Google
Search Console properties, indexing inspection, search analytics, and sitemap
management.
Show that Google Search Console MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/google-search-console-mcp-server)Google Search Console MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
| Field | MCP server for Google Search Console that lets Claude list properties, inspect indexing status, query search analytics, compare performance periods, audit sitemaps, and manage Search Console resources with guarded destructive tools. Open dossier | Local code indexing MCP server that lets AI assistants search repositories, build symbol indexes, inspect file summaries, monitor changes, and navigate multi-language codebases. Open dossier | Hosted streamable-HTTP MCP server registered as ai.com.mcp/skills-search that exposes Agent Skills Search API tools for discovering skills from the skills.sh registry using the open Agent Skills format. Open dossier | Real-time product search and price comparison across 11M+ products from Singapore, Southeast Asia, and US marketplaces via a remote streamable-HTTP MCP endpoint with API key auth. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| SubmitterDiffers | oktofeesh1 | oktofeesh1 | kiannidev | BuyWhere |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | ||
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | Amin Foroutan | johnhuang316 | Agent Skills | BuyWhere |
| Added | 2026-06-06 | 2026-06-06 | 2026-06-22 | 2026-06-26 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓The server requests the Google Search Console webmasters scope and can access every property available to the authenticated account. add_site, delete_site, and delete_sitemap are disabled by default and only run when GSC_ALLOW_DESTRUCTIVE is true. manage_sitemaps can submit or delete sitemaps depending on action and destructive settings. URL inspection and analytics tools can reveal indexing issues, search terms, landing pages, countries, devices, click-through rates, and ranking positions. Use least-privilege service accounts, avoid full-access credentials where read-only analysis is enough, and confirm exact site_url values with list_properties. | ✓Code Index MCP reads repository files, builds shallow and deep indexes, exposes file summaries, and can return source snippets through search and file resources. Point `--project-path` at one approved repository; avoid broad parent directories, home directories, generated dependency trees, or secret-heavy paths. Deep indexing and watcher refreshes can consume CPU, memory, disk IO, and temp storage on large codebases. The server can create and clear index/cache settings and temporary directories used for stored index data. Search results, file summaries, and symbol bodies can surface credentials, private code, customer data, internal URLs, or proprietary implementation details if they exist in the repository. | ✓Search results expose skill metadata and install instructions; installing a skill can give an agent executable scripts, shell commands, and third-party repository access. Treat discovered skills like unreviewed dependencies—inspect `SKILL.md`, scripts, and publisher sources before `npx skills add` or equivalent installers run. Self-hosted HAPI deployments inherit API rate limits and outbound network access to `https://skills.sh/api`; scope firewall and logging policies accordingly. Hosted remotes process search queries on vendor infrastructure; avoid sending confidential project names or customer identifiers in search strings when policy requires on-prem discovery. | ✓Read-only product catalog access by default; no write or delete operations exposed. API key should be stored in the MCP client config or environment, never committed. |
| Privacy notes | ✓OAuth client secrets, service account JSON, cached token files, Search Console properties, page URLs, query terms, sitemap URLs, countries, devices, clicks, impressions, CTR, and positions can be sensitive. The server stores OAuth tokens under a user config directory unless GSC_CONFIG_DIR is changed. Service account files and OAuth tokens must stay out of prompts, issue comments, logs, screenshots, and repository files. Redact property URLs, query data, page URLs, tokens, credential file paths, and inspection results before sharing MCP transcripts. | ✓Tool calls may expose file paths, filenames, source code snippets, imports, classes, methods, functions, symbols, search matches, complexity summaries, and project settings. Index data and temp directories can persist derived repository structure or symbol metadata outside the source tree. File watcher status, exclude patterns, and settings can reveal local project layout and development conventions. If an MCP client forwards tool results to a model provider, repository contents and search snippets may leave the local machine. Exclude secrets, generated artifacts, vendored dependencies, build output, and private data before indexing. | ✓Search queries, skill names, registry metadata, and tool responses enter MCP client context and may be logged by the hosted remote operator. skills.sh registry responses can include publisher URLs, install counts, and repository identifiers that reveal technology choices to shared clients. Installing skills from search results may download repository archives or scripts that process local files; review each skill's privacy posture before use. Self-hosted HAPI CLI mode keeps search traffic on your infrastructure but still contacts the public skills.sh API unless you mirror the backend. | ✓BuyWhere API key is sent as a Bearer token in the Authorization header on every request. Search queries are sent to BuyWhere's API to retrieve product data; no third-party analytics or telemetry is included in MCP responses. BuyWhere may log API request metadata (endpoint, timestamp, status) for abuse prevention and billing. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Give Claude local project indexes, advanced code search, file discovery, symbol summaries, watcher refreshes, and cached repository navigation.
Connect Claude to the skills.sh registry over streamable HTTP to search Agent Skills metadata, browse install counts, and discover installable skill packages.
Source-backed guides for putting this to work.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.