Developers
Automate Digispot with the MCP server and HTTP API — trigger crawls, pull findings, and wire SEO data into AI agents and CI pipelines.
Digispot exposes two programmatic interfaces. The MCP server is for AI agents and coding assistants; the HTTP API is for scripts, CI, and custom integrations.
MCP server
The MCP server lets Claude Code, Cursor, Windsurf, and any other MCP-compatible client query your crawl data, start crawls, and surface findings — all from a chat prompt or an agentic loop. No copy-paste required.
It comes in two forms:
- Desktop Spider — a local stdio server, bound per project, with 60+ tools. The agent talks directly to your on-machine crawl database.
- Cloud Platform — an HTTP server, managed via API keys in Settings, with cloud crawl and reporting access.
See MCP server for setup and reference.
HTTP API
The HTTP API is for triggering crawls and pulling results from your own code — CI pipelines, monitoring scripts, custom dashboards, or any tooling that cannot use MCP. It is available on the Cloud Platform with a key generated under Settings → API Keys.
See APIs for endpoint reference.
Which interface to use
| Goal | Use |
|---|---|
| Let an AI agent answer questions about your site's SEO | MCP server |
| Trigger a crawl from a pull request check | HTTP API |
| Pull findings into a custom dashboard | HTTP API |
| Have Claude Code generate fixes from real audit data | MCP server |
| Monitor a site on a schedule and alert on regressions | HTTP API |