Search Console MCP

Google + Bing + SEO analytics

Search data your AI assistant can inspect, compare and act on safely.

Search Console MCP connects Claude, Codex and other MCP clients to Google Search Console, Bing Webmaster Tools, GA4, CrUX, IndexNow and public-page audits.

View installation path

$ uvx gsc-mcp-tools

> Compare this site's Google and Bing visibility. Keep each provider's position semantics separate.

81 registered tools, structured JSON output

01 / Capabilities

Three sources. Explicit boundaries.

Start with the evidence your question needs.

Google data

Search Console performance and inspection, optional GA4 behavior data, and optional CrUX field data.

  • Search performance
  • URL inspection
  • GA4
  • CrUX

Bing data

Webmaster performance, crawl, feeds, backlinks and guarded submissions for sites visible to the configured Bing account.

  • Queries and pages
  • Crawl signals
  • Feeds
  • IndexNow

Public-page analysis

Fetched HTML, robots, sitemaps, structured data, content and internal-link signals without private provider credentials.

  • Metadata
  • Schema
  • Sitemaps
  • Internal links

Google and Bing position semantics remain separate.

02 / Workflow

From a question to a checked action.

  1. Connect

    Select only the verified properties and provider credentials you need.

  2. Measure

    Read queries, pages, crawl signals and public-page evidence.

  3. Compare

    Keep provider semantics and observed windows explicit.

  4. Explain

    Return structured facts, derived values and recommendations.

  5. Submit

    Run bounded write tools only after the target and action are confirmed.

03 / Get started

A small setup. A deliberate first check.

Choose an install path, connect your MCP client, then verify provider access.

  1. Evaluate once

    Run uvx gsc-mcp-tools without changing a project environment.

    uvx gsc-mcp-tools

  2. Install persistently

    Run uv tool install gsc-mcp-tools and point the MCP client at the installed executable.

    uv tool install gsc-mcp-tools

  3. Verify access

    Run gsc-cli list, then verify each configured provider separately.

    gsc-cli list

    Expected: the registered commands and their one-line descriptions.

Read the client-specific installation guide

04 / Evidence & safety

Know what the result proves.

An accepted submission proves neither crawl nor indexation.

Read the Bing API contract
Observed
API responses and fetched public-page data.
Derived
Calculations tied to an explicit observed window.
Requested
A provider accepted a submission. Crawl and indexation remain unproven.

05 / FAQ

Before you connect.

Does one Bing API key work for every site?

One Bing Webmaster API key can access the verified sites visible to that Bing account. Every tool call still names its target site. IndexNow uses a different key verified on each target host.

Do I need every Google API enabled?

No. Configure the provider families you use. Search Console credentials cover the core search workflows. GA4, CrUX and eligible Indexing API workflows require their own optional configuration.

Does a successful submission mean the page is indexed?

No. An accepted submission proves only that the provider accepted the request. Crawl and indexation must be measured separately in a later comparable check.

Can I use the server from Claude and Codex?

Yes. Search Console MCP runs over stdio and can be configured in Claude, Codex and other compatible MCP clients. The executable path and configuration format depend on the client.

Where do credentials live?

Credentials stay in the MCP server environment or the client configuration. The public website never receives them, and prompts should not contain secret values.

Ready to connect?

Install Search Console MCP.

Start with the package, then connect only the providers your workflow needs.

uvx gsc-mcp-tools

Read the installation guide