How to Connect SEOLint to Claude as an MCP Server

What Claude gets access to

Once connected, Claude has three new tools available in every conversation:

Step 1: Get your API key

SEOLint issued an API key on signup, generated instantly on the dashboard and shaped like sl_live_xxxxxxxxxxxx. Keys are no longer issued: the product shut down in July 2026. The MCP setup below is kept because the pattern transfers to any MCP server.

Step 2: Add to Claude Code

Run this once in your terminal. Replace sl_YOUR_KEY_HERE with your API key from step 1:

claude mcp add seolint \
  --env SEOLINT_API_KEY=sl_YOUR_KEY_HERE \
  -- npx -y seolint-mcp

You should see Added stdio MCP server seolint in the output.

Important: Start a new Claude Codesession after adding. The MCP server only loads on startup. After that, it's available in every session.

Or use the CLI directly

If you just want a quick scan without the MCP setup:

SEOLINT_API_KEY=sl_YOUR_KEY_HERE \
  npx @randomcode-seolint/cli scan https://mysite.com

Returns a markdown report you can paste into Claude or Cursor. Add --json for structured output.

Step 3: Ask Claude to scan

Open a new conversation and ask Claude naturally. Some examples:

When Claude Code has access to your repo, it can apply the fixes directly, not just describe them.

What Claude sees

Each issue in the scan result includes a fix_prompt field. Each one is a ready-to-use LLM instruction Claude can execute immediately:

{
  "id": "missing-h1",
  "severity": "critical",
  "title": "Missing H1 tag",
  "fix_prompt": "Add a single <h1> tag to this page containing the primary keyword. The page is about [topic]. Place it as the first heading inside the <main> element."
}

Claude reads this structure natively and can execute the fix in Cursor or Claude Code without any additional prompting from you.