MCP SEO Auditor MCP server

MCP SEO Auditor

Read-only SEO tools for Claude Code, Cursor and other MCP clients. Audits run locally. No API keys, telemetry, AI-provider costs or runtime dependencies.

MVP 0.1.0. Node wrapper requires Python 3.11+ (python3, or set MCPSEOPYTHON to an absolute executable path).

Install in your AI client

Requires Python 3.11+ on PATH in addition to Node.js. Works with any MCP client over stdio; no account or API key needed for the local server.

Claude Code

claude mcp add seo-auditor -- npx -y mcp-seo-auditor

Codex CLI

codex mcp add seo-auditor -- npx -y mcp-seo-auditor

Claude Desktop, Cursor, Windsurf, Cline, Gemini CLI — add to the client's MCP config (claudedesktopconfig.json, ~/.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, Cline MCP settings, ~/.gemini/settings.json):

{
  "mcpServers": {
    "seo-auditor": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-seo-auditor"
      ]
    }
  }
}

VS Code / GitHub Copilot — .vscode/mcp.json:

{
  "servers": {
    "seo-auditor": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-seo-auditor"
      ]
    }
  }
}

Zed — settings.json:

{
  "context_servers": {
    "seo-auditor": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-seo-auditor"
      ]
    }
  }
}

Run from a checkout

npm test
node bin/mcp-seo-auditor.mjs

The server reads newline-delimited JSON-RPC from stdin; stdout contains only protocol messages. It waits for an MCP client when started directly.

Claude Code registration (replace path):

claude mcp add seo-auditor -- node /absolute/path/mcp-seo-auditor/bin/mcp-seo-auditor.mjs

Generic MCP configuration:

{
  "mcpServers": {
    "seo-auditor": {
      "command": "node",
      "args": ["/absolute/path/mcp-seo-auditor/bin/mcp-seo-auditor.mjs"]
    }
  }
}

Alternatively install Python package with pip install . and run mcp-seo-auditor. Build-time setuptools is needed; runtime uses only stdlib.

Configuration can use npx -y mcp-seo-auditor.

Tools

Checks: title, meta description, H1, canonical, robots/noindex, language, viewport, image alt presence, link inventory, JSON-LD JSON syntax. Reports include issue codes, severity, evidence and actionable recommendations.

Example agent requests:

• “Audit https://example.com/ and prioritize the fixes.”
• “Crawl 10 pages and find duplicate titles.”
• “Audit this HTML before I deploy it.”

Boundaries and security

Shortened. The full README is on GitHub.