io.github.nitishagar/lumen
Deterministic SEO audits as MCP tools: 36-rule site audit, keywords, rank, CWV reports.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@lumen-seo/cliclaude mcp add lumen -e 'LUMEN_PSI_KEY=<your lumen_psi_key>' -e 'LUMEN_CRUX_KEY=<your lumen_crux_key>' -e 'LUMEN_OPR_KEY=<your lumen_opr_key>' -- npx -y @lumen-seo/cli@0.3.0
{
"mcpServers": {
"lumen": {
"command": "npx",
"args": [
"-y",
"@lumen-seo/cli@0.3.0"
],
"env": {
"LUMEN_PSI_KEY": "<your lumen_psi_key>",
"LUMEN_CRUX_KEY": "<your lumen_crux_key>",
"LUMEN_OPR_KEY": "<your lumen_opr_key>"
}
}
}
}
Environment variables
LUMEN_PSI_KEYsecret Google PageSpeed Insights API key — enables the CWV lab leg of page reports. Optional; without it that leg reports not-configured.LUMEN_CRUX_KEYsecret Chrome UX Report API key — enables field CWV data. Optional; without it that leg reports not-configured.LUMEN_OPR_KEYsecret Open PageRank API key — enables the OPR authority signal. Optional; without it that signal reports not-configured.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
lumen
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
Frequently asked questions
What is io.github.nitishagar/lumen?
Deterministic SEO audits as MCP tools: 36-rule site audit, keywords, rank, CWV reports.
How do I install io.github.nitishagar/lumen?
It runs on your machine. In Claude Code: claude mcp add lumen -e 'LUMEN_PSI_KEY=<your lumen_psi_key>' -e 'LUMEN_CRUX_KEY=<your lumen_crux_key>' -e 'LUMEN_OPR_KEY=<your lumen_opr_key>' -- npx -y @lumen-seo/cli@0.3.0. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.nitishagar/lumen need an API key?
Yes. It expects LUMEN_PSI_KEY, LUMEN_CRUX_KEY, LUMEN_OPR_KEY, which you set in its configuration.
Is io.github.nitishagar/lumen open source?
Yes. Its code is on GitHub under the Apache-2.0 license.
Who maintains io.github.nitishagar/lumen?
It is published by nitishagar. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.