LightSpot

Official registry Search and web

Audit a website for SEO and AI search visibility (ChatGPT, Perplexity, Gemini) and read the fixes.

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).

NPM package @lightspot/mcp
Claude Code
claude mcp add lightspot -e 'LIGHTSPOT_API_KEY=<your lightspot_api_key>' -e 'LIGHTSPOT_BASE_URL=<LIGHTSPOT_BASE_URL>' -- npx -y @lightspot/mcp@0.6.0
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "lightspot": {
            "command": "npx",
            "args": [
                "-y",
                "@lightspot/mcp@0.6.0"
            ],
            "env": {
                "LIGHTSPOT_API_KEY": "<your lightspot_api_key>",
                "LIGHTSPOT_BASE_URL": "<LIGHTSPOT_BASE_URL>"
            }
        }
    }
}

Environment variables

  • LIGHTSPOT_API_KEY required secret LightSpot API key (lspai_live_…), created in the LightSpot app
  • LIGHTSPOT_BASE_URL Optional API base URL, defaults to https://lightspot.ai

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. @lightspot/mcp
  2. Requirements
  3. Setup
  4. Tools
  5. Example prompts
  6. Notes
  7. License

@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 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 add or your project's .mcp.json
  • Cursor → ~/.cursor/mcp.json
Environment variables
VariableRequiredDescription
LIGHTSPOT_API_KEYyesYour API key (lspai_live_…).
LIGHTSPOT_BASE_URLnoOverride the API base URL (defaults to https://lightspot.ai). For self-hosted/testing only.
Claude plugin

The plugin/ folder packages this server as a Claude plugin: it pins @lightspot/mcp, asks for your API key once and stores it in your system's secure credential store, and adds an ai-visibility-audit skill. See plugin/README.md.

Tools

ToolWhat it does
audit_and_waitRun 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_auditStart an audit without waiting (returns the audit id).
get_audit_statusLightweight status of an audit (PENDING/RUNNING/DONE/FAILED + progress 0–1).
get_auditAudit results — a trimmed summary by default, or the full payload with full: true.
list_sitesList the sites in your team (with their latest score).
get_siteA site's metadata and recent audits.
list_site_auditsA site's paginated audit history.
get_competitorsGet a site's latest competitor analysis (detected competitors, tiers, citations, recommendations). Read-only — does not trigger a new analysis. Requires the Zenith plan.
get_expert_reportRead 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_calendarRead a site's calendar over an ISO date range, including imported slots and content already preparing, scheduled, or published.
create_editorial_calendarImport 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

Frequently asked questions

What is LightSpot?

Audit a website for SEO and AI search visibility (ChatGPT, Perplexity, Gemini) and read the fixes.

How do I install LightSpot?

It runs on your machine. In Claude Code: claude mcp add lightspot -e 'LIGHTSPOT_API_KEY=<your lightspot_api_key>' -e 'LIGHTSPOT_BASE_URL=<LIGHTSPOT_BASE_URL>' -- npx -y @lightspot/mcp@0.6.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does LightSpot need an API key?

Yes. It expects LIGHTSPOT_API_KEY, which you set in its configuration.

Is LightSpot open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains LightSpot?

It is published by nmarijane. 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.