Screpy MCP

Connect Screpy MCP to AI clients and investigate projects, crawls, and Google Search Console data.

Screpy MCP connects your Screpy account to AI assistants through the Model Context Protocol (MCP). Once connected, you can ask an AI client about your projects, crawls, technical SEO issues, Google Search Console, Rank Tracker, Core Web Vitals, uptime, and account usage without switching between dashboards.

You do not need to understand MCP or create an API key to get started. Choose your AI client, connect the Screpy MCP server, and approve the secure sign-in request. The AI client guides show the exact setup path for each supported client.

Screpy MCP uses OAuth

Connect Screpy MCP in three steps

Choose your AI client

Pick the AI client you already use, such as ChatGPT, Claude, Codex, Cursor, VS Code, or Gemini CLI. It must support remote HTTP MCP servers and browser-based OAuth sign-in.

Add the Screpy MCP server

Add this server URL in your client's MCP or connector settings:

https://mcp.screpy.com

Use the client-specific guide below when you need the exact menu path or configuration snippet.

Complete the Screpy sign-in page in your browser, approve access, then ask your AI client: "List my Screpy projects." Seeing the expected projects confirms that the connection is ready.

What you can do with Screpy MCP

Ask your AI assistant to use your Screpy data for practical SEO work, including:

Finding the most urgent Quick Wins from a completed crawl.
Explaining broken pages, redirect chains, missing metadata, or image issues.
Reviewing Core Web Vitals and uptime status.
Reviewing Rank Tracker visibility, keyword movement, stored results, and URL segments.
Filtering connected Search Console performance by query, page, country, device, or search appearance, and comparing date ranges.
Inspecting one URL's indexed status and reading the latest existing Index Status audit.
Adding or deleting tracked keywords and managing Rank Tracker segments when you explicitly request the change.
Comparing crawl progress across projects.
Starting a crawl only when you explicitly ask for it.

Screpy MCP returns only projects you own or that have been shared with your account. Sensitive actions still require your explicit intent, and high-impact actions ask for confirmation.

Rank Tracker keyword additions consume plan capacity and require confirmation. Keyword and segment deletion also require confirmation. Screpy MCP does not export Rank Tracker data, run live searches, or manually reanalyze an existing keyword; new keywords and scheduled updates use the normal analysis workflow.

Investigate Search Console data

First ask your AI client to list your projects and check the Search Console connection for the selected project. The seven read-only tools then use that project's selected Search Console property:

Tool	What it returns
`get_search_console_connection`	Connection and selected property status.
`get_search_console_overview`	Clicks, impressions, CTR, average position, and a daily trend; the `24h` preset uses an hourly trend.
`query_search_console_performance`	Filtered performance rows by up to three dimensions, with a cursor for the next page.
`compare_search_console_periods`	Totals for two periods on the same property, with optional top-row changes by one dimension.
`inspect_search_console_url`	Google's indexed view of one URL within the selected property.
`get_index_status_audit`	The latest existing Screpy Index Status audit and its progress.
`list_index_status_urls`	Inspected URLs from that latest audit, with index status, coverage, URL filters, and pagination.

Performance tools support 24h, 7d, 28d, 3m, 6m, 12m, and 16m presets or custom start and end dates. You can combine up to four query, page, country, device, or search-appearance filters with equals, not-equals, contains, not-contains, or regular-expression matching. For example, filter by one page and group by query to see its search terms; filter by a query and group by page to see its landing pages. The 24h preset covers yesterday and today in Pacific time, so its totals are not an exact rolling 24-hour window.

Search Console may omit lower-volume rows, and recent data can change. The tools distinguish an empty result from a disconnected account, missing property, exhausted quota, or temporary error. URL inspection reads Google's indexed version, uses a 24-hour cache and inspection quota, and does not run a live URL test or request indexing. Index Status tools read the latest audit without starting a new one. See example Search Console prompts and the Search Console dashboard guide for the visual workflow.