How do I install SEO Score API?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does SEO Score API need an API key?

The publisher lists these environment variables: SEO_SCORE_API_KEY.

What transport does SEO Score API use?

SEO Score API is reached over HTTP.

When was SEO Score API last checked?

Last checked 2026-11-11. SEO, GEO and ADA/WCAG audits, AI citation tracking and site crawls for AI assistants.

SEO Score API MCP server

SEO Score API — Model Context Protocol Server

Give Claude Desktop, Claude Code, Cursor, Windsurf, or any MCP-aware AI tool direct access to the SEO Score API: full audits, backlink data, monitoring, and history.

Quick start

npx -y seoscoreapi-mcp

Set your API key once and forget it:

export SEO_SCORE_API_KEY="ssa_your_key_here"

(Get a free key at https://seoscoreapi.com — no card required.)

Tools exposed

Tool	What it does	Plan
`audit`	Full SEO audit on a URL — score, grade, 80+ checks, AI readability, prioritized fixes. `include_core_web_vitals: true` adds measured LCP, INP and CLS (about 10 seconds slower, needs a key)	Free
`batch_audit`	Audit up to 10 URLs at once (`include_core_web_vitals` optional)	Starter ($5/mo)
`usage`	Current plan + monthly usage + remaining quota	Free
`report_url`	Public shareable HTML report for a domain	Free
`add_monitor`	Add a URL to scheduled re-audit + alerts	Starter
`list_monitors`	List monitored URLs	Starter
`history`	Time-series of past scores for a URL	Starter
`history_domains`	Every domain audited by this key with 30-day trend	Starter
`backlinks`	Observed backlinks for a domain (audit-fed graph; honest data caveat in every response)	Basic ($15/mo)
`deep_audit`	Deep Site Audit: 9 dimensions, thousands of catalog checks + up to 150 AI checks; waits for the result (`timeout_seconds`, default 600)	Pro ($39/mo), Ultra, or credits
`start_deep_audit`	Queue a Deep Site Audit and return its `job_id` at once (optional `webhook_url`)	same
`get_deep_audit`	Status of a Deep Site Audit job, with the `result` once completed	same
`deep_audit_usage`	Deep Site Audits used and remaining this month	same
`remove_monitor`	Remove a URL from score monitoring	Starter
`compare`	Structured diff across 2-5 URLs

Not exposed, on purpose

Report files (GET /audit/export): the PDF is binary and an MCP tool result is text. The audit tool returns the same data as JSON; use the REST API or the Python / Node SDK (audit_export / auditExport) for the file.
Turning auto-reload on. The API has no such endpoint for API keys: it authorizes charges, so it is set from the dashboard only. citation_auto_reload reads it.
Account actions (/signup, /verify, /upgrade, /rotate-key) and the public scoreboard opt-out.

Configuration

Env var	Default	Purpose
`SEO_SCORE_API_KEY`	(none)	Your API key
`SEO_SCORE_BASE_URL`	`https://seoscoreapi.com`	API host
`SEO_SCORE_DEEP_AUDIT_URL`	`SEO_SCORE_BASE_URL`	Deep Audit host (`POST /site-audit`, `GET /site-audit/{job_id}`, `GET /deep-audit/usage`). `SEO_SCORE_ENGINE_URL` is still read as a fallback; the legacy `https://engine.seoscoreapi.com` keeps working.

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "seoscoreapi": {
      "command": "npx",
      "args": ["-y", "seoscoreapi-mcp"],
      "env": {
        "SEO_SCORE_API_KEY": "ssa_your_key_here"
      }
    }
  }
}

Restart Claude Desktop. You'll see the SEO Score tools in the tool picker.

Claude Code

claude mcp add seoscoreapi -e SEO_SCORE_API_KEY=ssa_your_key_here -- npx -y seoscoreapi-mcp

Cursor

Open Cursor Settings → MCP Servers → Add a new server with the same JSON shape as Claude Desktop above.

Windsurf

Settings → Cascade → MCP Servers → paste the same configuration.

Any other MCP client

Run npx -y seoscoreapi-mcp as a stdio transport. The server speaks standard MCP and exposes all tools in the table above.

Example prompts

Once installed, talk to your AI assistant naturally:

"Audit https://stripe.com and tell me the top 3 things to fix."

"Run a batch audit on stripe.com, square.com, and adyen.com, then compare their AI readability scores."

"What backlinks have we seen pointing at my-startup.com?"

"Check the score history for our marketing site over the last 30 days."

"Run a deep audit on my-startup.com as a SaaS site and list the high-severity findings."

"Run an accessibility audit on our pricing page and list the critical WCAG failures."

"Crawl my-startup.com and show me the broken links and orphan pages."

"Build starter prompts for 'SEO audit API', create a citation tracker for Acme, and run it."

The tool the AI picks is shown in your client; you can always ask "what tools did you use?" to see the trace.

Why MCP?

MCP lets the AI reach data it wouldn't have — your actual site SEO scores, the backlink graph, your monitoring history — without any custom plumbing. Every prompt that says "audit this URL" goes from idea to result in one round-trip. Same source of truth as the REST API; no copying scores between tools.

Honest framing

The backlinks tool returns an audit-fed sample, not a comprehensive backlink index. Every response includes a data_caveat explaining exactly what the dataset is. We are not Ahrefs and don't pretend to be — we expose the unique, growing graph our customers' audits build for free.

Source

The MCP server is open source: https://github.com/SeoScoreAPI/seoscoreapi-mcp

License

MIT

SEO Score API

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions