36 free SEO MCP tools for Claude, Cursor, and Claude Code

Every tool GSC PAP exposes over the Model Context Protocol, pulling data from Google Search Console, Google Analytics 4, and PageSpeed Insights. Surface quick-win pages, find content decay, detect keyword cannibalization, audit Core Web Vitals, and join organic clicks to GA4 conversions in a single chat message.

Free, hosted, read-only. No Google Cloud project, no Python venv, no JSON files to manage.

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.

Used in: How to find striking distance keywords in Google Search Console, GSC clicks vs GA4 sessions: why they differ and how to tie clicks to conversions, Build a weekly SEO health report with Claude, Good position, no clicks: find the SERP features eating your CTR

find_cannibalization

Detect keyword cannibalization where multiple URLs compete for the same query, splitting click-through and confusing Google.

Used in: How to find keyword cannibalization in Google Search Console

Setup for: Amp

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.

Used in: Build a weekly SEO health report with Claude, Find the pages quietly losing organic traffic, before the rankings go

Setup for: Claude Code, opencode, Goose, Roo Code, n8n

historical_position_trend

Plot a query's position over the last N days to see whether you're trending up, down, or volatile.

Used in: How to find striking distance keywords in Google Search Console, How to find keyword cannibalization in Google Search Console, Google Search Console historical data: how to keep it past 16 months, Build a weekly SEO health report with Claude, Track keyword rankings in Google Search Console, past the 16-month limit, Find the pages quietly losing organic traffic, before the rankings go, Traffic changed: how to compare two Search Console periods and find out why

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.

Used in: How to find striking distance keywords in Google Search Console, Google Search Console historical data: how to keep it past 16 months, Build a weekly SEO health report with Claude, Track keyword rankings in Google Search Console, past the 16-month limit, Find the pages quietly losing organic traffic, before the rankings go, Traffic changed: how to compare two Search Console periods and find out why

Setup for: opencode, Goose, Kilo Code, Raycast, GitHub Copilot CLI, n8n, LibreChat

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.

search_analytics_archive

Query your full GSC history beyond the 16-month limit. Same dimensions and filters as the live API, but unlocked for long-term trend analysis.

Used in: Google Search Console historical data: how to keep it past 16 months, Track keyword rankings in Google Search Console, past the 16-month limit, Find the pages quietly losing organic traffic, before the rankings go

archive_status

Check archive coverage per site: earliest date, latest date, row count, last successful run.

Used in: Google Search Console historical data: how to keep it past 16 months, Track keyword rankings in Google Search Console, past the 16-month limit

Setup for: LM Studio

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.

Used in: Audit Core Web Vitals across your site with AI

Setup for: Claude Desktop, Cline, Google Antigravity, LibreChat

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.

Used in: Audit Core Web Vitals across your site with AI, Build a weekly SEO health report with Claude

Setup for: Goose, Kiro

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.

Used in: Bulk URL inspection in Google Search Console: diagnose indexing issues at scale

Setup for: Warp, Kiro

inspect_url

Single-URL deep dive: indexability, last crawl, canonical, mobile usability, structured data. The full URL Inspection API result.

Used in: Bulk URL inspection in Google Search Console: diagnose indexing issues at scale

Setup for: Cline, Google Antigravity, Roo Code

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.

Used in: Bulk URL inspection in Google Search Console: diagnose indexing issues at scale

Setup for: Warp, Amp, GitHub Copilot CLI

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.

Used in: GSC clicks vs GA4 sessions: why they differ and how to tie clicks to conversions, Audit Core Web Vitals across your site with AI, Google Search Console anonymized queries: measure the traffic you can't see, AI queries in Google Search Console: how to tell people, AI Mode and agents apart

Setup for: Claude Desktop, Cursor, Claude Code, Codex CLI (OpenAI), VS Code (GitHub Copilot), Gemini CLI (Google), Windsurf (Devin Desktop), Zed Editor, JetBrains IDEs, Continue (extension), Claude.ai (browser), Direct HTTP (curl, custom agents), LM Studio, ChatGPT, Raycast

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.

Used in: How to find striking distance keywords in Google Search Console, How to find keyword cannibalization in Google Search Console, Audit Core Web Vitals across your site with AI, Bulk URL inspection in Google Search Console: diagnose indexing issues at scale, Google Search Console anonymized queries: measure the traffic you can't see, Good position, no clicks: find the SERP features eating your CTR, Traffic changed: how to compare two Search Console periods and find out why, AI queries in Google Search Console: how to tell people, AI Mode and agents apart

get_search_by_page_query

Drill into a specific page to see which queries drive its traffic, impressions, and average position.

Used in: How to find keyword cannibalization in Google Search Console, GSC clicks vs GA4 sessions: why they differ and how to tie clicks to conversions, Google Search Console anonymized queries: measure the traffic you can't see, Find the pages quietly losing organic traffic, before the rankings go, AI queries in Google Search Console: how to tell people, AI Mode and agents apart

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.

Used in: GSC clicks vs GA4 sessions: why they differ and how to tie clicks to conversions

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.

Used in: AI queries in Google Search Console: how to tell people, AI Mode and agents apart

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.

Used in: GSC clicks vs GA4 sessions: why they differ and how to tie clicks to conversions, Build a weekly SEO health report with Claude

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.

Used in: Traffic changed: how to compare two Search Console periods and find out why

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.

Used in: GSC clicks vs GA4 sessions: why they differ and how to tie clicks to conversions

Setup for: ChatGPT

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 AI Overview, featured snippet, map pack and People Also Ask.

Used in: Good position, no clicks: find the SERP features eating your CTR

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.

Used in: Good position, no clicks: find the SERP features eating your CTR

serp_features_audit

Check up to 25 queries at once for click-eating SERP features. Explains why CTR is low at a good position: usually an AI Overview, featured snippet or map pack above you.

Used in: Good position, no clicks: find the SERP features eating your CTR

Setup for: Kilo Code

Manage sites & sitemaps

5 tools

List your verified properties, audit sitemap health, find duplicate property registrations that split your reporting.

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.

Used in: Traffic changed: how to compare two Search Console periods and find out why

Ready to plug these into your AI client?

One token, hosted MCP, free. Setup is two clicks plus a paste.

Connect your Google account