Google Search Console MCP server
Ask your AI assistant about your Google clicks, impressions, rankings and indexing, and get answers from your own Search Console data. Sign in with Google once in SEOForge. No Google Cloud project, credentials or code.
Included in every plan. Works with:
Claude Code
Cursor
Windsurf
VS Code- Any MCP client that takes an API key
Compare the last 28 days with the same period last year. Which pages lost the most clicks?
Clicks are down 9% on last year, and two pages explain most of it.
“Agile vs waterfall” lost 640 clicks. It still ranks 2nd, but impressions fell 40%, so fewer people are searching for it. Not much to fix there.
“Project budget template” lost 410 clicks after slipping from 4th to 9th. That one is worth refreshing.
Want me to plan what to change in the budget template article?
Try another question:
What you can ask about your Google Search Console data
Ask in your own words. Your assistant picks the right SEOForge tool, shown next to each question, and every one works with a read-only key.
- How have our clicks changed over the last 90 days?
get_search_traffic - What does this page actually rank for?
get_page_queries - Which pages are losing clicks, and why?
find_declining_pages - Which searches are almost on page one?
find_striking_distance - Which pages get seen but not clicked?
find_low_ctr_pages - Which of our pages compete with each other?
find_cannibalization - Which pages aren't in Google, and why?
find_indexing_issues - Which pages get no search traffic at all?
find_zombie_pages - What should this page's title be?
suggest_titles - Did the edits we made through SEOForge work?
measure_change_impact
Skip the Google Cloud setup
You can build your own Search Console MCP server from an open-source project. Here's what that takes, compared with SEOForge.
A do-it-yourself Search Console server
- Create a Google Cloud project and turn on the Search Console API
- Set up OAuth or a service account, and keep the credentials safe
- Install and run the server on every computer you use
- Your assistant gets raw rows from Google and has to do the analysis itself
Google Search Console through SEOForge
- Sign in with Google once in SEOForge, with read-only access
- Add one line to your AI tool. Nothing to install
- About 16 months of history, refreshed daily
- Analyses like declining pages and searches close to page one, built in
- Google Analytics, rank tracking and your articles in the same place
Set up in two minutes
You need an SEOForge plan or the free trial.
- 1
Connect Search Console in SEOForge
Open Search Console in SEOForge, click Connect with Google and pick your property. SEOForge gets read-only access and imports about 16 months of history.
- 2
Create an API key
In SEOForge, open Settings, then API & MCP. Name the key, choose its projects and copy it. It's shown only once.
- 3
Add SEOForge to your assistant
Run this in your terminal:
Terminalclaude mcp add --transport http --scope user seoforge https://www.seoforge.ai/api/mcp --header "Authorization: Bearer YOUR_API_KEY"Replace
YOUR_API_KEYwith the key you created. - 4
Ask your first question
Restart your assistant and try “Which of my pages get the most Google clicks?”
Stuck? The setup guide covers each client, limits and error messages.
More than Google Search Console
The same connection reads the rest of your SEO data, so your assistant can connect the dots: which searches bring visitors, which visitors convert, and what to write next.
See everything the SEOForge MCP server can do, or read about the Google Analytics MCP server.
Google Search Console MCP questions
It's a connector that lets AI assistants like Claude Code or Cursor read your Search Console data through MCP (Model Context Protocol). Instead of exporting reports, you ask questions in plain English, such as which pages lost clicks, and the assistant answers from your real numbers.
No. You connect Search Console in SEOForge by signing in with Google, then add SEOForge to your AI tool with an API key from your SEOForge settings. There's nothing to set up in Google Cloud and nothing to install.
No. SEOForge connects with read-only access, so neither SEOForge nor your AI assistant can change your property, settings or users.
SEOForge imports about 16 months of history when you connect, the most Google keeps, and refreshes it about once a day. Google publishes data with a 2–3 day delay, so the most recent days are always incomplete.
Any MCP client that can send an API key in a header, including Claude Code, Cursor, Windsurf and VS Code. ChatGPT and claude.ai connectors sign in with OAuth, which SEOForge doesn't support yet.
No. MCP access is included in every SEOForge plan and the 3-day free trial, and the Search Console tools have no data cost.
Yes. Connect Google Analytics in SEOForge and the same MCP server can answer questions about sessions, conversions and revenue, and combine them with your Search Console data.
Connect Google Search Console to your AI assistant today
Connect your site, and SEOForge builds your keyword plan and drafts your first articles in your brand voice. Try it free for 3 days.
