Install Google Search Console MCP

Install the CLI, connect Google Search Console, configure your MCP client, and check the connection.

Before you start

  • Install Node.js 22 or newer. Bun can manage the global package, but the CLI runs on Node.js.
  • Use a Google account with access to at least one Search Console property.

Choose an install method

Each option installs the latest package globally and starts setup. Keep the global command directory on your PATH so you can run gsc later.

Install with curl and npm

curl -fsSL https://gscmcp.dev/install.sh | sh

The installer uses npm by default and starts Quick Connect. To use Bun instead:

Install with curl and Bun

curl -fsSL https://gscmcp.dev/install.sh | sh -s -- --manager bun

Connect Google and your MCP client

Setup guides you in three steps: sign in with Quick Connect (recommended, read-only), choose your Search Console properties, and choose where to install. Sign in in the browser and approve the configuration change when setup shows it. Setup runs quietly by default; add --verbose or --dry-run for the full detail.

Start setup again at any time

gsc setup

Need Google write operations? Use your own OAuth client or a service account. See Credentials for the setup steps and access limits.

Verify the connection

Check the CLI and Google connection

gsc doctor
gsc auth status --online

Then restart your MCP client and confirm that Google Search Console MCP tools appear. gsc doctor checks the local setup; gsc auth status --online checks Google access.

Choose specific properties

Setup limits the MCP server to the properties you select. Interactively, press Enter for the first property, pick numbers for an explicit allowlist, or choose [0] (or all) for all current and future properties, which warns and asks for a second confirmation. When you run setup again with --site, include every property you want to keep in the allowlist. Pass one exact property ID per flag. Use --site all alone or --all-sites only when you want to allow every current and future property on the account.

Configure the full property allowlist

gsc setup --site 'sc-domain:example.com' --site 'https://shop.example.com/'

Update or reinstall

Updates never break a working install. If a major change requires migration, the tool performs it automatically with a backup of your configuration; it never asks you for manual steps.

The assisted option compares your installed version against the npm registry and, when behind, reinstalls the package for your current runtime, verifies the new version, and reminds you to restart:

Update with the assisted updater

gsc update

To compare versions without installing anything, run gsc update --check. If your installed build is ahead of the registry, it reports that and changes nothing — it never downgrades. gsc doctor --online includes the same version check without failing.

Or install again manually with your preferred package manager to update:

Update with npm

npm install -g @sonnivasquez/gsc-mcp

After updating, check with gsc --version and restart your MCP client: the previous server keeps running until you restart it.

To stay on a specific version or roll back, pin the version:

Pin a specific version

npm install -g @sonnivasquez/gsc-mcp@1.2.0

Updating, pinning, or rolling back never touches your Google tokens, profiles, or client configurations. To remove the CLI entirely, see Uninstall.

En español

Las actualizaciones nunca rompen una instalación que funciona. Si un cambio grande requiere migración, la herramienta la hace sola con respaldo de tu configuración; nunca te pedirá pasos manuales.

También puedes actualizar con el asistente gsc update (gsc update --check solo compara versiones, sin instalar), o vuelve a instalar con tu gestor preferido: npm install -g @sonnivasquez/gsc-mcp o bun install -g @sonnivasquez/gsc-mcp. Después, comprueba con gsc --version y reinicia tu cliente MCP: el servidor anterior sigue corriendo hasta que lo reinicies.

Para quedarte en una versión concreta o volver atrás, indica la versión (npm install -g @sonnivasquez/gsc-mcp@1.2.0). Actualizar, fijar o revertir versión no toca tus tokens de Google, tus perfiles ni la configuración de tus clientes. Para quitar el CLI, consulta la guía de desinstalación.

Next