Lumen
Deterministic SEO audits as MCP tools: 36-rule site audit, keywords, rank, CWV reports.
Runs on your machine from its package; the steps are below.
What it does
- Reads
- Writes
- High impact
Not assessed yet.
What it costs
FreeOdel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y @lumen-seo/cli
MCP client config
{
"mcpServers": {
"lumen": {
"command": "npx",
"args": [
"-y",
"@lumen-seo/cli"
]
}
}
}
Lightweight, pluggable, MCP-first SEO toolkit — free services only, bring your own keys, provenance on every number.
Status: v0.2.x — first public release. The CLI, the five MCP tools, and the docs site are live; see CHANGELOG.md for what shipped and the docs for the full guides.
Why lumen
Most SEO tooling is a black box with a subscription. lumen is the opposite: a local-first, agent-first audit toolkit that runs on free data sources, never ships a number it can't attribute, and speaks MCP so your coding agent can run it for you.
- Local site audits — bounded, robots-respecting crawler with 36 built-in rules, severity scoring, and CI-friendly exit codes (
0pass,1findings,2usage/abort). - Free-tier data providers — PageSpeed Insights, CrUX, Google Suggest, Wikipedia demand, OpenPageRank, Tranco, DuckDuckGo SERP. BYOK: keys are read from env vars by name, never stored or logged.
- MCP-first — five tools (
lumen_audit_site,lumen_page_report,lumen_keyword_ideas,lumen_rank_check,lumen_authority) over stdio or a thin Cloudflare Worker gateway. - Provenance on every number — each metric carries its source and fetch timestamp; no free source, no number.
Quickstart
Requires Node >= 22.7.
# One-off audit — no install
npx -y @lumen-seo/cli audit https://example.com
# Install globally
npm install -g @lumen-seo/cli
lumen audit https://example.com --max-pages 50
Wire it into Claude Code (or Cursor / VS Code — MCP onboarding):
claude mcp add --transport stdio lumen -- npx -y @lumen-seo/cli mcp
Then just ask: "audit my site and tell me what to fix first."
Packages
| Package | Purpose |
|---|---|
@lumen-seo/core | types + payload models, config loader (failThreshold), Fetcher (SSRF/timeout/backoff), robots, provider/rule SPIs + registries |
@lumen-seo/audit | bounded crawler, 36 built-in AuditRules, severity scorer, report assembly |
@lumen-seo/providers | built-in data providers (BYOK, free services only) |
@lumen-seo/cli | lumen CLI, JSONL history, stdio MCP launcher |
@lumen-seo/mcp | MCP tool definitions + transport adapters (Cloudflare Worker) |
@lumen-seo/site | docs site (live) |
Note on packaging: npm packages ship compiled JavaScript + type declarations (
dist/) — plainnodeimport, no flags, notsx. The TypeScript sources stay the source of truth in the repo; the release pipeline compiles per package at publish time.
Documentation
- Quickstart — first audit, JSON output, CI usage
- CLI reference — all thirteen commands and flags
- Rules reference — the 36 rules, severities, scoring
- Providers & BYOK — data sources, keys, rate-limit etiquette
- MCP onboarding — Claude, Cursor, VS Code, remote gateway
Development
Requires Node >= 22.
npm install
npm run lint
npm run typecheck
npm test
See CONTRIBUTING.md for conventions, SECURITY.md for the security policy, and docs/release.md for the release runbook.
License
Apache-2.0 — Copyright 2026 Nitish Agarwal
