Screpy SEO MCP

- Project and crawl overview— Ask for a project’s latest crawl health, on-page context, and issue counts viacrawl_summaryandproject_overview.
- URL-level investigation— Drill into a specific crawl URL withexact_page_details, or trace links and images back to their source pages.
- Crawl comparison— Compare completed crawls to see what changed in health indicators and issue counts over time.
- Quick Wins prioritization— Pull prioritized Search Console opportunities by project, category, and reporting range to scope next actions.
- Performance and uptime checks— Review available Core Web Vitals results and recent uptime incidents alongside crawl findings.
- Guarded high-impact actions— Start a crawl or update project settings only after explicit user confirmation, per the documented workflow.

Screpy SEO MCP connects compatible AI assistants to your authenticated Screpy account through the Model Context Protocol. Investigate projects, crawl issues, pages, opportunities, Core Web Vitals, and uptime without moving data between disconnected tools.

Screpy SEO MCP is a Model Context Protocol server that gives compatible AI assistants controlled access to a member’s Screpy projects and SEO workflows. It combines project context, crawl results, on-page data, Quick Wins, Core Web Vitals, and uptime information so an assistant can investigate a website using the same structured data available in Screpy.

- Screpy SEO MCP connects compatible AI assistants to the authenticated Screpy account through OAuth 2.0 and the standard Model Context Protocol.
- Screpy SEO MCP documents guided AI-assisted SEO workflows with ChatGPT, Claude, Perplexity, Gemini, Cursor, and GitHub Copilot.
- Screpy SEO MCP identifies Codex, Zed, Continue, Cline, Windsurf, and JetBrains AI Assistant as popular MCP clients; each connection depends on the deployed client supporting Screpy’s remote transport and OAuth flow.
- Screpy SEO MCP lists the projects available to the connected member and rechecks project access on every tool call.
- Screpy SEO MCP returns account context and plan-usage information so an assistant can understand the available Screpy workspace before investigating a project.

- Screpy SEO MCP returns a project overview with the latest completed crawl and on-page context for the selected website.
- Screpy SEO MCP lists crawls, reports crawl status, compares completed crawls, and returns crawl-level health indicators and issue counts.
- Screpy SEO MCP lists crawl pages and returns detailed data for an exact URL in a selected crawl.
- Screpy SEO MCP lists links and images, then traces their source pages so technical findings can be investigated in context.

- Screpy SEO MCP returns prioritised Quick Wins from existing Search Console opportunities for a selected project and reporting range.
- Screpy SEO MCP returns available Core Web Vitals results for performance analysis without mixing them with crawl page records.
- Screpy SEO MCP returns uptime status and recent incidents so availability problems can be included in the same SEO investigation.
- Screpy SEO MCP can start a crawl or change project settings only when the user explicitly confirms the requested high-impact action.

Bring Screpy into the AI workflow you already use.

Connect a compatible assistant to Screpy through the standard Model Context Protocol, then let it work from the project context and SEO data your account can access.

- Connect the authenticated Screpy account through OAuth 2.0
- Start with account context, plan usage, and the projects available to the member
- Keep each request scoped to the selected project and its allowed data
- Use the same Screpy context from AI conversations and development workflows

Give me a weekly SEO summary for this project.

I grouped the project signals into visibility, technical health, and content work so the weekly brief is ready to review.

Turn the three highest-impact findings into a practical plan.

I prioritized the three strongest findings by impact and added the affected pages with a practical next action for each.

Move from crawl health to the exact URL behind an issue.

Ask an assistant to inspect a completed crawl, identify the affected pages, and follow links or images back to their source context instead of relying on a generic summary alone.

- List completed crawls and check whether a current crawl is ready to investigate
- Review crawl-level health indicators, issue counts, and changes between completed crawls
- Filter the page inventory, then retrieve detailed data for one exact crawl URL
- Trace link and image findings to the pages where they appear

Investigate the URLs behind the crawl health decline.

I narrowed the health decline to the affected URLs and linked each one to its source page, link, or image context.

The broad health signal is now a URL-level investigation with clear technical evidence.

Turn Search Console opportunities into a focused next step.

Bring existing Quick Wins into an AI conversation with the affected project, category, and reporting range, then use the surrounding crawl and page context to investigate what deserves attention.

- Retrieve prioritised Search Console opportunities from the selected project
- Review striking-distance, click-through, content, crawl, and other available Quick Win categories
- Compare project and crawl context before turning an opportunity into work
- Keep the assistant grounded in the URLs, queries, and reporting range behind the recommendation

Turn the latest Quick Wins into two scoped tasks for this week.

I pulled the selected project, opportunity category, and reporting range into an impact-ranked action list.

Exclude marginal issues and keep the plan ready for this sprint.

The final plan keeps only the opportunities supported by the surrounding crawl and page context.

Include performance and uptime in every technical conversation.

SEO work does not stop at crawl data. Screpy SEO MCP also exposes available Core Web Vitals results and recent uptime incidents so an assistant can connect technical health with the next investigation.

- Review available Core Web Vitals results for the selected project
- Check uptime status and recent incidents before diagnosing a traffic or crawl problem
- Use project overview and completed-crawl context alongside health signals
- Keep performance, availability, and on-page findings in one scoped SEO workflow

Include speed regressions and uptime incidents in this technical SEO review.

I added available Core Web Vitals results and recent uptime incidents to the technical diagnosis.

Identify the next checks after the incident.

Next, verify the affected pages with a crawl or performance check and confirm the incident is resolved.

Screpy SEO MCP exposes the connected member’s project, crawl, on-page, opportunity, performance, and uptime workflows as structured tools for compatible AI assistants.

Connect a compatible AI client to the authenticated Screpy account through the SEO MCP OAuth flow.

