SEO MCP Documentation

Connect an AI agent to Screpy SEO data, then investigate crawls, rankings, AI visibility, and technical SEO with checkable evidence.

SEO MCP is a Model Context Protocol server for SEO work. It lets compatible AI agents ask questions about data in your Screpy account: projects, crawls, pages, links, images, uptime, Core Web Vitals, Rank Tracker, and AI Visibility.

Instead of pasting exports into a chat, you can ask a focused question. The agent discovers the correct project and crawl, retrieves only the relevant records, and explains its findings with the underlying evidence.

What SEO MCP is—and is not

SEO MCP is the connection between an AI agent and real SEO data. It does not replace a crawler, guarantee rankings, or give an agent unrestricted access to your account.

Start here

Connect your AI client

Authorize a compatible MCP client with OAuth and PKCE.

Run your first SEO audit

Move from a plain-language question to verified crawl findings.

Explore SEO workflows

Choose a playbook for crawls, rankings, AI visibility, and technical fixes.

Browse the tools

Find the right read or change tool for each dataset.

What can SEO MCP analyze?

Area	Questions you can answer	Main tools
Projects	What sites can I access? Which project needs attention?	`list_projects`, `get_project_overview`, `compare_projects`
Crawls	What changed between releases? Is a crawl complete?	`list_crawls`, `get_crawl_summary`, `compare_crawls`
Pages	Which pages have 4xx responses, missing titles, or canonical problems?	`list_pages`, `get_page_details`
Links	Where do broken links appear? Which pages link to a target?	`list_links`, `get_link_sources`
Images	Which images are large, broken, or missing alt text?	`list_images`, `get_image_sources`
Experience	Which pages have weak Core Web Vitals or uptime signals?	`list_core_web_vitals`, `get_uptime_summary`
Rankings	How did tracked keywords change across stored analyses and devices?	`get_rank_tracker_overview`, `list_rank_tracker_keywords`, `get_rank_tracker_keyword`
AI visibility	Which monitored prompts mention the brand, and which answers support that observation?	`get_ai_visibility_overview`, `list_ai_visibility_prompts`, `get_ai_visibility_answer`
Opportunities	Which issues or search signals have a concrete next step?	`list_quick_wins`

The safe default workflow

Call list_projects and select a valid project UID.
For crawl-level work, call list_crawls and select a valid crawl UID. Ranking and AI visibility tools use their own stored analyses.
Use a summary tool to understand scope.
Use filtered record tools to verify the finding.
Explain impact, evidence, and the next action separately.
Change state only when the user explicitly requests it.

This order matters. It prevents guessed identifiers, reduces unnecessary data retrieval, and makes the final answer easier to audit.

How these docs are written

Every workflow begins with the direct answer, then expands into requirements, tool sequence, prompt examples, validation, and limitations. The content reflects the current SEO MCP server surface and is maintained by the Screpy product team.

Last reviewed: September 24, 2026.

Next step

Go to Connect your AI client to add the SEO MCP endpoint, or open the prompt library if you are already connected.