About LightSpot
LightSpot MCP brings LightSpot SEO and AI search visibility audits and reports to MCP clients. It is for teams managing site audits, expert recommendations, and editorial calendars; calendar imports do not generate or publish content.
Key features
- 01Run and view SEO and AI visibility audits
- 02Read audit status, results, and history
- 03View competitor analysis
- 04Read expert reports and recommendations
- 05Read and import editorial calendars
Use cases
- 01Check a site's visibility in AI search such as ChatGPT
- 02Review audit findings and expert recommendations
- 03Import editorial calendar slots into LightSpot
MCP support
The server wraps the LightSpot public API as MCP tools for running audits, reading results and expert reports, and importing editorial calendars.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @lightspot/mcpLIGHTSPOT_API_KEYSecretLightSpot API key (lspai_live_…), created in the LightSpot appLIGHTSPOT_BASE_URLOptional API base URL, defaults to https://lightspot.aiLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
11Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| url | string | Yes | URL to audit (home page or a specific page). |
| maxPages | integer | No | Number of pages to crawl (capped by your plan). |
Details
From the project README@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 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 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
| 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 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.