GSCPAP - Google Search Console, GA4, PageSpeed Insights & live SERPs MCP
Read-only Google Search Console, GA4, PageSpeed Insights and live SERPs for Claude, ChatGPT and Cursor, with Search Console history past Google's 16-month limit. Hosted and free.
Hosted MCP Server
npx add-mcp 'https://mcp.gscpap.com/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
v0.3 - public previewFree, no credit card
Ask Claude about your Google Search Console.
Free. Sign in with Google, then either add GSC PAP as a connector in one click or paste one token into Claude Desktop, Cursor or Claude Code. Ask anything about your sites - top queries, decaying pages, ranking trends. GSC PAP is a hosted bridge that exposes your Google Search Console, Analytics 4 and PageSpeed data to AI assistants over the Model Context Protocol. No GCP project, no Python, no JSON files.
Free · OAuth via Google · Read-only Search Console scope · Revoke anytime · Privacy Policy
claude · gsc-pap
›
9,914
Tool calls served (live)
38
MCP tools available
covering the full GSC API surface
16+
Months of search history
we archive past Google's 16-month limit
Any MCP
AI clients supported
Claude Desktop, Cursor, Claude Code
What GSC PAP does
A hosted web service that connects your Google Search Console account to AI assistants over the Model Context Protocol. Read our Privacy Policy for the full data & storage details.
Hosted bridge
Sign in with Google once. We store an encrypted refresh token and call the Search Console API on your behalf when your AI assistant asks a question. No Python process to run, no JSON files to manage.
Read-only data access
We request the webmasters.readonly scope - the same data you see in your own Search Console UI: sites, search analytics, sitemaps, URL inspection. We never modify, delete, or write anything in Search Console.
Model Context Protocol
Claude Desktop, Cursor, and Claude Code call external tools through MCP. We expose your Search Console as a single MCP endpoint with one bearer token you paste into your AI client config.
Encrypted + revocable
Refresh tokens are AES-256-GCM encrypted at rest. Bearer tokens stored as SHA-256 hashes only. Revoke any token in one click; account deletion is real and final within 30 days.
38 tools, one MCP server
Every Search Console + GA4 + PageSpeed capability your AI assistant might need. Click a category to expand. Linking to #tool_name opens the right one automatically.
Browse the full 38-tool catalog
Spot quick SEO wins
2 tools
Surface low-hanging fruit your team can ship this week. Pages ranking just outside the top 10, queries cannibalizing each other.
find_quick_wins
Find queries ranking positions 5 to 20 with at least 100 impressions but under 5% CTR: the title and snippet fixes most likely to lift clicks.
find_cannibalization
Detect keyword cannibalization where multiple URLs compete for the same query, splitting click-through and confusing Google.
Find what's losing traffic
4 tools
Catch decaying pages and ranking drops before they tank your monthly traffic numbers. Compare any two periods, track positions over time.
find_content_decay
Identify pages losing organic traffic over time so you can refresh the content before rankings collapse.
historical_position_trend
Plot a query's position over the last N days to see whether you're trending up, down, or volatile.
compare_periods
Diff any two date ranges (e.g. last 28 days vs prior 28) to spot wins and losses across queries, pages, or countries.
find_dead_pages
Pages that have been appearing for months and have never earned a click, split by whether Google is showing them and nobody clicks (a listing problem) or barely showing them at all (not a listing problem). The larger group on most sites.
Beat the 16-month limit
2 tools
Google Search Console only retains 16 months of search data. GSC PAP runs a per-account archive so you can query years of history through Claude or Cursor.
archive_status
Check archive coverage per site: earliest date, latest date, row count, last successful run.
Diagnose performance & Core Web Vitals
2 tools
Run a Lighthouse audit or pull real-user (CrUX) Core Web Vitals for any public URL, right from your AI client. Lab data plus actual visitor metrics, with the top optimization opportunities ranked by potential time savings.
pagespeed_insights
Run a Google PageSpeed Insights (Lighthouse) audit. Returns performance / accessibility / best-practices / SEO scores, Core Web Vitals lab values (LCP, FCP, CLS, TBT), and the top opportunities ranked by potential savings.
pagespeed_field_data
Pull real-user Core Web Vitals from the Chrome User Experience Report (CrUX). LCP, INP, CLS at the 75th percentile, plus FAST/AVERAGE/SLOW rating, for both URL and origin level.
Diagnose indexing issues
4 tools
Find out exactly why pages aren't indexed. URL Inspection API in bulk, full coverage summary, single-URL deep dives without tab-switching the GSC UI.
get_index_coverage_summary
Get an account-wide breakdown of indexing states (indexed, crawled-not-indexed, discovered-not-indexed) so you know where to focus.
inspect_url
Single-URL deep dive: indexability, last crawl, canonical, mobile usability, structured data. The full URL Inspection API result.
batch_inspect_urls
Bulk URL Inspection, up to 10 URLs per call within Google's 2,000-per-day quota. Diagnose why a content cluster or sitemap isn't getting indexed.
find_new_pages
Pages Search Console started showing in the last week, and whether each one has earned a click yet. Across this archive, 90% of the clicks new pages ever earn go to pages clicked in their first seven days, so a page still silent after a week rarely becomes anything.
Pull performance data
3 tools
All the Search Analytics API capabilities, exposed natively to AI assistants. Skip the Google Cloud project setup, the OAuth dance, and the JSON parsing.
get_performance_overview
High-level performance snapshot for a site: clicks, impressions, CTR, position over the last N days.
search_analytics_query
Run any Search Analytics query with full dimension and filter support, identical to what you'd hit the GSC API for, but inline in chat.
Connect search to engagement & revenue (GA4)
11 tools
Pair GSC discovery with GA4 conversion data. Sessions, real-user engagement, top pages, conversions and revenue by source. The killer cross-tool joins GSC clicks per page to GA4 sessions, conversions, and revenue so you can see which top-ranking pages actually convert.
list_ga4_properties
List every Google Analytics 4 account and property the user can access. Always call first to discover the property_id needed for the other GA4 tools.
ga4_overview
High-level GA4 snapshot for a property: active users, sessions, new users, page views, bounce rate, average session duration, engagement rate, plus a per-day breakdown.
ga4_top_pages
Top pages by sessions over the last N days. One row per page path with sessions, active users, page views, bounce rate, average session duration. A session counts on every page it views, so the rows do not add up to total sessions.
ga4_traffic_sources
Acquisition breakdown by channel, source, medium, or campaign. Rows with sessions, active users, conversions per bucket. Choose the dimension to slice by.
ga4_realtime
Active users in the last 30 minutes broken down by country, device, city, current page, or minutes-ago. Plus the total active count.
ga4_conversions_by_source
Conversion attribution by source × medium with sessions, conversions, total revenue, and purchase revenue. Sorted by conversions to surface the channels driving outcomes.
ga4_user_demographics
Audience snapshot: top countries, device categories (desktop/mobile/tablet), and browsers. Useful for segmenting reports or identifying mobile-vs-desktop performance gaps.
ga4_engagement
Per-page engagement metrics. Engaged sessions, engagement rate, average session duration, bounce rate, event count. Spot pages that bring traffic but lose users.
ga4_events_by_name
Event-level breakdown: scroll depth, outbound clicks, file downloads and custom events, with event counts and users. Optionally per page, to answer questions like how many homepage visitors scrolled to 90%.
ga4_compare_periods
Diff any two windows for any GA4 metric (sessions, conversions, revenue, etc.). Week-over-week, month-over-month, with optional dimension slice. Returns absolute and percentage delta.
correlate_gsc_to_ga4
Cross-tool killer: join GSC clicks per page with the Google organic sessions, conversions and revenue GA4 recorded for visits landing on that page. Answer 'which top-ranking organic pages actually convert?' in one tool call instead of two manual exports.
See how AI assistants send you traffic (GEO)
2 tools
ChatGPT, Perplexity, Gemini and Claude now send visits of their own. See how many, which pages they recommend, and which queries an AI Overview is likely answering above you.
ga4_ai_traffic
AI assistant traffic from GA4: sessions per engine, share of total, ratio to Google organic, change against the previous period, and the landing pages assistants send people to beside their organic sessions. Counts the assistant visits GA4 files outside its AI Assistant channel too, about 10% on the sites we measured. Pass property_id="all" to compare every site you have.
find_ai_overview_suspects
Queries whose CTR fell while their position held, compared with the same dates a year ago or the period before: the footprint an AI Overview leaves in Search Console. Labelled as a suspicion, because Search Console does not report AI Overviews.
See who ranks above you on Google
3 tools
Search Console tells you your position, not who holds the spots above it or what is taking the clicks. Pull the live Google results for any query.
serp_top_results
Live Google results for any query and country: the top organic results plus which SERP features are present, such as featured snippet, map pack and People Also Ask. AI Overviews are reported as unknown, never as absent.
serp_competitor_analysis
Where your domain ranks for a query and the full top 10 around it. Pair it with find_quick_wins to see exactly who is beating you on a query you are close on.
serp_features_audit
Check up to 25 queries at once for click-eating SERP features. Explains why CTR is low at a good position: a featured snippet, map pack or People Also Ask above you. Says so when a country returns no feature data, instead of reporting none.
Manage sites & sitemaps
5 tools
List your verified properties, audit sitemap health, find duplicate property registrations that split your reporting.
list_sites
List every Search Console property you have access to, with verification state and permission level.
get_site_details
Permission level, verification state, and metadata for a single site URL.
list_sitemaps
List all sitemaps submitted for a property along with last download time and status.
get_sitemap_details
Per-sitemap detail: last submitted and downloaded, errors, warnings, and URLs submitted.
detect_duplicate_properties
Find duplicate Search Console properties (e.g. http vs https, www vs apex) that split your reporting and waste verification slots.
Works with your AI assistant
One sign-in, 27 documented clients. Pick yours and follow the short setup. The same token works across all of them, so you can switch clients without re-authorizing.
[
Claude.ai (browser)
Add Google Search Console to Claude.ai as a custom connector. Paste one URL and approve access. No token to copy, no config file, no Google Cloud project.
3 min setup
](https://gscpap.com/integrations/claude-ai-connectors)[
Claude Desktop
Connect Claude Desktop to Google Search Console without creating a Google Cloud project. Sign in with Google, paste one config block, restart Claude.
6 min setup
](https://gscpap.com/integrations/claude-desktop)[
Claude Code
Add Google Search Console to Claude Code with one claude mcp add command. Hosted and read-only: no Google Cloud project, no OAuth credentials, no Python.
3 min setup
](https://gscpap.com/integrations/claude-code)[
Cursor
Connect Google Search Console to Cursor through a hosted MCP server. Sign in with Google, paste one token into mcp.json, and skip the Google Cloud project.
5 min setup
](https://gscpap.com/integrations/cursor)[
ChatGPT
Add Google Search Console to ChatGPT as a custom MCP server. What the setup looks like, and the plan requirement that decides whether you can do it at all.
6 min setup
](https://gscpap.com/integrations/chatgpt)[
VS Code (GitHub Copilot)
Connect Google Search Console to GitHub Copilot in VS Code with one.vscode/mcp.json entry, then ask agent mode about GSC. You skip Google Cloud setup.
4 min setup
](https://gscpap.com/integrations/vscode-copilot)[
Codex CLI (OpenAI)
Add Google Search Console, GA4 and PageSpeed data to OpenAI's Codex CLI with one TOML block and a bearer token. You never create a Google Cloud project.
4 min setup
](https://gscpap.com/integrations/codex-cli)[
Gemini CLI (Google)
Query Google Search Console (GSC) from your terminal with Gemini CLI. Register GSC PAP as an MCP server in settings.json, with no Google Cloud project.
5 min setup
](https://gscpap.com/integrations/gemini-cli)[
Windsurf (Devin Desktop)
Give Windsurf, now Devin Desktop, your Google Search Console data. Add GSC PAP as a remote MCP server with one bearer token and no Google Cloud project.
5 min setup
](https://gscpap.com/integrations/windsurf)[
Continue (extension)
Continue MCP setup for Google Search Console: add one mcpServers entry with a bearer token in VS Code or JetBrains. You do not need a Google Cloud project.
4 min setup
](https://gscpap.com/integrations/continue)[
Zed Editor
Bring Google Search Console into Zed's AI assistant as an MCP context server. You add one settings.json block and a token, with no Google Cloud setup.
4 min setup
](https://gscpap.com/integrations/zed)[
Direct HTTP (curl, custom agents)
Call the GSC PAP MCP server from curl or your own agent. It is JSON-RPC over HTTP with a bearer token, so you need no MCP client or Google Cloud project.
5 min setup
](https://gscpap.com/integrations/mcp-direct)
Also set up and documented: JetBrains IDEs, opencode, Cline, Warp, LM Studio, Goose, Google Antigravity, Roo Code, Kilo Code, Amp, Kiro, Raycast, GitHub Copilot CLI, n8n, LibreChat.
What people do with it
Real SEO workflows you can run by asking your AI assistant. Each guide includes the exact prompt, the underlying GSC PAP tools it calls, and what the answer looks like.
How to find striking distance keywords in Google Search Console
Striking distance keywords rank just off page one of Google. Find them in Search Console, pick the ones worth fixing, and learn what to change on the page.
8 min read
How to find keyword cannibalization in Google Search Console
Check for keyword cannibalization in Google Search Console: find queries where your pages compete, judge whether it hurts, and fix the cases that do.
8 min read
GSC clicks vs GA4 sessions: why they differ and how to tie clicks to conversions
A Search Console click and a GA4 session measure different things. Why the numbers never match, what gap is normal, and how to compare and combine them page by page.
11 min read
Audit Core Web Vitals across your site with AI
Audit Core Web Vitals with Claude through a hosted PageSpeed Insights MCP server: Lighthouse lab data and real-user CrUX field data for your top pages.
7 min read
Google Search Console historical data: how to keep it past 16 months
Google Search Console keeps 16 months of historical data, then deletes it. Here is what it includes and how to keep it longer, from BigQuery to an archive.
8 min read
Build a weekly SEO health report with Claude
Automate a weekly SEO report with Claude: one saved prompt pulls Search Console changes, quick wins, decaying pages, GA4 conversions and Core Web Vitals.
8 min read
Bulk URL inspection in Google Search Console: diagnose indexing issues at scale
Search Console inspects one URL at a time. The URL Inspection API allows 2,000 checks a day per property. How to inspect in bulk and find indexing issues.
8 min read
Track keyword rankings in Google Search Console, past the 16-month limit
See a keyword's position history in Google Search Console, what that average really measures, and how to keep ranking history past the 16-month limit.
6 min read
Google Search Console anonymized queries: measure the traffic you can't see
Search Console hides anonymized queries from query rows but counts them in totals. Learn what they are, why no tool reveals them, and how to measure them.
6 min read
Good position, no clicks: find the SERP features eating your CTR
Ranking third and getting no clicks usually means something sits above you: an AI Overview, a featured snippet or a map pack. How to check which, query by query.
7 min read
Find the pages quietly losing organic traffic, before the rankings go
Content decay is slow enough to miss on a dashboard. How to find the pages whose clicks keep sliding, tell decay from seasonality, and decide what to refresh.
7 min read
Traffic changed: how to compare two Search Console periods and find out why
Clicks are down 18% and nobody knows why. How to compare two periods properly, avoid the three traps that fake a drop, and find the queries and pages behind it.
7 min read
AI queries in Google Search Console: how to tell people, AI Mode and agents apart
Search Console mixes AI Mode follow-ups, AI agent searches and scripts into your query report. How to spot each one, with regex filters and real data.
14 min read
Who uses GSC PAP?
Anyone whose work touches Google Search Console and who already uses an AI assistant. The product makes the second tool answer questions about the first one.
SEO consultants
Audit client sites in Claude Desktop. Run quick-wins, find cannibalization, spot decaying pages without opening a separate dashboard for each client.
In-house SEO + content teams
Ask "what's broken this week" in your team chat without anyone touching the Search Console UI. Pipe answers into Slack via your AI client.
Solo developers
Connect your personal site. Get AI-driven SEO insights inline while you write content or fix code in Cursor / Claude Code.
Agencies
Run cross-client SEO reports through one Claude session. Each user keeps their own scoped GSC PAP token; no shared dashboards or seat licenses.
How it works
Three steps, sixty seconds. No GCP project setup, no client_id JSON, no Python venv.
01
Sign in with Google
Standard OAuth, read-only Search Console scope. Your refresh token is encrypted at rest with AES-256-GCM.
02
Get your token
We mint a long-lived bearer token, shown once. Copy it into your MCP client config - Claude Desktop, Cursor, or anything else.
03
Ask anything
"What are my decaying queries?" "Find cannibalization on this domain." 38 tools for Search Console, GA4 and PageSpeed, real data, real time.
Built for technical users who care about access
We built this because we were tired of the OAuth client setup dance. Same here.
Your data, yours alone
Your Search Console archive is visible only to you. No other GSC PAP user can see it - ever.
Revoke anytime
One click revokes your token at Google + in our DB. Account deletion is real and permanent within 30 days.
Encrypted at rest
Refresh tokens are AES-256-GCM encrypted with envelope keys. Bearer tokens stored as SHA-256 hashes only.
Read-only by design
We only hold the read-only Google scope. Even if our service were compromised, no one can edit or delete anything in your Search Console.
vs self-hosting
Self-host is great for ops teams. For everyone else, the GCP setup kills momentum before the first query. The other hosted Search Console MCP servers are compared separately, prices included.
Self-host
Run gsc-pap-server on your own infra
- Set up a Google Cloud project
- Configure an OAuth web client
- Manage a Python venv + dependencies
- Edit JSON config files for each AI client
- Maintain Postgres + Redis + Cloudflare Tunnel
Time to first query~45 minutes
Recommended
GSC PAP (hosted)
Free, plug & play, no infra
- No Google Cloud project
- No OAuth client config
- No Python or dependencies to manage
- No JSON files (one paste in your AI client)
- No Postgres, no Redis, no infra ops
Time to first query60 seconds
Common questions
Quick answers. The full FAQ covers setup, privacy, supported clients, limits, and more.
Do I need a Google Cloud project to use GSC PAP?
No. The whole reason GSC PAP exists is to remove the Google Cloud setup step. When you sign in with Google through gscpap.com, you grant permission to our OAuth client (which we registered with Google one time). We then call the Search Console API on your behalf using your refresh token. You never touch the Google Cloud Console.
What Search Console data can GSC PAP access?
GSC PAP requests the webmasters.readonly OAuth scope - the same read-only level you would grant to any third-party Search Console viewer. Specifically we can read your verified site list, search analytics (clicks, impressions, CTR, position by query, page, country, device, date), sitemap submission status, and URL inspection results. This is exactly the data you see in your own Search Console UI. It also has the same gaps: Google leaves anonymized queries out of query rows in both the UI and the API, so GSC PAP cannot reveal them either. If you also connect Google Analytics, GSC PAP holds the analytics.readonly scope as well, and any Analytics data it keeps for you follows the same rules as your archive.
Is GSC PAP free? What are the limits?
Yes, GSC PAP is completely free during the public preview (v0.x). There is no credit card required, no trial expiration, and no premium feature gate. The only limits are technical ones to protect the service: 60 MCP tool calls per minute and 1,000 per hour per user. These limits are generous - typical AI assistant usage is 5-20 calls per question, so you can ask hundreds of questions per hour without hitting them.
How far back does my data go?
Google Search Console itself only retains the most recent 16 months of data. Anything older drops off Google's side and cannot be recovered, even with API access - this is a hard limit Google enforces on every Search Console user, including direct users of the official Google Search Console UI.