Audit websites for SEO and AI search visibility, access expert reports, and manage editorial calendars through an AI assistant.
Also known as nmarijane/lightspot-mcp, lightspot-mcp, @lightspot/mcp
- Stars
- 0
- Tools
- 11
- Downloads, 30 days
- 236
- Latest version
- 0.6.0
- Last commit
- Nov 8, 2026
- License
- MIT
What is LightSpot MCP?
LightSpot is an MCP server. Audit websites for SEO and AI search visibility, access expert reports, and manage editorial calendars through an AI assistant. It exposes 11 tools, such as audit_and_wait, run_audit, get_audit_status.
Summary generated from the project's README
About LightSpot MCP server
LightSpot provides an MCP server that allows developers and SEO professionals to perform website audits focused on search engine optimization and AI visibility. By connecting this server to clients like Claude Desktop, Claude Code, or Cursor, users can use an AI assistant to analyze why a site might not be cited by models like ChatGPT. The server functions by wrapping the LightSpot public API and requires a valid API key from an Eclat, Halo, or Zenith plan to operate.
Users can interact with specific tools to manage their digital presence. The audit_and_wait tool provides immediate summaries of scores and issues, while get_expert_report offers detailed insights from eight different specialist areas including technical SEO and brand authority. Beyond auditing, the server includes capabilities for content management through the get_editorial_calendar and create_editorial_calendar tools, which allow for the importing or updating of up to 50 dated editorial slots.
What you can do with it
- 1Analyze AI search visibilityAsk the assistant to audit a specific URL and identify why it is not being cited by AI models.
- 2Review specialist SEO feedbackRetrieve detailed recommendations from experts regarding structured data or technical performance.
- 3Manage content schedulesCreate and import a multi-week editorial plan directly into the LightSpot platform.
- 4Perform competitor analysisIdentify detected competitors and receive recommendations on how to improve standing.
Written from the project's README. Every use case is checked against a quote from it.
How to install LightSpot MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall LightSpot MCP in Claude Code
$ claude mcp add --env 'LIGHTSPOT_API_KEY=<YOUR_LIGHTSPOT_API_KEY>' lightspot-mcp -- npx -y @lightspot/mcpInstall LightSpot MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"lightspot-mcp": {
"command": "npx",
"args": [
"-y",
"@lightspot/mcp"
],
"env": {
"LIGHTSPOT_API_KEY": "<YOUR_LIGHTSPOT_API_KEY>"
}
}
}
}Install LightSpot MCP in VS Code
.vscode/mcp.json
{
"servers": {
"lightspot-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@lightspot/mcp"
],
"env": {
"LIGHTSPOT_API_KEY": "<YOUR_LIGHTSPOT_API_KEY>"
}
}
}
}Install LightSpot MCP in VS Code CLI
$ code --add-mcp '{"name":"lightspot-mcp","type":"stdio","command":"npx","args":["-y","@lightspot/mcp"],"env":{"LIGHTSPOT_API_KEY":"<YOUR_LIGHTSPOT_API_KEY>"}}'Install LightSpot MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"lightspot-mcp": {
"command": "npx",
"args": [
"-y",
"@lightspot/mcp"
],
"env": {
"LIGHTSPOT_API_KEY": "<YOUR_LIGHTSPOT_API_KEY>"
}
}
}
}Install LightSpot MCP in Codex
$ codex mcp add lightspot-mcp --env 'LIGHTSPOT_API_KEY=<YOUR_LIGHTSPOT_API_KEY>' -- npx -y @lightspot/mcpInstall LightSpot MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.lightspot-mcp] command = "npx" args = ["-y", "@lightspot/mcp"] [mcp_servers.lightspot-mcp.env] LIGHTSPOT_API_KEY = "<YOUR_LIGHTSPOT_API_KEY>"
Install LightSpot MCP in Gemini CLI
$ gemini mcp add -s user -e 'LIGHTSPOT_API_KEY=<YOUR_LIGHTSPOT_API_KEY>' lightspot-mcp npx -- -y @lightspot/mcpInstall LightSpot MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"lightspot-mcp": {
"command": "npx",
"args": [
"-y",
"@lightspot/mcp"
],
"env": {
"LIGHTSPOT_API_KEY": "<YOUR_LIGHTSPOT_API_KEY>"
}
}
}
}LightSpot MCP tools 11
Detected from the READMEaudit_and_waitrun_auditget_audit_statusget_auditlist_sitesget_sitelist_site_auditsget_competitorsget_expert_reportget_editorial_calendarcreate_editorial_calendar
| audit_and_wait | — | |
| run_audit | — | |
| get_audit_status | — | |
| get_audit | — | |
| list_sites | — | |
| get_site | — | |
| list_site_audits | — | |
| get_competitors | — | |
| get_expert_report | — | |
| get_editorial_calendar | — | |
| create_editorial_calendar | — |
Configuration
LIGHTSPOT_API_KEYRequiredSecretLightSpot API key (lspai_live_…), created in the LightSpot app
LIGHTSPOT_BASE_URLOptional API base URL, defaults to https://lightspot.ai
| Name | Description | |
|---|---|---|
| LIGHTSPOT_API_KEY | LightSpot API key (lspai_live_…), created in the LightSpot app | RequiredSecret |
| LIGHTSPOT_BASE_URL | Optional API base URL, defaults to https://lightspot.ai |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@lightspot/mcp
MCP server for LightSpot.ai — run SEO and AI-visibility audits, read their results and our experts' reports, and import editorial calendars from any MCP client (Claude Desktop, Claude Code, Cursor, …).
It wraps the LightSpot public API (/v1) as MCP tools, so an AI assistant can "audit this site and tell me why ChatGPT doesn't cite it" in one step.
Requirements
- A LightSpot API key (
lspai_live_…) — create one in LightSpot → Integrations → API keys. API access is included in the Eclat, Halo and Zenith plans. - Node.js ≥ 18 (run on demand via
npx, nothing to install globally).
Setup
Add the server to your MCP client config and set your API key:
{
"mcpServers": {
"lightspot": {
"command": "npx",
"args": ["-y", "@lightspot/mcp"],
"env": {
"LIGHTSPOT_API_KEY": "lspai_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
}
}
}
- Claude Desktop →
claude_desktop_config.json - Claude Code →
claude mcp addor your project's.mcp.json - Cursor →
~/.cursor/mcp.json
Environment variables
| Variable | Required | Description |
|---|---|---|
LIGHTSPOT_API_KEY |
yes | Your API key (lspai_live_…). |
LIGHTSPOT_BASE_URL |
no | Override the API base URL (defaults to https://lightspot.ai). For self-hosted/testing only. |
Claude plugin
The plugin/ folder is the Claude plugin. It connects Claude to LightSpot's hosted MCP server (https://mcp.lightspot.ai/mcp, same tools, OAuth sign-in instead of an API key) and adds an ai-visibility-audit skill. See plugin/README.md.
Tools
| Tool | What it does |
|---|---|
audit_and_wait |
Run an audit on a URL, wait for it to finish, and return a summary (score, top actions, main issues). The one-shot "audit this and tell me what's wrong." |
run_audit |
Start an audit without waiting (returns the audit id). |
get_audit_status |
Lightweight status of an audit (PENDING/RUNNING/DONE/FAILED + progress 0–1). |
get_audit |
Audit results — a trimmed summary by default, or the full payload with full: true. |
list_sites |
List the sites in your team (with their latest score). |
get_site |
A site's metadata and recent audits. |
list_site_audits |
A site's paginated audit history. |
get_competitors |
Get a site's latest competitor analysis (detected competitors, tiers, citations, recommendations). Read-only — does not trigger a new analysis. Requires the Halo or Zenith plan. |
get_expert_report |
Read the latest report from our 8 experts (technical SEO, content, AI visibility, structured data, sitemaps, performance, visual, brand authority) for a site or a given audit: prioritized findings, recommended actions with steps, limitations and ready-to-apply artifacts. Summary by default, full: true for everything, expert to read one chapter. Read-only — does not trigger an analysis. |
get_editorial_calendar |
Read a site's calendar over an ISO date range, including imported slots and content already preparing, scheduled, or published. |
create_editorial_calendar |
Import or update up to 50 dated editorial slots. Idempotent with externalId; it does not generate or publish content. |
Example prompts
- "Audit https://example.com and give me the top 3 things to fix for AI visibility."
- "List my LightSpot sites and which one has the lowest score."
- "Get the full results for audit
<id>and group the issues by severity." - "What competitors were detected for my site
<siteId>, and what should I do about them?" - "Read the experts' report for my site
<siteId>and fix what the structured-data expert recommends in my codebase." - "Create a four-week editorial calendar for my site
<siteId>with two LinkedIn posts and one educational Reddit post per week, then import it into LightSpot." - "Show me everything planned or published for site
<siteId>between 2026-08-01T00:00:00+02:00 and 2026-09-01T00:00:00+02:00."
Notes
- Quotas (audits/month, pages/audit) and per-key rate limits follow your LightSpot plan.
- Importing editorial slots does not consume AI credits and never generates, schedules, or publishes content automatically.
- The full REST API reference lives at lightspot.ai/docs/api.
License
MIT
LightSpot MCP questions
How do I add LightSpot MCP to Claude Code?
Run claude mcp add --env 'LIGHTSPOT_API_KEY=<YOUR_LIGHTSPOT_API_KEY>' lightspot-mcp -- npx -y @lightspot/mcp in your terminal. Add --scope user to make it available in every project.
How do I add LightSpot MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does LightSpot MCP provide?
It exposes 11 tools, including audit_and_wait, run_audit, get_audit_status, get_audit, list_sites.
How do I set up LightSpot with my MCP client?
Add the server to your MCP client configuration using npx and provide your LIGHTSPOT_API_KEY in the environment variables.
Does importing an editorial calendar automatically publish content?
No, importing editorial slots is idempotent and does not generate or publish content automatically.
Can I get competitor analysis with this server?
Yes, you can use the get_competitors tool to see detected competitors and recommendations, provided you are on the Halo or Zenith plan.