Google Search Console · Plan: Free
Google Search Console MCP server, hosted.
Connect your Search Console properties once. Then ask questions in plain language from Claude, Cursor, Windsurf, VS Code or ChatGPT and get analysis back, not a CSV. 20 Search Console tools, from raw search analytics to content decay, cannibalization and brand split.
Start free No card. Connect a Google account in one minute.
Questions you can ask
- “Which pages lost the most clicks in the last 7 days compared to the week before?”
- “Show me queries on positions 5 to 20 with at least 100 impressions, ranked by potential.”
- “Where is my CTR far below what the position should deliver? Which titles need work?”
- “Do I have keyword cannibalization, and which page should win?”
- “How is non-brand traffic developing compared to brand traffic?”
- “Did traffic drop after the last core update? Show daily clicks with anomalies.”
- “Which question-shaped queries lead to my site? Build me an FAQ from them.”
- “Is my sitemap processed and are there URLs with indexing problems?”
Why hosted
No Google Cloud setup
No project, OAuth client, consent screen or verification. Sign in, pick properties, done.
All clients, one URL
Agencies connect every client's Google account into one workspace and switch properties by name.
Analysis, not raw rows
Quick wins, CTR opportunities, decay and cannibalization are computed server-side with sane defaults.
Daily watch
Every property is analyzed once a day. Drops and data gaps become findings and alerts.
Add it to your client
claude.ai, ChatGPT: add a custom connector with this URL
https://metricport.io/api/mcpClaude Desktop, Cursor, Windsurf, VS Code
{
"mcpServers": {
"metricport": {
"command": "npx",
"args": ["-y", "metricport-mcp"],
"env": { "METRICPORT_API_KEY": "mp_your_api_key" }
}
}
}20 Tools
gsc_search_analytics | Clicks, impressions, CTR and position by query, page, country, device, date or search appearance. Filters, search type and period comparison. |
gsc_top_queries | Top queries by clicks, optionally for one page. |
gsc_top_pages | Top pages by clicks, optionally for one query term. |
gsc_page_queries | Every query one URL ranks for, with position. |
gsc_quick_wins | Striking-distance queries (positions 5-20) ranked by potential extra clicks, with the ranking page. |
gsc_ctr_opportunities | Page-one queries whose CTR is far below the expected curve: title and snippet problems with missed clicks. |
gsc_content_decay | Pages that lost the most clicks vs. the previous period or last year, plus the winners. |
gsc_new_and_lost_queries | Queries that appeared or disappeared between two periods. |
gsc_cannibalization | Queries where several of your pages compete, with leader share and competitors. |
gsc_brand_split | Brand vs. non-brand totals, click share, trend and top non-brand queries via regex. |
gsc_query_clusters | Groups queries into topic clusters with totals and examples. |
gsc_question_queries | Question-shaped queries (how, what, why, wie, was…) for FAQs and snippets. |
gsc_zero_click_pages | Pages with impressions but no clicks. |
gsc_daily_trend | Daily clicks and impressions with 7-day average and flagged drops or spikes. |
gsc_device_country_breakdown | Performance per device and country with the mobile vs. desktop CTR gap. |
gsc_search_appearance | Search appearance types plus Discover and Google News traffic. |
gsc_inspect_url | Index status, crawl date, canonical and rich result status for one URL. |
gsc_index_check | Batch inspection of up to 10 URLs with canonical mismatch and blocker flags. |
gsc_sitemaps | Submitted sitemaps with errors, warnings and URL counts. |
gsc_weekly_report | One-call weekly summary: totals, winners, losers, new queries, quick wins, anomalies. |
MetricPort vs. running an open-source MCP server yourself
| Open-source, local | MetricPort | |
|---|---|---|
| Google Cloud project, OAuth client, consent screen | You set it up and keep it verified | Done, Google-reviewed app |
| Several Google accounts (clients) | One per server instance | Unlimited on Agency, all behind one URL |
| Works from claude.ai, ChatGPT, phone | No, needs a local process | Yes, remote server with OAuth |
| Analysis tools | Raw API wrappers | 57 tools: decay, quick wins, wasted spend, cannibalization, pacing |
| Daily insights, alerts, client reports | No | Yes |
| Write access to your accounts | Depends on the server | Never, read-only by design |
| Cost | Free, plus your time | Free plan, Pro 19 €, Agency 79 € |
FAQ
- Is this the official Google Search Console MCP?
- No. Google does not offer an MCP server. MetricPort uses the official Search Console API with your consent and is reviewed by Google under its API Services User Data Policy.
- What does it cost?
- Search Console is included in the Free plan: one Google account, 500 tool calls per month. Pro adds more accounts, Google Ads and AdSense, daily insights and alerts.
- Can it change anything in my Search Console?
- No. MetricPort only requests the read-only scope. It cannot submit sitemaps, remove URLs or change settings.
- Which clients work?
- Anything that speaks MCP: claude.ai and Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, ChatGPT with custom connectors, n8n, and your own agents via the API key.
- How fresh is the data?
- As fresh as Search Console itself, which lags about two days. Responses are cached for five minutes.