searchconsole-mcp

MCP server that automates Google Search Console for your projects: search analytics, sitemap management, site properties and URL inspection.

Tools

Related MCP server: Google Search Console MCP Server

One-time Google setup

1. In Google Cloud Console create a project.

2. Enable the Google Search Console API (APIs & Services > Library).

3. Create a Service account (IAM & Admin > Service Accounts) and download a JSON key.

4. For each Search Console property: Settings > Users and permissions > Add user, paste the service account email (...@...iam.gserviceaccount.com) and grant Owner (Owner is required for the URL Inspection API).

Configuration

Environment variables:

The server also loads .env from its working directory at startup.

Register in an MCP client

opencode (~/.config/opencode/opencode.json or project .opencode/opencode.json):

{
  "mcp": {
    "searchconsole": {
      "type": "local",
      "command": ["node", "/absolute/path/to/searchconsole-mcp/dist/index.js"],
      "environment": {
        "GSC_SERVICE_ACCOUNT_FILE": "/absolute/path/to/service-account.json",
        "GSC_DEFAULT_SITE": "sc-domain:example.com"
      }
    }
  }
}

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "searchconsole": {
      "command": "node",
      "args": ["/absolute/path/to/searchconsole-mcp/dist/index.js"],
      "env": {
        "GSC_SERVICE_ACCOUNT_FILE": "/absolute/path/to/service-account.json",
        "GSC_DEFAULT_SITE": "sc-domain:example.com"
      }
    }
  }
}

Development

npm install
npm run build     # tsc -> dist/
npm start         # run the server on stdio
npm run smoke     # boots the server and lists tools

Notes

• Analytics data lags ~2 days; pass dataState: "all" to include fresh partial data.

• The API caps analytics rows at 25,000 per request; use startRow to page.

• Adding a site via API leaves it unverified until ownership is confirmed; easiest path is adding the service account email as an Owner in the UI first.