Google Search Console
Resumen
Descripción del creador (original en inglés)
Google Search Console: 37 tools, every API endpoint, hourly data, history beyond 16 months.
Los tres pilares de PopNx MCP
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
- Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
- Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
- UsoiMuy nuevo↓ 33/sem · ★ –
Qué puedes hacer con él
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
- Conexión: Se ejecuta en tu computadora
- Transporte: stdio
- Categoría: Búsqueda y memoria de IA
Instalación
Elige la app de IA que usas y copia la configuración.
Antes de instalar
- Revisiones básicas: 1 de 1 superadas
- Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
- El registro no indica ninguna clave que completar.
Necesitas
- PyPIuv de Python instalado (para el comando uvx)
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"gsc-full": {
"command": "uvx",
"args": [
"gsc-mcp-full"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add gsc-full -- uvx gsc-mcp-fullO copia la configuración tú
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"gsc-full": {
"command": "uvx",
"args": [
"gsc-mcp-full"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
O copia la configuración tú
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"gsc-full": {
"type": "stdio",
"command": "uvx",
"args": [
"gsc-mcp-full"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Qué puede hacer
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisiones básicasi
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 9 nov 2026
- ✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub mamrrez, dueña del repo
- … Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
- – No aplica
El endpoint responde
Este se ejecuta en tu computadora; no hay endpoint en internet
- – No aplica
Inicio de sesión con OAuth
Se ejecuta en tu computadora y usa ajustes locales en su lugar
- … Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con otros en Búsqueda y memoria de IAi
- Más estrellas que el 0% de los otros 5747 servidores de esta categoría
- Publicado en el registro más recientemente que el 51% de los otros 5747 servidores de esta categoría
- Revisiones básicas iguales o mejores que el 100% de los otros 5747 servidores de esta categoría
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Preguntas frecuentes
¿Es seguro Google Search Console?
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
¿Qué claves o códigos necesita?
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
¿Se ejecuta en mi computadora o en la nube?
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
¿Sigue en mantenimiento?
El repo de GitHub cambió por última vez –, y la última versión (0.2.2) llegó al registro hace 37 días.
¿Qué apps pueden usarlo?
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.
¿Qué puedo usar en su lugar?
En la misma categoría: Context7, Codebase Memory, Exa
Alternativas
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
README del creador
Abrir el README
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Google Search Console MCP Server — gsc-mcp-full
The complete MCP server for Google Search Console. Ask Claude, Cursor, Windsurf, VS Code, Codex or any other MCP client about your search performance, indexing and sitemaps in plain language — and get analysis back, not a spreadsheet.
37 tools · every Search Console API endpoint · the 24-hour view and hourly data · history beyond 16 months · correct numbers in every language.
[Quick start](#quick-start) · [Tools](#tools) · [Languages](#languages) · [FAQ](#faq) · [Full docs](https://mamrrez.github.io/gsc-mcp-full/) · [Project page](https://hasanpour.com/tools/gsc-mcp-full/)
What you get
| ✅ Complete | All 10 live methods of the Search Console API, all 6 search types (web, image, video, news, Discover, Google News), all 7 dimensions including hourly, with contains, exact, exclude and regex filters. Nothing in the API is left out. |
| ⚡ Fast | Starts in under a second. Inspects up to 10 URLs in parallel, 50 per request, inside a time budget so a big batch never times out your client. Retries rate limits and server errors on its own. Groups 25,000 queries in about half a second. Questions about synced history never touch the network. |
| 🔄 Current | Built on MCP SDK 2.x. API coverage checked against Google's own API definition (October 2026). Mirrors the Performance report's newest options: the 24-hour view with preliminary data, and hourly, daily, weekly or monthly granularity. Tested on Linux, macOS and Windows with Python 3.10–3.13 on every change. |
| 🧠 Answers, not exports | Cannibalization, striking-distance keywords, under-performing titles, decaying pages, brand vs non-brand — worked out for you and returned as short tables your AI can reason about. |
| 🌍 Right in every language | Search Console splits one keyword into several rows when it is typed several ways. This server merges them — Persian, Arabic, Chinese, Japanese, Korean, Turkish, Vietnamese, Russian and more — so the totals are the real ones. |
| 🗄️ No 16-month limit | Sync your data into a local file once; compare this quarter with the same quarter two years ago, long after Google has deleted it. |
| 🕒 Your timezone | Search Console days are Pacific-Time days. Hourly data is re-cut into *your* local days. |
| 🎯 Numbers you can trust | Header totals are the real period totals, not a sum of the rows shown. Page URLs are never shortened, so they can be passed straight to the next tool. A failure is reported as an error with its reason, never as an empty result. Covered by 117 automated tests on Linux, macOS and Windows, and checked end to end against real properties. |
| 🔒 Safe by default | Read-only access unless you opt in. Runs on your machine; your sign-in never leaves it. No hosted service, no account, no telemetry. |
| 💸 Free and light | MIT licensed. Four dependencies. One command to run. |
Works with: Claude Desktop · Claude Code · Cursor · Windsurf · VS Code (Copilot agent mode) · OpenAI Codex CLI · any MCP client over stdio or HTTP.
Tools
37 tools in 8 groups. You don't call them yourself — ask in plain language and your AI picks the right one.
🌍 merges spelling variants · 🗄️ can run on local history (any date range) · ✍️ needs write access (GSC_ALLOW_WRITE=1)
📊 Search performance
| Tool | What it gives you | Ask it like this |
|---|---|---|
performance_overview | One-screen summary: totals, a daily, weekly or monthly trend, top queries and pages, devices, countries, data freshness | *"How did example.com do in the last 6 months, month by month?"* |
query_search_analytics 🌍 | Any report you can build in Search Console: every dimension, search type and filter, with a query filter that also matches a term's other spellings | *"Top mobile queries from Germany containing 'klima' last month"* |
compare_periods 🌍 | Two periods side by side with the biggest movers first — previous period, same dates last year, 52 weeks ago, or custom dates | *"Compare this month with the same month last year"* |
queries_for_page 🌍 | Every query that brings traffic to one page | *"What do people search to land on /pricing/?"* |
pages_for_query 🌍 | Which pages rank for one keyword and how impressions split between them | *"Which of my pages rank for 'air conditioner installation'?"* |
hourly_performance | Search Console's 24-hour view, and hour-by-hour data for the last 10 days in your own timezone | *"Show the last 24 hours"* · *"Show last week as Tehran days"* |
data_freshness | Which recent days and hours are final and which are still preliminary | *"Is yesterday's data complete yet?"* |
🎯 SEO opportunities
| Tool | What it gives you | Ask it like this |
|---|---|---|
striking_distance 🌍🗄️ | Keywords ranking 8–20 with real demand, and the clicks you'd gain on page one | *"What are my quickest ranking wins?"* |
find_cannibalization 🌍🗄️ | Keywords where two or more of your pages compete as separate results (sitelinks and #section links are not counted as competitors), ranked by wasted impressions | *"Where are my pages competing with each other?"* |
low_ctr_opportunities 🌍🗄️ | Page-one results whose click-through rate is far below what their position should earn | *"Which titles should I rewrite first?"* |
content_movers 🌍🗄️ | Pages or queries that decayed, rose, disappeared or appeared since the last period | *"Which pages lost traffic this month?"* |
brand_split 🌍🗄️ | Brand vs non-brand traffic, with your brand matched in every script it's written in | *"How much of my traffic is non-brand?"* |
🌍 Multilingual intelligence
| Tool | What it gives you | Ask it like this |
|---|---|---|
query_variants 🗄️ | Keywords that Search Console splits across spellings, with their real combined totals | *"Which keywords are split across spellings?"* |
language_breakdown 🗄️ | Share of clicks and impressions by the language and script of the query | *"How much of my traffic is Arabic vs English?"* |
keyboard_mistypes 🗄️ | Queries typed with the keyboard on the wrong layout (ovdn lhadk = «خرید ماشین») | *"Find searches typed on the wrong keyboard"* |
top_terms 🗄️ | Most demanded words across all queries — including Chinese, Japanese and Thai, which have no spaces | *"What words appear most in my Japanese queries?"* |
build_query_regex | A regex filter that works for non-English text, for the API or the Search Console UI | *"Give me a regex for خرید خودرو that matches every spelling"* |
🗄️ Unlimited history
| Tool | What it gives you | Ask it like this |
|---|---|---|
sync_history | Copies your data into a local database, day by day, past Google's 16 months and row caps | *"Sync the last 16 months of example.com"* |
history_status | What's stored: date range, days and rows per property | *"What history do I have saved?"* |
history_query 🌍 | Any report over any stored date range | *"Top queries for all of 2025"* |
history_trend 🌍 | Clicks, impressions, CTR and position per day, week or month | *"Monthly clicks for 'heat pump' over two years"* |
history_compare 🌍 | Two stored periods against each other, however far apart | *"Q3 this year vs Q3 two years ago"* |
history_sql | Your own read-only SQL against the stored data | *"Run this SQL on my history: …"* |
🔍 Indexing and URL inspection
| Tool | What it gives you | Ask it like this |
|---|---|---|
inspect_url | Full inspection of one page: index status, last crawl, canonical, robots, sitemaps, rich results | *"Is /new-article/ indexed? What canonical did Google pick?"* |
inspect_urls | Up to 50 pages inspected in parallel, as one table with separate index and rich-result verdicts | *"Inspect these 30 URLs"* |
indexing_summary | Problems only: which pages are not indexed or fail structured data, and why | *"Which of these pages have indexing issues?"* |
inspection_quota | How much of Google's daily inspection allowance is used | *"How many inspections do I have left today?"* |
🗺️ Sitemaps
| Tool | What it gives you | Ask it like this |
|---|---|---|
list_sitemaps | Every submitted sitemap with URL counts, errors and warnings | *"List my sitemaps and their errors"* |
get_sitemap | Details of one sitemap | *"When did Google last read sitemap.xml?"* |
submit_sitemap ✍️ | Submit or resubmit a sitemap | *"Submit example.com/sitemap.xml"* |
delete_sitemap ✍️ | Remove a sitemap from Search Console | *"Remove the old sitemap"* |
🏠 Properties
| Tool | What it gives you | Ask it like this |
|---|---|---|
list_properties | Every property your account can see, with your permission level | *"List my Search Console properties"* |
get_property | Details of one property — accepts example.com as well as the exact property URL | *"Do I own example.com in Search Console?"* |
add_property ✍️ | Add a site to your account | *"Add newsite.com to Search Console"* |
remove_property ✍️ | Remove a site from your account | *"Remove the old staging property"* |
🛠️ Utilities
| Tool | What it gives you | Ask it like this |
|---|---|---|
get_capabilities | Sign-in status, access level, stored history and the tool list | *"Is Search Console connected?"* |
reauthenticate | Sign in again to switch Google accounts | *"Switch to my other Google account"* |
Every parameter of every tool: Tool reference.
Quick start
Three steps, about ten minutes, no cost. You need a Google account with access to Search Console.
1. Create your Google credentials
Google requires every app that reads Search Console to identify itself, so you create a free "OAuth client" once.
- Open Google Cloud Console and create a project (any name).
- Enable the Google Search Console API for it.
- Open Credentials → Create credentials → OAuth client ID. If asked, fill in the consent screen first: type External, any app name, your own email.
- Choose Desktop app, create it, and Download JSON. Keep the file somewhere permanent, for example
~/gsc/client_secret.json. - On the consent screen page, click Publish app. Without this, Google signs you out every 7 days. No review is needed for personal use.
Using a service account instead (servers, scheduled jobs, teams)
- In the same project: IAM & Admin → Service accounts → Create service account.
- Open it → Keys → Add key → Create new key → JSON. Use this file instead of the OAuth one.
- In Search Console → Settings → Users and permissions → Add user, add the service account's email address to each property.
No browser sign-in is needed with a service account; skip the auth command in ste
Solo se muestra el principio; lee el resto en el repo