seo-tools-mcp

seo-tools-mcp

Upgrading from an earlier package name: replace the package in your MCP client command with npx -y seo-tools-mcp@latest. Existing environment settings and saved data remain compatible.

An SEO MCP server — a stdio Model Context Protocol server that gives an AI host a set of SEO tools. The MVP is 100% free and keyless: on-page/technical audits, robots.txt, sitemaps, structured data, broken-link checks, and keyword ideas.

Built on the same proven scaffold as mcp-browser-extension: SDK Server → StdioServerTransport, a flat tool registry, and a never-throw dispatch firewall.

Tools (all free, no API key)

Use it as an MCP server

Requires Node 20.18.1+. Local Lighthouse audits require Node 22.19+; Node 24 is recommended for all features. There is nothing to clone, build, or configure — add this to your MCP host config (e.g. a project .mcp.json) and restart the host:

{
  "mcpServers": {
    "seo-tools-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "seo-tools-mcp@latest"]
    }
  }
}

Or with Claude Code: claude mcp add seo-tools-mcp -- npx -y seo-tools-mcp@latest

Or, after npm install -g seo-tools-mcp@latest, set "command": "seo-tools-mcp" with no args.

Windows

WSL2 is not required — native Windows works. One config change is, though: on Windows npx is npx.cmd, a batch shim, and MCP hosts spawn the server without a shell, which cannot execute a .cmd. So "command": "npx" fails to start. Wrap it in cmd /c:

{
  "mcpServers": {
    "seo-tools-mcp": {
      "type": "stdio",
      "command": "cmd",
      "args": ["/c", "npx", "-y", "seo-tools-mcp@latest"]
    }
  }
}

Or: claude mcp add seo-tools-mcp -- cmd /c npx -y seo-tools-mcp@latest

Develop

From a source checkout:

npm install
npm run build      # → dist/src/cli.js
npm test

Then point your host at the local build with "command": "node", "args": ["<abs-path>/dist/src/cli.js"].

Then ask things like "audit https://example.com for SEO" or "what does example.com's robots.txt block?".

Quick smoke test (no MCP host needed)

node -e "require('./dist/src/seo/audit').auditPage('https://example.com').then(r=>console.log(JSON.stringify(r,null,2)))"

Develop

npm run typecheck   # tsc --noEmit
npm run build       # → dist/
npm test            # node:test suite (no network — fetch is stubbed)

CI (.github/workflows/ci.yml) runs typecheck → build → test on Node 20/22. Node 20.18.1+ is required by Cheerio and Undici. The optional local Lighthouse engine requires Node 22.19+; hosted PageSpeed checks remain available on Node 20.18.1+.

Performance & output size

• Request caching — identical GETs are de-duplicated by a short-TTL cache with in-flight coalescing, so a audit_page → export_audit_pdf pair (or a sitemap/robots.txt referenced during a crawl) hits the network once. Tune with SEO_MCP_CACHE_TTL_MS (milliseconds, default 15000); set 0 to disable.
• Compact audit_site — by default the site audit returns a slim, worst-first per-page table (score + issue counts) plus the aggregates, to keep the response small inside an MCP host's context. Pass detail: true for the full per-page breakdown, or use export_site_pdf for a formatted report.

PageSpeed (optional key)

The pagespeed tool works keyless but Google rate-limits anonymous requests. To raise the quota, grab a free PageSpeed Insights API key and set it in your MCP host config:

{
  "mcpServers": {
    "seo-tools-mcp": {
      "type": "stdio",
      "command": "node",
      "args": ["<absolute-path>/seo-tools-mcp/dist/src/cli.js"],
      "env": { "PAGESPEED_API_KEY": "your-key-here" }
    }
  }
}

Roadmap (needs a key — not in the free MVP)

• serp_rank — real SERP position checks (drive a browser, or a paid SERP API)
• domain_authority — OpenPageRank (free key) for an authority score
• backlinks — real backlink profiles (paid: Ahrefs / SEMrush / DataForSEO)

Related

• MCP Browser Extension (mcp-browser-extension): let Claude, Cursor or any MCP agent use the Chrome you are already logged into, with a deny-all domain allowlist.

License

MIT