---
title: "Google Search Console MCP Server: No Google Cloud Setup"
description: Connect Google Search Console to Claude, Cursor, or any MCP client — no Google Cloud project needed. Query clicks, impressions, CTR, position, and indexing.
---

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. OpenSEO handles the Google connection for you. You sign up, connect your property, and start asking.

## Setup: no Google Cloud project

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

The hosted MCP server URL is:

```txt
https://app.openseo.so/mcp
```

### Claude Code

```bash
claude mcp add --transport http --scope user openseo https://app.openseo.so/mcp
```

### Claude Desktop

1. Open Settings → Connectors.
2. Click **Add custom connector**.
3. Paste `https://app.openseo.so/mcp`.

### Cursor

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

```json
{
  "mcpServers": {
    "openseo": {
      "url": "https://app.openseo.so/mcp"
    }
  }
}
```

### Codex CLI

```bash
codex mcp add openseo --url https://app.openseo.so/mcp
```

Any other MCP client works the same way: add `https://app.openseo.so/mcp` as a remote server and sign in. Full setup and troubleshooting live in the [MCP docs](/docs/mcp).

### 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 OpenSEO never burns usage. They're included with the OpenSEO 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. If you'd rather not pay at all, OpenSEO is open source and free to self-host — see the FAQ below.

## OpenSEO vs. the alternatives

<ComparisonTable />

## FAQ

### What does it cost?

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

### Is it open source?

Yes. OpenSEO is open source, so you can self-host the whole thing for free, including the Search Console MCP. The one-click connection here uses OpenSEO's hosted Google app. If you self-host, you bring your own Google OAuth client, the same Cloud-console step the hosted version saves you. Hosted means no setup; self-hosted means full control.

### Is it read-only?

Yes. OpenSEO 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 OpenSEO 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.