Google Search Console × Model Context Protocol

Plug Google Search Console into Claude in 60 seconds.

One personal MCP URL. Works in Claude, Cursor, Codex, and Antigravity. No code, no chatbot — your AI just gets superpowers.

Free to start · OAuth secured · Read-only by default

claude.ai → connectors → custom mcp

Your MCP URL

https://mcp.genieseo.app/u/8f3e2a91Active

Properties

12

Requests · 7d

1,284

Tools

21

Works with the AI clients you already use

Claude
Claude Desktop
Cursor
Codex
Antigravity
The bridge

Search Console data, where your AI works.

GenieSeo is a secure relay between Google Search Console and any MCP-compatible AI client. Set it up once. Use it everywhere.

Search Console

GenieSeo MCP

Claude
Cursor
Codex
Antigravity
How it works

From zero to AI-powered SEO in three steps.

No SDKs, no servers, no chatbot to babysit. Once it's connected, your AI client owns the workflow.

STEP 01

Create your account

Sign up with email. We provision a personal MCP namespace for you in the background.

Create account

STEP 02

Connect Google

Authorize Search Console via OAuth. We fetch your verified properties and store nothing you don't see.

Authorized · 12 properties
oauth.google.com → genieseo.app
STEP 03

Paste MCP URL

Copy your URL into Claude, Cursor, Codex or Antigravity's connector settings. Done.

https://mcp.genieseo.app/u/8f3e
What you get

Every Search Console capability — exposed as tools your AI calls directly.

Search analytics

Clicks, impressions, CTR, position — query, page, date.

URL inspection

Index status, mobile usability, structured data per URL.

Sitemap management

List, submit, verify, and audit sitemaps end-to-end.

Indexing checks

Find indexing issues across batches of URLs.

Period compare

YoY and MoM comparisons with diff & deltas baked in.

Property details

Permission level, verification, hierarchy, status.

2-minute setup

Paste your URL into any MCP-aware client.

We support every major AI workspace. Same URL — different connector UI per client. Step-by-step instructions live inside your dashboard.

ClaudeClaude DesktopCursorCodexAntigravity
Settings → Connectors → Custom MCPConnected

Server name

GenieSeo · Search Console

Server URL

https://mcp.genieseo.app/u/8f3e2a91
json · claude desktop
{
  "mcpServers": {
    "genieseo": {
      "url": "https://mcp.genieseo.app/u/8f3e2a91"
    }
  }
}
Security

Your tokens never leave our encrypted vault.

OAuth tokens are sealed at rest. URLs are personal and revocable in one click. Read-only by default — you opt into anything that writes.

  • OAuth 2.0 authorization with Google
  • AES-encrypted credential vault
  • Per-user MCP URL with rotate / revoke
  • Read-only by default — destructive actions opt-in
  • Full activity log of every tool call
FAQ

Questions, answered.

What is MCP?+

Model Context Protocol — an open standard that lets AI clients connect to external tools and data over a single URL. We are an MCP server for Google Search Console.

Is there a chatbot inside GenieSeo?+

No. GenieSeo is the connector. All AI conversations happen inside Claude, Cursor, Codex, or Antigravity — wherever you already work.

What can my AI do once connected?+

Pull search analytics, inspect URLs, manage sitemaps, compare periods, run indexing checks — every Google Search Console capability, exposed as tools.

Is my Google data safe?+

Yes. OAuth tokens are encrypted at rest, never shared, and accessible only through your personal MCP URL. Revoke anytime.

Can I use multiple Google accounts?+

One Google account per GenieSeo account today. Multi-account workspaces are on the roadmap.

How much does it cost?+

Free to start with generous limits during beta. Paid tiers will arrive with team workspaces, larger property counts, and priority support.

Beautifully done. Now your AI sees what Google sees.

Set it up once. Use it everywhere your AI lives.