seo_run_audit
Queue an audit
Your AI passes a URL; the same pipeline the website uses crawls the site and scores it. Returns a slug to poll.
MCP · Pro & Agency
Connect DeepSEOAnalysis to any AI client with the Model Context Protocol. Your AI queues real SEO + AI-visibility audits and pulls the scored results straight into the conversation — no copy-paste, no dashboards.
How it works
The core loop is three tools. There's also seo_audit_page for a quick single-page check, plus seo_list_monitored_sites, seo_rank_history, and seo_ai_visibility_history to read your Pro/Agency monitoring data.
seo_run_audit
Your AI passes a URL; the same pipeline the website uses crawls the site and scores it. Returns a slug to poll.
seo_get_audit
Poll until done (polls are free), then pull a compact summary, a paginated issue list, or the full report — overall, per-category, and AI-visibility scores.
seo_list_audits
List the account's recent audits so your AI can compare runs or pick up where a previous conversation left off.
Connect in a minute
Endpoint: https://deepseoanalysis.com/api/mcp — authenticate with a bearer API key.
Claude Desktop
{
"mcpServers": {
"deepseoanalysis": {
"command": "npx",
"args": [
"mcp-remote",
"https://deepseoanalysis.com/api/mcp",
"--header",
"Authorization: Bearer dsa_live_YOUR_KEY"
]
}
}
}Cursor
{
"mcpServers": {
"deepseoanalysis": {
"url": "https://deepseoanalysis.com/api/mcp",
"headers": { "Authorization": "Bearer dsa_live_YOUR_KEY" }
}
}
}VS Code
{
"servers": {
"deepseoanalysis": {
"type": "http",
"url": "https://deepseoanalysis.com/api/mcp",
"headers": { "Authorization": "Bearer dsa_live_YOUR_KEY" }
}
}
}Claude.ai & ChatGPT connectors
Web clients that add a custom connector by URL use OAuth rather than a pasted key. Point them at https://deepseoanalysis.com/api/mcp and sign in when prompted. Until OAuth is enabled, connect Claude Desktop, Cursor, or VS Code with a bearer key as shown above.
Plans
Pro unlocks the MCP server for AI clients. Agency adds the raw REST API and white-label reporting on top.
FAQ
It is a remote Model Context Protocol (MCP) server that exposes the DeepSEOAnalysis audit engine as tools an AI client can call. From Claude, Cursor, or any MCP client, your AI can queue an SEO + AI-visibility audit for a URL and read back the scored results — overall score, per-category scores, an AI-visibility (GEO) score, and prioritized issues.
Any MCP client. Cursor and other IDE clients support the remote endpoint with a bearer header natively. Claude Desktop connects through the mcp-remote bridge for header auth. The endpoint is a stateless Streamable HTTP transport at https://deepseoanalysis.com/api/mcp.
Seven tools: seo_run_audit (queue a full-site audit), seo_audit_page (quick single-page check), seo_get_audit (poll status, then fetch a summary, paginated issues, or the full report), seo_list_audits (recent audits), seo_list_monitored_sites (monitored sites with latest scores), seo_rank_history (keyword ranking history), and seo_ai_visibility_history (weekly AI-visibility trend). The last three read data from Pro/Agency monitoring.
Yes. The server ships MCP prompts — one-click guided workflows your client can surface: full_seo_review (audit a whole site and walk the fixes), quick_page_check (fast single-page review), and ai_visibility_review (trend review of your monitoring data). They chain the tools for you.
With a DeepSEOAnalysis API key (dsa_live_...) sent as an Authorization: Bearer header. Create a key on your account’s API & MCP page. Keys are stored as scrypt hashes and are burst-limited to 60 requests per minute.
MCP is included on both Pro and Agency. The raw REST API (api/v1) remains Agency-only. Free accounts can read the docs but keys only work once the account has MCP or API entitlement.
No. Status polls and completed-report reads only count against the per-minute burst limit. Monthly quota is spent once when you start an audit, so retrying or paging through results is free.