SEO Score API in your AI assistant (MCP server)
Add https://seoscoreapi.com/mcp to any assistant that supports remote MCP
servers. Sign in to seoscoreapi.com when it asks, or send your API key as
Authorization: Bearer ssa_... (or X-API-Key: ssa_...). Then ask it to
audit a URL.
https://seoscoreapi.com/mcpPick your assistant
ChatGPT
Sign-in only
Claude (claude.ai and Claude Desktop)
Sign-in or API key header
Claude Code
API key header or sign-in
Cursor
API key header or sign-in
GitHub Copilot in VS Code
API key header
Gemini CLI and Antigravity
API key header or sign-in
OpenAI Codex
API key (bearer) or sign-in
Windsurf (Devin Desktop)
API key header or sign-in
Microsoft Copilot Studio
API key header
Two ways to connect
- Sign in (OAuth). Add the URL; the assistant opens seoscoreapi.com, you sign in with an email link, Google or GitHub (or create a free account) and click Allow. ChatGPT and Claude's connectors work this way, and so do the coding tools that support MCP sign-in.
- API key header. For any client that lets you set request headers:
Authorization: Bearer ssa_...orX-API-Key: ssa_....
Listing the tools works without either; every tool call needs one.
What your assistant can do
SEO audit
Score any URL out of 100 with 80+ checks and a prioritised fix list; batch audits, side-by-side comparisons and score history.
GEO and AI visibility
How visible a page is to AI search, how readable it is for LLMs, brand mention probes and llms.txt generation.
ADA / WCAG accessibility
WCAG 2.1 AA violations with the affected elements and a plain-English fix for each.
AI citation tracking
Track whether ChatGPT, Gemini, Perplexity and Claude mention and cite your brand for the prompts your buyers use.
Site crawl and Deep Audit
Broken pages, redirects, duplicates and orphans across a site, and the full Deep Site Audit.
Monitoring
Score and GEO monitors that re-check a URL on a schedule, plus conversion scores, tracker inventories and page-2 quick wins.
Prompts to try first
| Ask | Tool | Plan |
|---|---|---|
| Audit https://example.com and list the top 5 fixes, most important first. | audit | Free key |
| How well can AI assistants read https://example.com? Run an AI readability check. | ai_readability | Free key |
| Score the conversion of https://example.com/pricing and tell me what is costing sign-ups. | conversion | Free key (full fix list on paid plans) |
| Is https://example.com visible to ChatGPT and AI search? Run a GEO audit. | geo_audit | Basic ($15/mo) and up |
| Check https://example.com for ADA / WCAG 2.1 AA issues and list the critical ones with fixes. | accessibility_audit | Paid plans, from Starter ($5/mo) |
| Generate an llms.txt file for example.com. | llms_txt | Any key |
| Crawl example.com and show me the broken pages, redirects and orphan pages. | crawl_site | Pro ($39/mo), Ultra or a Deep Audit credit |
| Track whether ChatGPT, Gemini, Perplexity and Claude mention Acme when people ask for an SEO tool. Build starter prompts, create a citation tracker and run it. | create_citation_tracker | Starter ($5/mo) and up |
| Run a Deep Audit on https://example.com and list the high-severity findings. | deep_audit | Pro ($39/mo), Ultra or credits |
FAQ
What is the SEO Score API MCP server?
A hosted Model Context Protocol server at https://seoscoreapi.com/mcp. Add it to an AI assistant and the assistant can run SEO Score API's audits and trackers for you: SEO, GEO and AI visibility, ADA / WCAG accessibility, AI citations, site crawls, Deep Audits and monitoring.
Is it free?
Yes, to start. A free SEO Score API key includes 20 audits a month and needs no card. GEO audits, accessibility audits, citation tracking, crawls and Deep Audits need a paid plan; plans start at Starter ($5/mo). Every tool call uses your plan's allowance exactly as the REST API does.
Do I need to install anything?
No. The server is hosted at https://seoscoreapi.com/mcp, so you add a URL, not a program. If your assistant only runs local servers, the same tools are in the open-source npm package: npx -y seoscoreapi-mcp with SEO_SCORE_API_KEY set.
API key or sign-in: which should I use?
Either works. Assistants that let you set a request header can send your key as Authorization: Bearer ssa_... or X-API-Key: ssa_.... Assistants with MCP sign-in open seoscoreapi.com, you sign in with an email link, Google or GitHub (or create a free account), approve, and you are done. Listing the tools works without either; running one needs one of them.
What can't it do?
It does not download PDF reports (a tool result is text; the audit tool returns the same data), it does not change account settings such as auto-reload, and it cannot create, upgrade or rotate keys. Those stay in your dashboard.
Prefer a local server?
The same tools ship as an open-source npm package that runs on your machine over stdio. Any client that runs local MCP servers can use it:
{
"mcpServers": {
"seoscoreapi": {
"command": "npx",
"args": [
"-y",
"seoscoreapi-mcp"
],
"env": {
"SEO_SCORE_API_KEY": "ssa_your_key_here"
}
}
}
}Source: github.com/SeoScoreAPI/seoscoreapi-mcp.
Questions? Email aaron@seoscoreapi.com. See every AI assistant guide, all integrations and the API docs.