topmcps
Browse MCPs
Google Search Console

Google Search Console

Query Search Console clicks, impressions, and queries from an AI agent.

Score 63(?)Community (ahonn)MIT224Verified Top MCPs for Marketing & SEO →
InstallView on GitHub

Quick answer

What it does

Connects to Google Search Console and exposes search_analytics — query-level clicks, impressions, CTR, and position data with filtering and regex support — so an agent can analyse organic search performance without opening the GSC UI.

Best for

  • Organic query performance analysis
  • CTR and position auditing
  • Page-two "quick win" discovery
  • Click and impression trend analysis

Not for

  • URL inspection / index coverage workflows
  • Non-Google search engines

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
  "mcpServers": {
    "google-search-console": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-gsc"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
      }
    }
  }
}

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    # export GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account-key.json
claude mcp add google-search-console -- npx -y mcp-server-gsc

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
  "mcpServers": {
    "google-search-console": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-gsc"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
      }
    }
  }
}

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
  "servers": {
    "google-search-console": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-gsc"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
      }
    }
  }
}

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
  "mcpServers": {
    "google-search-console": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-gsc"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
      }
    }
  }
}

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
  "mcpServers": {
    "google-search-console": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-gsc"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
      }
    }
  }
}

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "mcp-server-gsc"
          ],
          "env": {
            "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
          }
        }
      }
    ]
  }
}

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
[mcp_servers.google-search-console]
command = "npx"
args = [
  "-y",
  "mcp-server-gsc",
]
env = { GOOGLE_APPLICATION_CREDENTIALS = "${GOOGLE_APPLICATION_CREDENTIALS}" }

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
  "context_servers": {
    "google-search-console": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-server-gsc"
        ]
      },
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
      }
    }
  }
}

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Apps directory

    Google Search Console doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

  2. 2

    Set required secrets

    Set GOOGLE_APPLICATION_CREDENTIALS in your shell environment before launching your MCP client.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

ToolDescriptionArgsSide effects
search_analyticsReturn clicks, impressions, CTR, and position for a property, with dimension filters, regex, and quick-wins detection.siteUrl: string, startDate: string, endDate: stringRead

Security & scope

Access scope
Read-only
Sandbox
Authenticates with a Google service-account key that has read access to a verified Search Console property. The single exposed tool is a Search Analytics read — it cannot submit sitemaps, request indexing, or change property settings. Scope the service account to read-only access on only the properties the agent needs.
Gotchas
  • The service-account JSON sits in a client config file in plaintext — rotate it if the config is shared.
  • Add the service-account email to the GSC property with restricted (read) access, not full — full access is unnecessary for Search Analytics.
  • Search Analytics data lags ~2 days; treat the most recent days as provisional in any agent-generated report.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. marketing & seo work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-marketing-seo
Compare Google Search Console against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Google Search Console MCP vs [Google Analytics MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/google-search-console
- top-mcps.com listing for Google Analytics
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Google Search Console MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/google-search-console (fetch https://top-mcps.com/mcp/google-search-console.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (GOOGLE_APPLICATION_CREDENTIALS) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Marketing & SEO MCPs

Other tools in the same category worth evaluating.

DataForSEO
Official

Live SERP, keyword, backlink, and on-page SEO data for an AI agent.

seo, serp, keywords, backlinks
10 minMedium
Google Analytics
Official

Query GA4 reports, funnels, and realtime data from an AI agent.

analytics, ga4, google-analytics, reporting
15 minMedium
Ahrefs
Official

Backlinks, keyword research, and rank tracking from the official Ahrefs remote MCP.

seo, backlinks, keywords, rank-tracking
5 minLow

Compared with Google Search Console

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Google Search ConsolevsDataForSEOGoogle Search ConsolevsGoogle AnalyticsGoogle Search ConsolevsAhrefs

Exploring Top MCPs for Marketing & SEO? See all Marketing & SEO MCPs →