Skip to content
MCP server

Google_search_console

MCP server giving AI clients read access to Google Search Console search and index data

Install
Pricing
Freemium
Platforms
API, CLI, self-hosted
Runs
Locally or Remotely
Version
0.2.1
Listing updated
today

Similar MCP servers

About Google_search_console

Google_search_console is a freemium MCP server for web search and scraping. It can run locally on your machine or as a hosted remote server.

The README describes this as a Pipeworx pack that wraps the Search Console API, so an AI client can list the properties in a connected account, pull search-performance figures, check submitted sitemaps and inspect the index status of individual URLs. Each tool is designed to be called in a sequence: listing sites first returns the exact property identifier the other tools expect.

The server is hosted on the Pipeworx gateway and is reached over streamable HTTP or through a local npm stdio bridge. The README notes that the bridge needs network access and has no offline mode. Calls made without a Pipeworx key are anonymous and capped daily, and a free account raises that cap.

It suits SEO analysts and developers who want to ask an assistant questions about organic clicks, impressions, CTR or why a page is not indexed, without writing their own API client. The README says the endpoint also lists shared gateway meta-tools alongside the four pack tools.

Install

Run in a terminal

claude mcp add --transport http google_search_console https://gateway.pipeworx.io/google_search_console/mcp

Add to Settings → Connectors → Add custom connector

https://gateway.pipeworx.io/google_search_console/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "google_search_console": {
      "url": "https://gateway.pipeworx.io/google_search_console/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "google_search_console": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/google_search_console/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "google_search_console": {
      "serverUrl": "https://gateway.pipeworx.io/google_search_console/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "google_search_console": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/google_search_console/mcp"
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • PIPEWORX_API_KEYOptional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

Tools this server provides (4)

Taken from the project documentation; the running server may differ.

gsc_list_sites
List the sites (properties) in the connected Search Console account, with the permission level for each.
gsc_search_analytics
Query Search Console search-performance data: clicks, impressions, CTR, and average position, grouped by dimensions.
gsc_list_sitemaps
List the sitemaps submitted for a property, including last download time, warnings/errors, and indexed counts.
gsc_inspect_url
Inspect a specific URL's index status in Google: coverage state, last crawl, canonical, mobile usability, and rich-results status.

What it does

Site property listing
Lists the Search Console properties in the connected account with the permission level for each.
Search performance queries
Returns clicks, impressions, CTR and average position grouped by chosen dimensions.
Sitemap health audit
Shows submitted sitemaps with last download time, warnings, errors and indexed counts.
URL index inspection
Reports coverage state, last crawl, canonical, mobile usability and rich-results status for a URL.
Multiple client connections
Connects through a hosted streamable HTTP endpoint or a local npx stdio bridge.

Good for

  • Find top organic queries and pages for a given month
  • Track CTR and ranking trends for a property
  • Audit sitemap submissions for warnings and errors
  • Diagnose why a specific URL is not indexed

Pricing

Freemium, from $49 a month

Anonymous use capped at 50 calls a day; free account 200 calls a day; paid credits and subscriptions beyond that.

Prices change. Check pipeworx.io before you buy.

Google_search_console FAQ

Do I need a key to use it?

The README says calls without a Pipeworx API key are anonymous and capped daily. A free account raises the daily cap to 200 calls.

Which tools does the pack provide?

Four tools: gsc_list_sites, gsc_search_analytics, gsc_list_sitemaps and gsc_inspect_url.

Does the npm package work offline?

No. The README says it is a stdio bridge to the Pipeworx gateway and needs network access.

Is Google_search_console free?

Google_search_console has a free plan, with paid plans for more usage or features. Paid plans start at $49 a month.

How do I add Google_search_console to Claude Code?

Run this command in your terminal: claude mcp add --transport http google_search_console https://gateway.pipeworx.io/google_search_console/mcp

What are the best alternatives to Google_search_console?

The closest alternatives to Google_search_console are Google Search Console MCP, Google Search Console MCP, Google Search Console, Search Console MCP and GSCPAP - Google Search Console, GA4, PageSpeed Insights & live SERPs MCP.

Where this comes from

  • Description: written from the project's README, the project's website and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers