Skip to content

Search Console MCP

Google Search Console MCP for Claude, Cursor, and AI clients

Connect Google Search Console to Claude, Cursor, or another MCP client without setting up a Google Cloud project. Query clicks, CTR, position, and indexing.

No subscription. Search Console tools do not reduce your balance.

Some self-managed Google Search Console (GSC) MCP servers take substantial setup. 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. FlexQueries handles the Google connection for you. You sign up, connect your property, and start asking.

Setup: no Google Cloud project

  1. Sign up for FlexQueries. There is no subscription.
  2. Go through the onboarding. When prompted, click Connect Search Console and pick your property.
  3. Add the FlexQueries MCP endpoint to your client (steps below) and approve the FlexQueries login when prompted.

The hosted MCP server URL is:

https://app.flexqueries.com/mcp

Claude Code

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

Claude Desktop

  1. Open Customize → Connectors.
  2. Click +, then Add custom connector.
  3. Paste https://app.flexqueries.com/mcp.

Cursor

Add this server to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for all projects. Merge the FlexQueries entry into mcpServers if you already have other servers configured:

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

Approve the FlexQueries login when prompted. See the Cursor MCP guide for more setup options.

Codex CLI

codex mcp add flexqueries --url https://app.flexqueries.com/mcp
codex mcp login flexqueries

Other clients with remote HTTP MCP and OAuth support can connect: add https://app.flexqueries.com/mcp as a remote server and sign in. Full setup and troubleshooting live in the MCP docs.

A typical self-managed setup

  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. Request available history up to 16 months back. Large results may require pagination; anonymized queries remain hidden.

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.

These two Search Console tools are read-only. Other FlexQueries MCP tools can save keywords, start audits, and run paid research in your authorized project.

What it costs

Your AI client or model provider may charge separately. Connecting MCP does not include a subscription to that client.

The Search Console tools do not reduce your balance because Google does not charge you to read your own data. Other tools such as keyword research, rank tracking, and backlinks are pay as you go through the same MCP endpoint.

FlexQueries vs. the alternatives

Typical setup patterns; individual servers and vendors differ. AI client fees are separate. FlexQueries research beyond Search Console is metered.

Scroll to compare all columns

Search Console MCP setup, cost, and features
CapabilityFlexQueriesDIY MCP serversData-pipeline tools
Setup
Simple, guided onboarding
Server installation and Google credentials; varies by project
Account + connector setup
Google Cloud project
Not needed
Often required
Usually not needed
Search Console usage
No FlexQueries subscription or GSC usage charge
License, hosting and quota depend on the server
Paid or limited free tier
Search Console permissions
webmasters.readonly
Depends on the scopes you grant
Varies
Built for SEO
Also does keyword, rank, and backlink research
Other tools depend on the server
Reporting and analytics focus

FAQ

What does it cost?

The Search Console MCP tools have no usage charge. There is no FlexQueries subscription. Other tools, including keyword research, rank tracking, and backlinks, draw from your non-expiring account balance through the same endpoint.

Do I need my own Google Cloud project?

No. FlexQueries uses its managed Google connection, so you can connect a property without creating a Google Cloud project or OAuth client.

Is it read-only?

Yes. FlexQueries requests read-only access (webmasters.readonly). The Search Console tools can read performance and inspect URLs without changing your Google property. The wider FlexQueries MCP also exposes write and paid tools.

Which AI clients work?

Clients must support remote HTTP MCP and OAuth. Supported clients include Claude Code, Claude Desktop, Cursor, Codex, and OpenClaw. Add the FlexQueries 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.

Point your AI at your real search data

No Google Cloud project. No charge to read your own data. Works with Claude, Codex, OpenClaw, OpenCode, and Gemini.