Return the member’s available project count and product access context before an assistant starts an SEO investigation.

Return current plan-usage context so an assistant can understand the available account capacity and limits.

List the Screpy projects available to the connected member as the starting point for project-scoped SEO work.

Return high-level SEO and crawl context for one project, including the latest completed crawl and on-page overview.

Compare selected Screpy projects when an assistant needs to review website-level SEO context side by side.

Create a Screpy project when the user explicitly asks the assistant to add a new website workspace.

Update project settings only after the user explicitly confirms the requested high-impact change.

Delete a project only after the user explicitly confirms that exact destructive action.

List a project’s crawls and use their crawl UIDs to select the exact crawl for follow-up analysis.

Check whether a selected crawl is still running, completed, or ready for the next investigation step.

Start a new crawl only when the user explicitly confirms the selected project and crawl action.

Return totals, health indicators, and issue counts from one completed crawl for technical SEO review.

Compare completed crawls to investigate what changed in website health and technical findings over time.

Return the project’s on-page audit context before drilling down into an individual crawl page.

List crawl pages with structured filters so an assistant can narrow technical SEO analysis to relevant URLs.

Return detailed crawl data for one exact URL in a selected crawl when a finding requires page-level evidence.

Return prioritised existing Search Console opportunities by project, category, reporting range, and cursor.

List discovered links from a selected crawl and filter the results during internal-link and crawl-path investigations.

Return the pages that contain a selected link so an assistant can trace a link finding to its source context.

List discovered images from a selected crawl for image SEO, delivery, and page-quality investigation.

Return the pages that contain a selected image so image findings can be investigated in their page context.

Return available Core Web Vitals results for project-level performance analysis without using crawl page data.

Return uptime status and recent incidents so availability is part of the technical SEO investigation.

ChatGPT, Claude, Perplexity, Gemini, Cursor, and GitHub Copilot are the AI clients currently documented in Screpy’s guided MCP workflow. Codex, Zed, Continue, Cline, Windsurf, and JetBrains AI Assistant are popular MCP clients for SEO and development work; connect them when the deployed client supports Screpy’s remote transport and OAuth flow.

Use ChatGPT with Screpy SEO MCP to turn project-scoped crawls, page findings, Quick Wins, Core Web Vitals, and uptime data into clear SEO summaries and next-step plans. Keep the discussion tied to the exact Screpy project instead of manually copying dashboard exports.

Use Codex with Screpy SEO MCP when an SEO investigation needs to become a code-level change. Give Codex project-scoped crawl, URL, and monitoring context before it plans a fix for a template, redirect, metadata rule, or release regression.

Use Claude to investigate technical SEO issues with the crawl, URL, link, and image context stored in Screpy. Claude can help turn completed-crawl findings and ranking opportunities into a prioritised implementation brief for the right pages.

Connect Perplexity to Screpy SEO MCP when research needs the website context behind a question. Bring completed-crawl data, page-level findings, and existing opportunities into an investigation before deciding what to verify or fix.

Use Gemini with Screpy MCP to review authenticated project data alongside your SEO workflow. Ask Gemini to examine crawl health, page details, Quick Wins, Core Web Vitals, and uptime information without losing the project scope behind each result.

Use Cursor with Screpy SEO MCP while working in the codebase that affects your website. Investigate an affected URL, trace a crawl finding to its source context, and turn the result into a focused technical change instead of a generic SEO ticket.

Bring Screpy SEO context into GitHub Copilot for release, migration, and template work. Review crawl issues, page-level signals, and monitoring context while planning code changes that can affect indexability, performance, or availability.

Use Zed with Screpy SEO MCP when technical SEO work happens beside the code that serves the website. Zed supports remote MCP servers and standard OAuth, allowing developers to bring project-scoped crawl and monitoring context into an agent session before changing a template, route, or deployment setting.

Use Continue in agent mode with Screpy SEO MCP to connect remote technical SEO data to editor-based planning and implementation. Continue supports HTTP-based MCP transports, making it useful for teams that want crawl findings, affected URLs, and SEO priorities available while they work through a change.

Use Cline’s MCP configuration to give an agent the SEO context behind a development task. Connect a compatible Screpy remote MCP setup before asking Cline to investigate a broken URL, a crawl regression, or the page-level signals affected by a code change.

Use Windsurf’s remote MCP server configuration when SEO investigations need to follow the development workflow. Teams can keep Screpy project and crawl context close to the code editor, then verify the client’s available authentication flow before rolling a connection out across the team.

Use JetBrains AI Assistant with configured MCP tools when SEO work takes place in IntelliJ-based projects. Bring Screpy’s URL-level findings and technical monitoring context into the IDE so developers can assess the search impact of backend, frontend, or template changes before release.

Follow the MCP documentation to configure a compatible AI client, authenticate securely, and start using Screpy workflows.

Learn how Screpy SEO MCP connects compatible AI assistants to project-scoped SEO data and workflows.

An SEO MCP server makes SEO data and workflows available to compatible AI assistants through the Model Context Protocol. Screpy SEO MCP connects an authenticated Screpy account to that workflow so an assistant can work with the projects and tools the account can access.

Which AI assistants can connect to Screpy SEO MCP?

Screpy positions SEO MCP for AI-assisted workflows with ChatGPT, Claude, Perplexity, Gemini, Cursor, and GitHub Copilot. A client must support the Model Context Protocol and complete the Screpy OAuth connection flow.

What SEO data can Screpy SEO MCP access?

Screpy SEO MCP currently exposes account and project context, crawls, completed-crawl summaries and comparisons, on-page overview and page details, links, images, existing Quick Wins, Core Web Vitals, and uptime status. Every request remains scoped to projects available to the connected member.

How does Screpy SEO MCP protect project access?