SEOcrawl AI MCP Server

SEO + GEO MCP: live Google Search Console data, keyword and page analysis, site audit and SEO tasks — 21 tools.

Documentation

https://mcp.seocrawl.ai

Google Search Console MCP Server

The Google Search Console MCP server with SEO + GEO superpowers: your GSC data and SEO tasks inside your AI assistant.

38 MCP tools, one connector. Pull live Google Search Console and Google Analytics 4 data, drill into any keyword or page, slice it by your own tags, audit your AI visibility across ChatGPT, Claude, Gemini and Perplexity, measure the traffic those engines send you, surface technical issues from your site audit, and create or close SEO tasks — all from a chat. Built on the open Model Context Protocol (MCP), so it works out of the box with Claude, ChatGPT, Cursor and Claude Code. Part of SEOcrawl AI's SEO + GEO (AI visibility) platform.

Works with

Watch demo · 4:01

Google Search Console MCP Use Cases

Fourteen real conversations you can have today — SEO and GEO (AI visibility) alike. Each one maps to the actual MCP tools listed below — no hand-waving, no copy-paste, no exports.

get_gsc_summary · compare_date_ranges

Search Console recap, in chat

Get your weekly Search Console recap in one chat — the same data you'd open the SEO Dashboard for. Skip the manual export: ask for last 28 days vs the 28 before, and your assistant pulls the four headline metrics with diff and change_pct already calculated.

Example prompt

“Compare seocrawl.ai performance for the last 28 days vs the previous 28 — clicks, impressions, CTR and average position.”

get_top_pages · get_page_detail

Growing and Declining Pages

See which pages move the needle, and which just dropped. Ask for top pages with period-over-period and your assistant ranks them by clicks, flags the losers, and offers to fetch the daily breakdown for any URL you call out.

Example prompt

“Top 5 pages by clicks on seocrawl.ai this last 28 days, and which ones dropped vs the previous 28.”

get_keyword_detail

Keyword Deep Dive

Zoom into a single keyword’s day-by-day trend. Once you’ve spotted a query worth investigating, pull its daily time series — useful for catching the exact day a position shift happened or correlating with a Google update.

Example prompt

“Show me the daily trend for 'geo optimization' on seocrawl.ai for the last 28 days — clicks, impressions and position.”

create_task

From Insight to Action

Spin up an SEO task without leaving the chat. When the data points to action, your assistant creates it right there in your Task Manager — title, description, assignee, priority (1–5) and taskbox, all in one call.

Example prompt

“Create a task to update the meta title on /blog/technical-seo. Priority 2, assigned to me, description should mention the -38% click drop.”

list_tasks · update_task · add_comment

One-Chat Task Triage

Triage your open SEO tasks in a single chain. Your assistant lists what’s open, changes status on any one of them, and appends a comment with what was done — three MCP calls, one natural-language request.

Example prompt

“List my open tasks on seocrawl.ai, mark 'Update meta title on /blog/technical-seo' as Done, and add a comment with the new title.”

list_winners_losers

Biggest movers, ranked

See the gainers and decliners between two periods without drilling each one. Ask for the biggest movers and your assistant returns keywords (or pages) sorted by how far they climbed or dropped — deltas pre-computed, so you skip opening each item.

Example prompt

“What are the biggest keyword movers on seocrawl.ai — last 28 days vs the previous 28? Show the top gainers and the biggest decliners.”

list_pages_for_keyword

Spot keyword cannibalization

Find every page competing for the same query. Give your assistant a keyword and it lists the pages on your site that earn its clicks and impressions, ranked — so you can see when two URLs split the same intent and pick a canonical one.

Example prompt

“Which pages on seocrawl.ai rank for 'seo dashboard'? I want to check whether more than one URL is competing for it.”

add_annotation · list_annotations

Mark the moment, read it back

Pin context to your Search Console timeline. When something changes — a migration, a Google update, a big publish — your assistant records a dated annotation, then reads the timeline back so the ‘why’ behind a traffic shift is never lost.

Example prompt

“Add an annotation on seocrawl.ai for today: 'Shipped new /mcp landing'. Then list the annotations from the last 3 months.”

page_explorer

Find the pages behind a technical issue

Turn your site audit into a question. Ask for pages with a missing canonical, no H1, a 404 status, or any audit check, and your assistant returns the exact URLs from your latest crawl — health score, error and warning counts included — so you go straight from issue to fix list without opening the dashboard.

Example prompt

“On seocrawl.ai, list pages from the last crawl that are missing an H1 or return a 404 — worst health first.”

list_prompts

Audit your AI visibility coverage

See exactly what your AI Tracker is monitoring across ChatGPT, Claude, Gemini and Perplexity. Ask which prompts a property tracks and your assistant lists each one with the engines it runs against and how many times it ran in the window — so you can audit your GEO coverage and spot gaps without opening the dashboard.

Example prompt

“List the AI Tracker prompts seocrawl.ai is tracking — show which engines each runs on and how many times they ran in the last 28 days.”

create_tag_rule · get_top_keywords

Slice your data by your own taxonomy

Group keywords and pages your way, then read Search Console through that lens. Ask your assistant to auto-tag everything matching a pattern — say every query containing ‘geo’ — and it creates a rule that tags current and future matches, then pulls your top keywords filtered to that tag. By product line, by intent, brand vs non-brand — your taxonomy, your reports.

Example prompt

“Tag every keyword on seocrawl.ai that contains 'geo' as 'GEO', then show me the top keywords with that tag over the last 28 days.”

get_ga4_summary · compare_ga4_date_ranges

Your GA4 recap, next to your GSC data

Google Analytics 4 headline metrics in the same conversation as Search Console — no tab-switching, no Looker Studio detour. Ask for any window and your assistant pulls sessions, users, conversions and engagement rate with the delta vs the previous period already calculated — or compares any two windows side by side.

Example prompt

“Give me the GA4 summary for seocrawl.ai over the last 28 days — sessions, users, conversions and engagement rate, vs the previous 28.”

get_ga4_traffic_by_source

See where your traffic actually comes from

One question, your full acquisition mix. Your assistant breaks GA4 sessions down by channel or by source/medium — each row with its share of the period's total — so you see at a glance how much search, referrals, social and paid actually drive, without building a single report.

Example prompt

“Break down seocrawl.ai traffic for the last 28 days by channel — sessions and share of total.”

get_ga4_ai_referrers

Measure your AI traffic, engine by engine

The missing half of GEO: not just where you're mentioned, but the traffic it sends. Your assistant reads AI/LLM referral sessions straight from your GA4 source/medium — ChatGPT, Perplexity, Gemini, Claude, Copilot — with key events and session duration per engine, no manual regex filters. Pair it with your AI Tracker prompts to connect visibility to visits.

Example prompt

“How much AI traffic did seocrawl.ai get in the last 28 days? Break it down by engine — sessions, key events and change vs the previous period.”

38 MCP tools for SEO & GEO

38 SEO MCP tools across 12 groups. Names below match the real MCP tool IDs so you (or your assistant) can call them directly.

Properties

1 tool

Discover which Search Console properties (projects) are connected to the account before any other query.

list_properties

List every GSC property the authenticated user can access. Returns the property ID (UUID) and URL (sc-domain:…) you pass to all other tools.

Performance overview

3 tools

High-level Search Console performance for any property, plus apples-to-apples comparison between two date windows.

get_gsc_summary

Clicks, impressions, CTR and average position for a property over a chosen window. Accepts presets (last_7_days, last_28_days, last_3_months, last_year) or absolute from/to dates. Also returns a branded_breakdown that splits clicks, impressions, CTR and position into branded vs non-branded — driven by the property's Brand tag.

compare_date_ranges

Compare two GSC windows side by side and get diff + change_pct for clicks, impressions, CTR and position. Period A can be a preset; Period B is absolute.

The biggest movers between two periods, with deltas pre-computed so your assistant skips drilling each item. Pick dimension=keywords or pages, a metric (clicks, impressions or position) and direction=up / down / both to get gainers, decliners or the largest swings either way. Period B defaults to the window immediately before Period A.

Keywords

3 tools

Find which queries actually drive traffic, then zoom into any single keyword's day-by-day trend.

get_top_keywords

Top keywords for a property ranked by clicks, impressions, CTR or position — with period-over-period comparison. Paginated via next_cursor. Filter by branded: true|false to split brand-driven queries from SEO-earned ones; the summary returns a branded_breakdown you can read in one shot.

Daily time series (clicks, impressions, CTR, position) for a single search query in a property. Same date-range options as the summary.

Given a single query, list the pages on your property that earn its clicks and impressions — ranked by clicks, impressions, CTR or position, with period-over-period deltas and next_cursor pagination. Handy for spotting keyword cannibalization or finding the canonical page for a term.

Pages

3 tools

See which URLs carry the traffic, where they lost ground, and pull a daily breakdown for any one of them.

get_top_pages

Top pages for a property ranked by clicks, impressions, CTR or position — every row returns clicks, impressions, CTR and position with period-over-period deltas. Paginated via next_cursor.

get_page_detail

Daily time series (clicks, impressions, CTR, position) for a single page URL in a property. Drop-in compatible with the summary's date-range syntax.

list_keywords_for_page

Given a page URL, list the search queries driving its clicks and impressions — ranked by your chosen metric, with period-over-period deltas and next_cursor pagination. The inverse of list_pages_for_keyword: start from a URL and see exactly which queries feed it.

Tasks

7 tools

The SEOcrawl Task Manager — fully wired into the MCP. Create work, edit it, comment on it, never leave the chat.

list_tasks

All tasks for a property. Filter by status (open / done), assignee, taskbox (column) or q (case-insensitive title search). Paginated via next_cursor.

list_taskboxes

The task board's columns (taskboxes) for a property: id, name, status (todo / in_progress / done) and order. Pass a returned taskbox id — or the status keyword — to create_task or update_task to move a task into that column.

get_task

Full detail for a single task. Accepts a UUID, a slug, or a full browser task URL (the property arg is optional when you pass a URL).

create_task

Create a task on a property with title (required) plus optional description, assignee, priority (1–5, default 3) and taskbox (defaults to the TO-DO column).

update_task

Partially update a task — any combination of title, description, assignee, priority, taskbox, or unassign:true to clear the owner.

add_comment

Append a comment to a task. Same flexible ticket reference (UUID / slug / URL) as get_task and update_task.

get_comments

List the comments on a task, including nested replies. Same flexible ticket reference (UUID / slug / URL) as get_task — the property arg is optional when you pass a URL.

Annotations

4 tools

Chart notes for any property — record what changed and when, then read the timeline back so context never gets lost next to your Search Console trends.

add_annotation

Create a chart note on a property for a given date (Y-m-d) with the note text — plus optional longer description, category and a linked task UUID. Added as a custom, site-wide note authored by you.

list_annotations

List a property's annotations within a date range, newest first. Use a preset (last_7_days, last_28_days, last_3_months, last_year) or absolute from/to dates, with optional substring search on the note text and pagination (limit capped at 200).

get_annotation

Full detail for a single annotation by its id — date, note, description, category, linked task, author and the property it belongs to. Use list_annotations to find the id.

delete_annotation

Delete a custom annotation by its id. Only your own custom notes can be removed — official or global notes are rejected. Returns the id with deleted: true.

Site Audit

1 tool

Query your latest site-audit crawl from chat — find the exact pages behind a technical issue without opening the dashboard.

page_explorer

Find crawled pages that match technical SEO criteria from your latest site audit. Filter by status_code (e.g. 404), no_canonical (missing canonical tag), missing_h1 (missing H1 heading) or check_title (any audit check shown in the UI, e.g. "Title Tag too short"). Sort by health, status_code, url or depth, paginated via next_cursor. Every row returns url, status_code, title, indexability, performance_score (health 0–100), last_crawled_at, count_errors and count_warnings — plus a check_description when a check filter is active.

AI Tracker

1 tool

Your AI Tracker (GEO / AI visibility) — see which prompts a property monitors across ChatGPT, Claude, Gemini and Perplexity, straight from chat.

list_prompts

List the AI Tracker (Brand Radar) prompts a property is tracking. Every row returns prompt_id, prompt_text, engines_tracked (the LLM engines the prompt runs against), last_run_at (ISO-8601, most recent run) and runs_in_range (engine executions inside the window). Scope runs_in_range with a preset (last_7_days, last_28_days, last_3_months, last_year) or absolute from/to dates — the full prompt list always comes back. Filter by engine (chatgpt/openai, claude/anthropic, gemini, perplexity) and page via limit (max 200) and next_cursor.

GA4 Web Analytics

5 tools

Google Analytics 4 in the same connector — sessions, conversions, traffic sources and the AI/LLM referral traffic behind your GEO work, straight from chat.

list_ga4_properties

List the GA4 properties connected to your projects. Each entry returns the project id and URL (either works as the property argument for the other GA4 tools), the underlying GA4 property ID and the connection date. Only projects with a connected GA4 property are returned.

get_ga4_summary

Sessions, users, new users, conversions, engagement rate and sessions per user for a property over a chosen window — presets (last_7_days, last_28_days, last_3_months, last_year) or absolute from/to dates. Every metric returns current, prev and delta vs the immediately preceding period.

