SEO MCP Server for AI Assistants

Read the authenticated member’s product access, available project count, current usage, and remaining allowance before a workflow consumes capacity.

List accessible projects, open one project’s high-level SEO context, or compare summary metrics across two to five available projects.

Create a project, update allowed settings, or delete a selected project only through the dedicated tool and the required user-intent or confirmation flow.

List crawl runs for one project, select the exact crawl UID, and check progress or state before treating results as complete.

Start a new crawl only for the selected project and only after explicit confirmation because the action may consume plan allowance.

Read crawl totals, health indicators, issue counts, and on-page metrics, then compare two completed crawls to inspect metric changes.

Filter pages within one crawl and retrieve detailed crawl data for one exact URL after the relevant record has been identified.

List link records with structured filters and trace one destination back to the crawl pages that contain it.

List image records from one crawl and return the pages that reference a selected image for contextual investigation.

Retrieve existing project Quick Wins by supported category, reporting range, and cursor without presenting them as a full Search Console replacement.

Read available field-performance results, current uptime status, and recent incidents as separate health signals for the selected project.

Read supported countries, languages, devices, frequencies, segment-rule options, overview metrics, visibility, distribution, and plan usage.

Filter and paginate tracked keywords, then open one keyword with up to 30 stored analyses and the results from the selected or latest analysis.

Add or delete up to 100 project-scoped keyword IDs per action only with explicit confirmation, including the requested device variants.

List segments with SQL-backed match counts and unmatched keywords, then preview proposed rules, overlap, average position, and example URLs without saving.

Create, update, or delete project-scoped segments only when the user explicitly asks to save or remove the exact rules.

Read stored overview, mention, answer, citation, prompt, source, and activity records without triggering a new analysis.

Add 1 to 20 prompts for one market only after explicit user intent, and require confirmation before soft-deleting a project prompt.

“List my projects, select [site], compare the two latest completed crawls, and show the metrics that changed. Do not start a new crawl.”

“Open the latest completed crawl for [site], find [URL], explain its page, link, and image evidence, and separate facts from hypotheses.”

“Show visibility, falling keywords, and affected ranking URLs for [site]. Do not add, delete, or reanalyze keywords.”

“Preview a Rank Tracker segment for [rules], show matches and overlap with existing segments, and do not save it.”

“Summarize stored AI Visibility for [site], then show the prompts, answers, citations, and sources behind the largest change. Do not add or delete prompts.”

The connection uses browser-based OAuth, and every tool call checks access to the selected project instead of exposing unrelated Screpy data.

Project, crawl, page, link, image, Quick Wins, Rank Tracker, AI Visibility, Core Web Vitals, and uptime tools can collect evidence without changing project state.

Project, crawl, keyword, segment, and AI Visibility prompt changes use dedicated tools. The request must clearly describe the change instead of hiding it inside a broad analysis prompt.

Capacity-consuming or destructive actions require confirmation. The connected AI client should also let you inspect and deny tool invocations.