SEO MCPSEO MCP vs REST API: Which Fits Your Workflow?
Choose Screpy SEO MCP for conversational investigation or the Screpy REST API for deterministic integrations and scheduled application workflows.
Screpy SEO MCP and the Screpy REST API offer different ways to use SEO data. Choose MCP when an AI client should discover tools, inspect project-scoped evidence, and answer a bounded question with you reviewing its calls. Choose the REST API when your application needs a predetermined request, response, retry, and storage flow. Use the dashboard when you want direct visual review.
Make the choice by the work
| Need | Better starting point | Why |
|---|---|---|
| Ask why a site's crawl health changed and inspect exact pages interactively | SEO MCP | The AI client can move from project discovery to the relevant read tools within one investigation. |
| Build a scheduled data pipeline or product integration with fixed inputs and outputs | REST API | Application code can own credentials, pagination, retries, storage, and deterministic behavior. |
| Review charts, adjust settings, and inspect a project directly | Screpy dashboard | A person can see the current account and project state before acting. |
| Change keywords, prompts, settings, or crawls from a conversation | SEO MCP only when the action is supported and explicitly requested | Dedicated write tools enforce their own plan, scope, and confirmation requirements. |
These are starting points, not equivalent feature lists. Confirm a particular operation in the current MCP tool reference and the Screpy API documentation before designing around it. An MCP connection uses the member's browser-based OAuth grant; a REST integration uses the API's own authentication and application contract. Do not paste an API credential into an MCP prompt.
Example decision
If an analyst asks, “Which newly broken internal links appear on important pages after this release?”, the broken-links workflow can discover the project and crawl, trace sources, and explain the evidence. If a product must run that same check every night and store every result in its database, define the API calls and failure handling in code instead of relying on an open-ended prompt.
MCP does not expose every dashboard or API capability. It does not provide a live SERP lookup, Rank Tracker export, or manual reanalysis of an existing keyword. Choose based on the exact task and verify the current surface. For the hosted endpoint and access model, see getting started and security and permissions.
Related documentation
Continue exploring SEO MCP
Audit Content for Search and AI Answers
Use SEO MCP technical evidence to audit whether content is crawlable, internally discoverable, machine-readable, and supported by clear page signals.
SEO MCP Security and Permissions
Learn how SEO MCP limits access with OAuth, scoped tokens, project authorization, rate limits, bounded filters, and explicit confirmation.