Lumen

io.github.nitishagar

Deterministic SEO audits as MCP tools: 36-rule site audit, keywords, rank, CWV reports.

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "io.github.nitishagar-lumen": {4      "command": "npx",5      "args": [6        "-y",7        "@lumen-seo/[email protected]"8      ],9      "env": {10        "LUMEN_PSI_KEY": "<secret>",11        "LUMEN_CRUX_KEY": "<secret>",12        "LUMEN_OPR_KEY": "<secret>"13      }14    }15  }16}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @lumen-seo/[email protected]

Credentials from the publisher

LUMEN_PSI_KEY — Google PageSpeed Insights API key — enables the CWV lab leg of page reports. Optional; without it that leg reports not-configured.
LUMEN_CRUX_KEY — Chrome UX Report API key — enables field CWV data. Optional; without it that leg reports not-configured.
LUMEN_OPR_KEY — Open PageRank API key — enables the OPR authority signal. Optional; without it that signal reports not-configured.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1LUMEN_PSI_KEY=<secret> LUMEN_CRUX_KEY=<secret> LUMEN_OPR_KEY=<secret> claude mcp add io.github.nitishagar-lumen -- npx -y @lumen-seo/cli@0.3.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.nitishagar-lumen": {4      "command": "npx",5      "args": [6        "-y",7        "@lumen-seo/[email protected]"8      ],9      "env": {10        "LUMEN_PSI_KEY": "<secret>",11        "LUMEN_CRUX_KEY": "<secret>",12        "LUMEN_OPR_KEY": "<secret>"13      }14    }15  }16}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.3.0
API key: LUMEN_PSI_KEY, LUMEN_CRUX_KEY, LUMEN_OPR_KEY
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Lumen?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Lumen need an API key?

The publisher lists these environment variables: LUMEN_PSI_KEY, LUMEN_CRUX_KEY, LUMEN_OPR_KEY.

What transport does Lumen use?

Lumen runs locally over stdio.

When was Lumen last checked?

Last checked 2026-10-28. Deterministic SEO audits as MCP tools: 36-rule site audit, keywords, rank, CWV reports.

From the publisher

Documentation

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 (0 pass, 1 findings, 2 usage/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/) — plain node import, no flags, no tsx. 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

Lumen

io.github.nitishagar

Deterministic SEO audits as MCP tools: 36-rule site audit, keywords, rank, CWV reports.

Marketing

Add to Cursor Add to VS Code Run on PlugMCP

GitHub npm

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "io.github.nitishagar-lumen": {4      "command": "npx",5      "args": [6        "-y",7        "@lumen-seo/[email protected]"8      ],9      "env": {10        "LUMEN_PSI_KEY": "<secret>",11        "LUMEN_CRUX_KEY": "<secret>",12        "LUMEN_OPR_KEY": "<secret>"13      }14    }15  }16}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @lumen-seo/[email protected]

Credentials from the publisher

LUMEN_PSI_KEY — Google PageSpeed Insights API key — enables the CWV lab leg of page reports. Optional; without it that leg reports not-configured.
LUMEN_CRUX_KEY — Chrome UX Report API key — enables field CWV data. Optional; without it that leg reports not-configured.
LUMEN_OPR_KEY — Open PageRank API key — enables the OPR authority signal. Optional; without it that signal reports not-configured.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1LUMEN_PSI_KEY=<secret> LUMEN_CRUX_KEY=<secret> LUMEN_OPR_KEY=<secret> claude mcp add io.github.nitishagar-lumen -- npx -y @lumen-seo/cli@0.3.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.nitishagar-lumen": {4      "command": "npx",5      "args": [6        "-y",7        "@lumen-seo/[email protected]"8      ],9      "env": {10        "LUMEN_PSI_KEY": "<secret>",11        "LUMEN_CRUX_KEY": "<secret>",12        "LUMEN_OPR_KEY": "<secret>"13      }14    }15  }16}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.3.0
API key: LUMEN_PSI_KEY, LUMEN_CRUX_KEY, LUMEN_OPR_KEY
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Lumen?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Lumen need an API key?

The publisher lists these environment variables: LUMEN_PSI_KEY, LUMEN_CRUX_KEY, LUMEN_OPR_KEY.

What transport does Lumen use?

Lumen runs locally over stdio.

When was Lumen last checked?

Last checked 2026-10-28. Deterministic SEO audits as MCP tools: 36-rule site audit, keywords, rank, CWV reports.

From the publisher

Documentation

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

Local site audits — bounded, robots-respecting crawler with 36 built-in rules, severity scoring, and CI-friendly exit codes (0 pass, 1 findings, 2 usage/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/) — plain node import, no flags, no tsx. 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.