Google Search Console MCP server for Claude and other AI assistants
Connect Search Console to Claude, Cursor or any MCP client, then ask about queries, pages, clicks, positions and indexing in plain English. Setup takes about two minutes.
3 days free, then $10/month. Cancel any time.
A Google Search Console MCP server lets an AI assistant read your Search Console data directly, so you can ask questions instead of exporting reports. ClimbPast is a hosted one: sign in with Google, copy a key into Claude, Cursor or another MCP client, and you are connected in about two minutes. It is read-only by default.
What you can ask
ClimbPast gives your AI tools for Search Console performance, URL inspection and sitemaps. Questions like these work:
- “Which queries got the most clicks in the last 28 days?”
- “Which pages have lots of impressions but a low click-through rate?”
- “How did clicks and impressions change by date over the last 90 days?”
- “Which countries and devices send me the most clicks?”
- “Is this URL indexed by Google?”
- “Are any of my sitemaps showing errors or warnings?”
- “Compare clicks by page this month with last month.”
How to connect
This is the short version. The MCP docs have the full config for each client.
- 1Start your free trial and sign in with Google.
- 2Click Connect Google and approve read-only access in the Google popup. Pick the property you want to use.
- 3Create a cp_ key from your dashboard (Settings > API Keys).
- 4Add ClimbPast to your AI client as a remote MCP server. Use the server URL and send the key as a Bearer token. The Claude Code command is below.
- 5Ask your first question.
Claude Code:
claude mcp add --transport http climbpast https://climbpast.com/api/mcp --header "Authorization: Bearer cp_YOUR_KEY"
In claude.ai, go to Settings > Integrations > Add custom connector, set the URL to https://climbpast.com/api/mcp, choose Bearer token and paste your key. For Cursor, add the same URL and an Authorization header to mcp.json. The MCP docs have the full config for each client.
What data it reads
ClimbPast reads from the Search Console API, the same source as the Search Console website. It asks for read-only access when you connect.
- Search performance by query, page, date, device or country, plus URL inspection and sitemap status, through the webmasters.readonly scope.
- Your Google tokens are stored encrypted and are never sent to your AI. Your AI holds only a cp_ key.
- Revoke the key from your dashboard and it stops working right away. You can also revoke access from your Google account.
- Write access, such as submitting a sitemap, is off until you opt in from Settings. It needs its own Google consent.
ClimbPast vs connecting Search Console's API yourself
Google publishes its own APIs, and you can build an MCP server on top of them. ClimbPast is that server, already hosted.
| ClimbPast | Build it yourself | |
|---|---|---|
| Google sign-in | One OAuth popup. Read-only scopes by default. | You set up your own Google Cloud project, enable the APIs and create credentials. |
| What your AI holds | A short cp_ key you can revoke in one click. | Whatever credentials you give your own server. |
| Server | Hosted at the URL above. Nothing to run. | You build, host and maintain an MCP server. |
| Setup time | About two minutes (see the MCP docs). | Depends on your setup. |
Pricing
One plan. 3 days free, then $10 a month. Your card is collected when you start the trial, and you can cancel any time from your dashboard. See the pricing page.
Frequently asked questions
What is a Google Search Console MCP server?
A Google Search Console MCP server is a service that lets an AI assistant read your Search Console data through the Model Context Protocol (MCP). The assistant calls the server, the server asks Google for clicks, impressions and index status, and the assistant answers in plain English. ClimbPast runs one for you, so there is nothing to build or host.
How do I connect Google Search Console to Claude?
Start a ClimbPast trial, connect your Google account with read-only access, and create a cp_ key from your dashboard. Then add ClimbPast to Claude as a remote MCP server. In Claude Code that is one command. In claude.ai it is a custom connector with the server URL and your key as a Bearer token. The steps are above and in the MCP docs.
Is it read-only?
By default, yes. Google sign-in requests read-only scopes, so ClimbPast can read your Search Console data but cannot change it. Write actions, such as submitting a sitemap, are a separate opt-in you turn on in Settings, which triggers its own Google consent screen.
Does it work with ChatGPT?
ClimbPast is a standard remote MCP server, so it should work with any client that can add a remote MCP server with a Bearer token, including ChatGPT connectors. Our step-by-step setup guides cover Claude Code, claude.ai and Cursor. For ChatGPT or any other client, use the same server URL and send your cp_ key as a Bearer token.
What can it tell me that the Search Console website does not?
The data is the same, since ClimbPast reads it from Google. The difference is that you ask in plain English and your AI can combine it with GA4 data from the same connection, for example to look at search clicks next to sessions. See the Search Console analytics page for how the two fit together.
How much does it cost?
There is one plan. It is free for 3 days, then $10 a month. Your card is collected when the trial starts, and you can cancel any time.
Related