@abbyseo/mcp-server

Model Context Protocol server for abbyseo.com — exposes the SEO scanner's JSON API as Claude Desktop / Claude Code tools.

Tools

| Tool | What it does | |---|---| | submit_scan(url, email) | Queues a new SEO scan. Returns scan_id. Email is required (results are emailed). | | get_scan_status(scan_id) | Polls scan progress. Returns status, score, counts. | | get_scan_results(scan_id) | Returns full findings: per-check pass/warn/fail with remediation text, plus an upgrade block linking to a paid PDF guide. |

Free API tier returns the top 5 issues by severity; paid customers (one-time $8.99) see all checks plus a prioritized fix guide. Every check also carries a when_doesnt_apply field — context for when the rule legitimately doesn't apply to a site type (e.g., link aggregators deliberately omit a visible H1).

Two ways to use this

1. Remote MCP (easier, no install) — point your client at https://www.abbyseo.com/mcp. The server runs on our infrastructure; you just configure the URL.
2. Local stdio (this npm package) — the client launches npx @abbyseo/mcp-server and talks to it over stdio. Same three tools, runs in your environment, no network call until a scan is submitted.

Pick remote for the lowest-friction install. Pick local if you prefer the client to spawn the server directly or want to override ABBYSEO_API_BASE for staging.

Install — Remote MCP (Claude Code)

claude mcp add --transport http abbyseo https://www.abbyseo.com/mcp

Install — Claude Desktop

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "abbyseo": {
      "command": "npx",
      "args": ["-y", "@abbyseo/mcp-server"]
    }
  }
}

Restart Claude Desktop. You'll see the abbyseo tools appear in the tool list.

Install — Claude Code (local stdio)

claude mcp add abbyseo -- npx -y @abbyseo/mcp-server

Usage

Once installed, ask Claude things like:

Scan https://example.com for SEO issues — my email is [email protected] What were the top issues? How do I fix the heading hierarchy problem?

Claude will call the tools, surface the findings, and include the upgrade link in its summary.

Local development / testing

git clone https://github.com/abbyseo/mcp-server abbyseo-mcp-server
cd abbyseo-mcp-server
npm install
npm run build
# Point Claude Desktop at the local build instead of npm:
#   "command": "node",
#   "args": ["/absolute/path/to/abbyseo-mcp-server/dist/server.js"]

Override the API base URL for testing against staging:

ABBYSEO_API_BASE=https://staging.abbyseo.com node dist/server.js

License

MIT