Developers
Automate Digispot with the MCP server — query crawl data, trigger crawls, and wire SEO findings into AI agents and coding assistants.
Digispot exposes its crawl data programmatically through the MCP server. AI agents and coding assistants query audits, start crawls, and read findings without copy-paste.
MCP is the supported programmatic interface today. The desktop Spider and the Cloud Platform each run their own server.
MCP server
The MCP server lets Claude Code, Cursor, Windsurf, and any other MCP-compatible client work directly against your crawl data. An agent can answer questions about a site, pull the top issues from a finished audit, and generate fixes grounded in real findings.
It comes in two forms:
- Desktop Spider — a local stdio server, bound per project, with 64 project-scoped tools. The agent talks straight to the on-machine crawl database, so nothing leaves the machine.
- Cloud Platform — an HTTP server managed with keys created in Settings. It reaches cloud crawls and reporting, which suits shared team projects.
See MCP server for setup and the tool reference.
Which server to use
| Goal | Use |
|---|---|
| Query crawl data that stays on your machine | Desktop Spider |
| Have Claude Code generate fixes from real audit data | Desktop Spider |
| Reach audits shared across a team | Cloud Platform |
| Work on client sites under NDA | Desktop Spider |
Keys and connections
Cloud MCP keys are created and revoked in the Cloud Platform under Keys & connections. The same screen manages Chrome-extension keys and Spider desktop licenses. See Keys & connections.