For Claude

Let Claude fix your SEO

Add Abby SEO to Claude as an MCP server and Claude doesn't just audit your site — it fixes it. Scan any URL for free, then unlock a full remediation plan that Claude Code saves to your project as seo-remediation-plan.md and works through fix by fix — pausing to ask you for brand and keyword details, and re-scanning to verify each fix landed.

Install in one line (Claude Code):
claude mcp add --transport http abbyseo https://www.abbyseo.com/mcp

Then just say: “Scan example.com and fix its SEO.” — or run the getting_started prompt / how_to_use tool for a guide.

Free

Scan & preview

Claude scans any URL against 20 SEO checks (5–15s) and reports your score plus the top issues by severity. Just needs an email — results are sent there too.

Paid — one-time $8.99

The full fix plan

Unlocks every issue as an executable remediation runbook: priority-ordered fixes, copy-ready meta tags / JSON-LD schema / canonical tags, and explicit points where Claude asks you for input. Claude Code runs it end to end.

How it works

Scan → buy → Claude fixes it.

You stay in the chat the whole time — the only thing you do by hand is pay in your browser.

  1. Ask Claude to scan your site. It collects your email, runs the scan, and shows your score + top issues.
  2. Unlock the full plan ($8.99). Claude hands you a Stripe checkout link; you pay in your browser. Claude waits and picks back up automatically — no second prompt.
  3. Claude Code executes the runbook. It saves seo-remediation-plan.md to your project and works through each fix, stopping at ❓ ASK THE OWNER points (brand name, target keywords, www vs non-www, business details) so nothing is invented.
  4. It verifies. After each fix Claude re-scans the URL and confirms the check now passes — and your score climbs.
Already scanned or bought earlier? No need to track scan IDs. Just tell Claude the email you used and it calls find_my_reports to pull up your report and continue.
Install

Two ways to connect.

Remote (recommended) — Claude Code

Runs on our infrastructure at https://www.abbyseo.com/mcp. No install, no dependencies.

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

Remote — Claude Desktop / Claude.ai

Open Settings → Connectors → Add custom connector, paste https://www.abbyseo.com/mcp, and restart the client.

Local stdio (npm)

Prefer the server to run in your own environment? Use @abbyseo/mcp-server (MIT) via npx:

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

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

Tools

Eight tools — Claude picks the right one.

You never call these by name; Claude orchestrates them from your plain-English request. Listed here for reference.

ToolWhat it does
submit_scan
(url, email)
Queue an SEO scan. Email required (results are emailed). Returns a scan_id. destructiveopenWorld
get_scan_status
(scan_id)
Poll until the scan is complete (typically 5–15s). readOnlyidempotent
get_scan_results
(scan_id)
Free: score + top issues. readOnly
purchase_report
(scan_id)
Returns the $8.99 Stripe checkout link for the full plan. openWorld
get_purchase_status
(scan_id)
Lightweight “paid yet?” poll Claude uses while waiting for checkout. readOnly
get_remediation_plan
(scan_id)
The full paid runbook as Markdown — Claude Code saves & executes it. readOnly
find_my_reports
(email)
Look up your past scans by email — for returning users with no scan_id. readOnly
how_to_useReturns this usage guide inside the chat. readOnly

There's also a getting_started prompt (in Claude Code: /mcp__abbyseo__getting_started). Annotations follow the MCP spec: readOnly = no side effects; destructive = writes/sends; idempotent = stable repeat; openWorld = reaches external services.

Talking to Claude

Just ask in plain English.

FREE CHECK

“Scan example.com and tell me its top SEO issues.”

FULL FIX

“Scan example.com and fix everything you can.”

RETURNING USER

“Pull up my Abby SEO report and continue the fixes — my email is me@example.com.”

ORIENT

“How do I use Abby SEO?”

Technical details

For reviewers and integrators.

Transport

Streamable HTTP at /mcp. POST takes JSON-RPC 2.0 (initialize, tools/list, tools/call, prompts/list, prompts/get). A browser GET serves this page; an MCP GET (SSE) returns 405; DELETE returns 204. initialize returns an instructions string describing the workflow.

Authentication

No OAuth, no API key. Your email is passed per-call as a tool argument (delivery address + rate-limit key). The paid plan is gated by Stripe payment against the scan, not by login.

Rate limits

On submit_scan: 5/hr per email, 20/hr per IP+UA, 100/hr & 10/min per IP. Overflow returns 429 with a JSON reason.

Payment

The $8.99 full plan is a one-time charge via Stripe Checkout, completed in your browser — card details are never collected through the MCP tools.

Source & license

The stdio package is MIT-licensed at npmjs.com/package/@abbyseo/mcp-server. The remote endpoint runs the same protocol server-side.

Privacy & data

Scan URLs and emails are stored; scans retained 30 days; no cross-session profiling. See our Privacy Policy and Terms. Contact support@abbyseo.com.

Try it free.

Run a free scan from the homepage, or connect the MCP server and ask Claude to scan your site.

Run a free scan