compare_ga4_date_ranges

Compare two GA4 windows side by side — sessions, users, new users, conversions and engagement rate, with both values plus diff and change_pct per metric. Period A can be a preset; Period B is absolute. The GA4 twin of compare_date_ranges.

Sessions broken down by acquisition source. Pick dimension=source_medium (default) or channel for GA4's default channel grouping — rows come sorted by sessions, each with its share_pct of the period total, capped by limit (default 25, max 100).

AI/LLM referral traffic by engine — ChatGPT, Perplexity, Gemini, Claude, Copilot and more, detected from the GA4 session source/medium. Each engine returns sessions, key events and average session duration, with the change vs the previous period. Your GEO traffic, measured.

Tags

8 tools

Build a custom taxonomy over your keywords and pages, then slice Search Console by it. Create tags, assign them by hand or with auto-rules, and pass them to the tags filter on get_top_keywords, get_top_pages and list_winners_losers.

list_tags

List a property's keyword and page tags. Each tag returns tag_id, name, type (keyword|page), color, rule_count (auto-assignment rules) and member_count (keywords or pages currently carrying it). Pass tag names to the tags filter on get_top_keywords, get_top_pages and list_winners_losers.

create_tag

Create a tag on a property. type is keyword (tags keywords), url (tags pages) or both. Optional color is a hex string used by the SEOcrawl UI. Tag identity is name + type, so re-creating an existing tag just updates its color.

apply_tag

Manually apply a tag to specific keywords and/or pages, on top of any auto-rules. Pass keywords (exact strings) and/or urls (exact page URLs); at least one is required. The tag is created for the relevant type if it does not exist yet.

remove_tag

Remove a tag from specific keywords and/or pages — the inverse of apply_tag. Only unassigns the tag from those items; it does not delete the tag itself or touch auto-assignment rules.

delete_tag

Delete a tag entirely: unassign it from every keyword/page and remove the tag. type is keyword, url or both. The built-in Brand / Non-Brand tags cannot be deleted. Auto-rules targeting the tag are left intact — use delete_tag_rule for those.

list_tag_rules

List a property's auto-assignment rules — the patterns that tag keywords/pages automatically. Optionally filter by tag. Each rule returns rule_id, tag, field (keyword|url), country and its conditions (match + value).

create_tag_rule

Create an auto-assignment rule that tags every matching keyword or page — current and future. field is keyword or url; match is contains, not_contains, exact, starts_with, ends_with or regex (a safe RE2 pattern); value is the pattern. One rule per tag+field; tagging of existing items runs asynchronously.

delete_tag_rule

Delete an auto-assignment rule by its rule_id (from list_tag_rules). Stops future auto-tagging for that pattern; items already carrying the tag keep it (use remove_tag or delete_tag to unassign).

Web Fetch

1 tool

Inspect any live page mid-conversation — parsed SEO elements, clean markdown content and raw HTML, no crawl required.

fetch_url

Fetch a single live URL on demand (plain HTTP GET, no JavaScript) and get the response details back — final URL, status code, full redirect chain, response time and decoded page size — plus optional blocks: parsed SEO elements (title, meta description, meta robots, canonical, hreflang, headings, OG/Twitter tags, JSON-LD types, word count, link counts, images missing alt), the main content as clean markdown, and the raw HTML. Transport failures return structured errors (dns_error, timeout, blocked_url…). Free — it never burns MCP credits; rate-limited per user.

Platform health

1 tool

Check the connector itself before you build on it — one free call shows whether every surface is up right now.

health

Live status of the MCP backend per surface (GSC, GA4, Site Audit, AI Tracker, Tasks) and per data store, each reported as ok, degraded or down with last_check_at and a sample_error. Free and takes no arguments — poll it before a multi-step workflow so a broken endpoint is visible up front.

MCP clients: Claude, ChatGPT, Cursor & Claude Code

SEOcrawl AI MCP follows the open Model Context Protocol — any MCP-compatible client works. Here are the four most common setups today.

Claude

Connect SEOcrawl AI from Claude.ai and Claude Desktop. Ask for performance summaries, top pages or task triage and Claude calls the right MCP tool for you.

Setup

Settings → Connectors → Add custom connector

ChatGPT

Use SEOcrawl AI inside ChatGPT via the Apps connector. Mention @SEOcrawl in a chat to pull live Search Console data or open a task without leaving the conversation.

Setup

Settings → Apps → Advanced → Developer mode → Create

Cursor

Drop the SEOcrawl AI MCP into Cursor and pull live performance or task data while you're writing code, briefs or release notes.

Setup

Cursor Settings → Tools & MCP → Add new MCP server

Claude Code

Register SEOcrawl AI in Claude Code from your terminal. Every tool becomes a one-line CLI call inside your existing dev workflow.

Setup

claude mcp add --transport http seocrawl https://mcp.seocrawl.ai

SEOcrawl AI MCP — FAQ

What is MCP?

MCP (Model Context Protocol) is an open standard introduced by Anthropic in late 2024 that lets AI assistants like Claude and ChatGPT talk to external tools and data sources. Instead of copy-pasting reports into a chat, the assistant calls SEOcrawl AI directly and brings the data back. Full spec at modelcontextprotocol.io.

What is the SEOcrawl AI MCP?

It's a server that exposes 38 SEOcrawl AI tools — Search Console performance queries, keyword and page drill-downs, GA4 web analytics (sessions, traffic sources and AI/LLM referral traffic), custom tagging, AI Tracker (GEO) prompt coverage, site-audit page exploration, the full SEOcrawl task system, and chart annotations — as MCP tools your AI assistant can call. You ask in natural language; the assistant runs the right query against your account and brings the result back.

Is this a Google Search Console MCP server?

Yes — and more. Most Google Search Console MCP servers are bare connectors that need service accounts, OAuth setup or local installs. SEOcrawl AI's MCP gives you Search Console performance data out of the box (sign in with your SEOcrawl AI account, no Google Cloud setup), plus everything raw GSC can't do: side-by-side date comparisons, branded vs non-branded segmentation, custom tags, GA4 analytics, site-audit checks and SEO task management — 38 tools in one connector.

What does it actually do today?

Five families of work: (1) Search Console performance — clicks, impressions, CTR and position summaries plus side-by-side date comparisons; (2) Keyword and page analysis — top lists with period-over-period deltas, branded vs non-branded segmentation (driven by your property's Brand tag) and daily breakdowns for any single keyword or URL; (3) GA4 analytics — sessions, users, conversions, traffic by source or channel, and AI/LLM referral traffic per engine; (4) Site audit — find crawled pages by technical criteria (missing canonical, missing H1, status codes, or any audit check) straight from your latest crawl; (5) SEO tasks — list, create, update, comment on and close tasks inside your SEOcrawl projects. New tools (Brand Radar, backlinks) ship on a rolling basis — see the public roadmap for what's next.

Does the MCP help with GEO and AI visibility?

Yes — two GEO surfaces are live today. list_prompts shows which AI Tracker (Brand Radar) prompts a property monitors across ChatGPT, Claude, Gemini and Perplexity, and get_ga4_ai_referrers measures the AI/LLM referral traffic those engines actually send your site, straight from GA4. Deeper Brand Radar data (mentions, share of voice, cited pages) lives in the SEOcrawl AI dashboards and is next on the MCP roadmap. We update this page when new tools ship.

Which plans include MCP access? How are calls metered?

MCP access is included on every SEOcrawl AI plan — see the pricing page for the per-tier breakdown. Each plan ships with a monthly MCP credit pool — 3,000 (Starter), 10,000 (Growth), 30,000 (Pro), 100,000 (Agency) and Unlimited (Enterprise). Each MCP call burns 1–6 credits depending on the tool: light lookups (list_properties, get_task) cost 1, performance summaries and time-series cost 3, top-keyword / top-page calls cost 5, side-by-side date comparisons cost 6. A per-minute rate limit and a hard daily cap apply on every plan to protect the platform from runaway agents. Your account's project, click and LLM-credit limits still apply on top.

Which AI clients does it work with?

Claude (Claude.ai and Claude Desktop), ChatGPT (via the Apps connector), Cursor and Claude Code today. Any MCP-compliant client should work — the server uses the open MCP transport, with no client-specific code paths.

Does it use my real SEOcrawl AI data?

Yes. The MCP authenticates against your SEOcrawl AI account and reads the same Search Console properties and tasks you see in the app. We never share data across accounts.

How do I set it up?

Add the SEOcrawl AI MCP endpoint — https://mcp.seocrawl.ai — to your AI client's MCP/connector configuration. It's the same URL for everyone, with nothing to switch on in your account settings first. Sign in with your SEOcrawl AI account when your client prompts you, and most clients pick the 38 tools up automatically so you can start chatting in under a minute.