Google Search Console MCP Server: No Google Cloud Setup

Most Google Search Console (GSC) MCP servers are open source, but they take a lot of effort to set up. You need to create a Google Cloud project, enable an API, build an OAuth client, download a credentials.json, then keep a local server running. SEOProve handles the Google connection for you. You sign up, connect your property, and start asking.

Setup: no Google Cloud project

1. Sign up for SEOProve ($10/month).
2. Go through the onboarding. When prompted, click Connect Search Console and pick your property.
3. Add the SEOProve MCP endpoint to your client (steps below) and approve the SEOProve login when prompted.

The hosted MCP server URL is:

https://app.seoprove.com/mcp

Claude Code

claude mcp add --transport http --scope user seoprove https://app.seoprove.com/mcp

Claude Desktop

1. Open Customize → Connectors.
2. Click Add (or +), then choose Add custom connector.
3. Paste https://app.seoprove.com/mcp.

Cursor

1. Open Cursor Settings → Tools & Integrations → MCP Tools.
2. Click New MCP Server (this opens mcp.json) and add:

{
  "mcpServers": {
    "seoprove": {
      "url": "https://app.seoprove.com/mcp"
    }
  }
}

Codex CLI

codex mcp add seoprove --url https://app.seoprove.com/mcp

For ChatGPT web or desktop, follow the ChatGPT setup steps and plan requirements. For other remote MCP clients, add https://app.seoprove.com/mcp and sign in. Full setup and troubleshooting live in the MCP docs.

The DIY way (every other GSC MCP)

1. Create a Google Cloud project
2. Enable the Search Console API
3. Configure the OAuth consent screen
4. Create OAuth client credentials
5. Download credentials.json
6. Install and run a local MCP server

Things to actually ask it

• "Which queries am I ranking on page two for that I'm close to pushing onto page one?"
• "Show me pages where impressions went up but clicks stayed flat — probably a title or meta problem."
• "Are any of my blog posts competing with each other for the same query?"
• "Is /pricing indexed? If not, what's blocking it?"
• "Which queries lost the most clicks over the last 28 days?"

What your agent can read

Two read-only tools over the property you connect. Both pull Google's own numbers, and neither uses credits.

Search performance. Clicks, impressions, CTR, and average position for your site, sliced by query, page, country, device, and date. Pull up to 16 months of history in a single question.

URL inspection. Whether a page is indexed and, if not, why: coverage status, last crawl, the canonical Google chose versus the one you declared, plus mobile and rich-result checks. Up to 10 URLs at a time.

The agent can read and inspect. It cannot change anything in your account.

What it costs

The Search Console tools use zero credits — Google doesn't charge you to read your own data, so reading it through SEOProve never burns usage. They're included with the SEOProve plan ($10/month, which includes monthly usage credits for the research tools), alongside the credit-based tools (keyword research, rank tracking, backlinks) that run through the same MCP endpoint. There is a free trial with $0.50 of credits, and the free SEO tools work without a plan.

SEOProve vs. the alternatives

FAQ

What does it cost?

The Search Console MCP tools are included with the $10/month SEOProve plan (which comes with a 30-day money-back guarantee) and use zero credits. SEOProve's other tools (keyword research, rank tracking, backlinks) use the usage credits included with the plan, through the same endpoint.

Do I need my own Google Cloud project?

No. The one-click connection uses SEOProve's Google app, so you sign in and pick a property. Setting up a comparable server yourself means creating a Cloud project, enabling the API, and managing an OAuth client; that setup is the part SEOProve removes.

Is it read-only?

Yes. SEOProve requests read-only access (webmasters.readonly). Your agent can read performance data and inspect URLs, but it can't change your account.

Which AI clients work?

Any MCP client, including Claude Code, Claude Desktop, Cursor, Codex, and OpenClaw. Add the SEOProve MCP endpoint and sign in.

How fresh is the data?

It's Google's own data, so the most recent few days can be incomplete. History runs back 16 months, the same as the Search Console interface.