One pass. Every tip.
Your agent.

The directory is free to read. The MCP server is the product: it gives Claude Code, Cursor or claude.ai a ranked, applicable SEO plan for the project it is working in. $19 once — not monthly.

Directory

$0

For reading and research.

  • Every published tip, browsable and searchable
  • Extended briefs and agent prompts with a free account
  • RSS, llms.txt, and the public JSON API
Browse tips

MCP access

$19 once

Lifetime access. Not a subscription.

  • Remote MCP server at /mcp (Streamable HTTP)
  • 18 tools: project profiles, ranked plans, progress, verification, feedback
  • 600 requests/hour per key, keys you can revoke
  • Every tip added later, including new tools

Pre-order joins the list; the owner emails a key and grants access once checkout is live. Nothing is charged today.

Manual SEO vs the MCP pass

Doing it by hand

  • Search a tweet, open the article, read to the end, guess the order.
  • Re-explain your stack to a general-purpose chatbot every session.
  • No record of what was applied, verified or skipped.
  • Advice drifts: no source, no check, no risk label.

With seo-mcp connected

  • The agent profiles the repo and gets only the tips that apply.
  • The plan is ordered foundation → quick wins → growth, with a check per step.
  • Progress, verification and evidence persist per project.
  • Every tip links to its source; risky moves are labelled and opt-in.

What your agent will do

One connection, then a normal conversation. This is the shape of a first session:

You: connect to seo-mcp.io and work on the SEO of this project

Agent → start_seo_session   { project_id: "riverstone-web" }
Agent → profile_project     { stack: ["nextjs"], site_type: "saas" }
Agent → audit_html          { files: ["app/layout.tsx", "app/page.tsx"] }
Agent → get_action_plan     { limit: 10 }

Plan
 1. Add canonical URLs with the Metadata API          high
 2. Ship app/sitemap.ts and app/robots.ts             high
 3. Add Organization JSON-LD in the root layout       high
 4. Unique title and description per route            medium

Agent edits the files, runs the checks, then:
Agent → verify_tip { tip: "canonical-metadata", evidence: "…" }
Agent → get_progress → 1/4 applied, 1 verified

What you can hold us to

Every published tip names its source and links to it. The extended briefs and prompts are written at ingestion time and reviewed; nothing is generated when your agent asks. That is why the same request returns the same plan on every client, and why a wrong tip is a bug we can fix for everyone.

Read the index first — the free half is the whole catalogue.

The free audit result for seo-mcp.io: 98/100, one low-severity redirect finding, and the tip that fixes it
The same deterministic checks the MCP server runs, on this site: 98/100, one low-severity finding, linked to the tip that fixes it. Captured 2026-10-19.
Crop of get_action_plan returning ten ordered steps with a do, a verify check and a source for each
The plan your agent receives: ten ordered steps, each with a do, a verify check and its source. Cropped from a session against the Next.js fixture.

162 published tips in 9 categories704 of 704 steps carry a verify commandsources: practitioners on X and official docsruns on Claude Code, Cursor and claude.ai

Questions buyers ask

What does the MCP server actually do?

It exposes the catalogue to your agent as tools: profile a repository, get a ranked plan, record what you applied, verify a fix, and fetch the next action. Answers are deterministic lookups over the curated tips; no AI runs at request time.

Why not free?

Reading the directory is free and stays free. The pass pays for the server: the profiling, the applicability rules, progress storage and the upkeep of the catalogue. It is a one-time payment because the work is done at ingestion, not on every request.

Is my repository data sent anywhere?

No file contents leave your machine. The agent sends the signals the tools ask for — framework, site type, detected issues, a project name — and receives tips. Media keys and API keys are never included in MCP output.

Do I need a separate account for Claude?

No. Claude connectors use OAuth: you sign in here, approve the connection, and the server issues a revocable API key. Cursor and other clients can paste a key directly.

What if a tip is wrong or outdated?

Use submit_feedback from your agent, or the “report an error” link on the tip. The message reaches the editor and the fix lands for every property using that tip.

Is this a subscription?

No. $19 once, lifetime access, no renewal and nothing to cancel. New tips and new tools are included.

Checkout is not enabled yet on this deployment; pre-orders join the list and the owner grants access manually. Questions: hello@seo-mcp.io.