A Google Search Console MCP server lets Claude, ChatGPT or Cursor read your Search Console data and answer questions about it in plain English. MCPifex hosts one with 19 tools. You sign in with Google once, with no JSON keys and nothing to install, and every write action stays off until you turn it on.
What can you do with a Google Search Console MCP server?
You stop clicking through the dashboard and ask instead. The AI calls the right Search Console tool, reads the numbers, and explains them. It can pull clicks and impressions, compare two periods, check whether a page is indexed, and list your sitemaps. It does the sorting, filtering and summarizing that usually takes you an hour in a spreadsheet.
MCP is the standard that lets an AI app talk to outside tools. If the term is new, what is MCP explains it in a few minutes, and the official MCP introduction is the primary source. The idea is the same.
Which tools does it include?
There are 19 tools as of October 2026. 14 only read data and are on by default. 2 write and 3 are destructive, and all five of those start off. The tables group them by the job they do.
Search analytics
ToolTypeWhat it does
get_search_analyticsRead
Clicks, impressions, CTR and position for a date range.
get_performance_overviewRead
The overall performance trend for a property.
compare_search_periodsRead
Two date ranges side by side.
get_search_by_page_queryRead
Performance for each page and query pair.
get_advanced_search_analyticsRead
Several dimensions and filters at once.
URL inspection and indexing
ToolTypeWhat it does
inspect_url_enhancedRead
Google's URL Inspection for one URL.
batch_url_inspectionRead
URL Inspection for many URLs in one call.
check_indexing_issuesRead
Scans a property for common indexing problems.
Sitemaps
ToolTypeWhat it does
get_sitemapsRead
Lists the sitemaps submitted for a property.
list_sitemaps_enhancedRead
Lists sitemaps with status and error detail.
get_sitemap_detailsRead
Submission and indexing details for one sitemap.
submit_sitemapWrite (off by default)
Submits a sitemap URL.
manage_sitemapsWrite (off by default)
List, inspect, submit or delete sitemaps in one call. Delete works only if delete_sitemap is also on.
delete_sitemapDestructive (off by default)
Permanently removes a submitted sitemap.
Site management
ToolTypeWhat it does
get_capabilitiesRead
What the server and its data states support.
list_propertiesRead
The properties your connected account can see.
get_site_detailsRead
Verification and permission details for one property.
add_siteDestructive (off by default)
Adds a property to the connected account.
delete_siteDestructive (off by default)
Removes a property from the connected account.
A fresh instance can only read. The gateway hides every tool that is off from the AI's tool list and refuses a call to it, even if the AI asks by name. For most marketers the safe default is to leave all five write and destructive tools off. Turn on submit_sitemap only if you want the AI to submit a new sitemap after a site launch. Keep delete_site and delete_sitemap off unless you have a specific cleanup in mind, because removing a property cannot be undone from the AI. You change these switches per API key in the portal. See instances and tools for where.
What can you ask it? 10 example prompts
Copy these and swap in your own site and dates. Each one works with read tools only.
- "Which queries lost the most clicks this month compared with last month?"
- "Which pages have more than 1,000 impressions and a click-through rate under 1%?"
- "List my top 20 queries on positions 8 to 15. Those are the ones a small content update might push onto page one."
- "Compare mobile and desktop clicks for the last 28 days and tell me where the gap is biggest."
- "Which pages get impressions for the same query? Flag possible cannibalization."
- "Is /pricing indexed? If not, show me the reason Google gives."
- "Inspect these 30 URLs from my last blog batch and group them by indexing status."
- "Which sitemaps have errors, and what do the errors say?"
- "Show clicks by country for the last 90 days and name the three countries growing fastest."
- "Write a one-page monthly SEO report for my site: totals, biggest winners, biggest losers, three actions."
For a worked reporting example in ChatGPT, read Search Console data in ChatGPT. To pair your own rankings with demand data, the Google Trends server runs beside this one on the same endpoint.
How do you connect it with Google sign-in?
You do not paste an API key from Google or upload a JSON file. You click Connect Google account and sign in, the same way you would sign in to any Google app. The account must be an owner or full user of the property, and it can differ from the account you use to log in to MCPifex. How MCPifex stores and uses connected accounts is covered in connected accounts and OAuth.
- Create a free MCPifex account. The Free plan includes 3 instances and needs no card.
- Pick Google Search Console in the marketplace and name your instance.
- Click Connect Google account and sign in with the account that owns your property.
- Choose a Data state. All matches the Search Console dashboard and is the default. Final only returns settled data that runs two to three days behind.
- Leave the write and destructive tools off, then click Test connection; a wrong sign-in or missing permission shows up straight away.
- Generate an API key, then add MCPifex to your AI app. Claude and ChatGPT have step-by-step pages, and custom connectors in Claude covers the web app.
The key starts with mcpx_. Replace <YOUR_MCPX_KEY> in the snippets with it. The gateway URL is https://mcp.mcpifex.com/mcp.
Claude Code
claude mcp add mcpifex --transport http https://mcp.mcpifex.com/mcp \
--header "Authorization: Bearer <YOUR_MCPX_KEY>"Cursor
Add this to .cursor/mcp.json in your project, or to Cursor's global mcp.json, then reload Cursor:
{
"mcpServers": {
"mcpifex": {
"type": "http",
"url": "https://mcp.mcpifex.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MCPX_KEY>"
}
}
}
}Claude Desktop
Use Claude's remote custom connector where it's available. Otherwise, this mcp-remote bridge works, and needs Node.js and npx. Merge the mcpifex entry into the mcpServers object in claude_desktop_config.json, then restart the app:
{
"mcpServers": {
"mcpifex": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.mcpifex.com/mcp",
"--header",
"Authorization:${MCPIFEX_AUTH_HEADER}"
],
"env": {
"MCPIFEX_AUTH_HEADER": "Bearer <YOUR_MCPX_KEY>"
}
}
}
}ChatGPT
ChatGPT's custom MCP form has no header field, so the key goes in the URL: https://mcp.mcpifex.com/mcp/<YOUR_MCPX_KEY>. The quickstart has the step-by-step ChatGPT setup. Treat that URL like a password.
Bing reports its own clicks and queries. If you track both engines, the Bing Webmaster Tools MCP server gives the same AI access to Bing data with one API key, so you can ask about both in one chat.
How does it compare with other Search Console MCP options?
There are three ways to get one, and each fits a different person. This comparison is as of October 2026, and the details come from each project's own page.
- Self-hosted open source. AminForou/mcp-gsc is a free, MIT-licensed server for search analytics, URL inspection and sitemaps. Suganthan's GSC MCP is also free and runs locally. Its README lists opportunity-finding tools such as CTR opportunities, traffic drops, cannibalization and content decay. Both cost you setup time: you run them on your own machine and create Google credentials.
- Other hosted options. Advanced GSC is a hosted server with Google sign-in. Its pricing page showed a Starter plan at $15 a month for up to 3 properties at the time of writing. Google Analytics 4 is on its Pro plan at $40 a month. RankBuddy is a hosted connector that adds keyword, competitor and backlink data to Search Console. Check its pricing page for current plans.
- MCPifex. MCPifex runs a hosted server built on an open-source Search Console server, with Google sign-in instead of credentials, plus per-key tool switches and a log of every call. Plans limit instances, not calls: Free has 3 instances, Pro is $19 a month with 10, and Team is $49 a month with 30. See pricing.
Choose a self-hosted server if you are comfortable with a terminal and want the most control. Choose a hosted tool built around SEO research if you need keyword and backlink data alongside Search Console. Choose MCPifex if you want Search Console in Claude or ChatGPT with no install, and if the same endpoint should also reach other servers. Best MCP servers compares the wider field.
What are the limits and data lag?
The server reads from the Google Search Console API, so Google's rules apply to it. Three limits matter for day-to-day use.
- Fresh data is not final. In the API, the
dataStatesetting controls this. Fresh data can include rows that are still being collected, while final data includes only finished days. That is why the Data state option exists. Google documents this in the Search Analytics query reference. - Row limit per request. A single Search Analytics request returns at most 25,000 rows. Very large sites need narrower questions, such as one section or one country at a time.
- Quotas. Google lists Search Analytics limits of 1,200 queries per minute per site, and URL Inspection limits of 2,000 queries per day and 600 per minute per site. Google also applies load quotas to heavy queries. All of this is on the usage limits page.
The URL Inspection API reports the version of a page that is in Google's index. It cannot test a live URL, as the URL Inspection reference states. If you just fixed a page, the answer reflects what Google last indexed, not your fix. Batch inspection of a few hundred URLs will also use up the daily quota, so inspect the pages that matter first.
If Google revokes access, for example because a Workspace admin blocks third-party apps, the instance shows a revoked connection. Connect the account again to fix it. Each AI session gets its own isolated server process, and every call is logged in the portal.
Frequently asked questions
Yes. MCPifex hosts one with 19 tools. You sign in with Google, add the MCPifex URL as a custom connector in Claude, and ask about clicks, rankings and indexing. Open-source and other hosted options exist too, compared above.
Not with MCPifex. You click Connect Google account and sign in. The account must be an owner or full user of the Search Console property you want to query.
Only if you allow it. The three destructive tools (add_site, delete_site, delete_sitemap) and the two write tools start off. The gateway hides them and refuses calls to them until you switch them on for a key.
Usually the data state. All includes fresh, not-yet-final days, as the dashboard does. Final only returns settled data, which runs two to three days behind. Check the date range and filters you asked for too.
MCPifex has a Free plan with 3 instances and no card, with unlimited tool calls on every plan. Self-hosted servers such as mcp-gsc are free but you run them yourself. Some hosted competitors charge monthly.
Run this server through MCPifex
Run hosted MCP servers behind one endpoint and choose exactly which tools your AI can use.