
LightSpot
io.github.nmarijanev0.5.0Updated Oct 3, 2026
Audit a website for SEO and AI search visibility (ChatGPT, Perplexity, Gemini) and read the fixes.
Overview
Lets an assistant run SEO and AI-search visibility audits on a website, read the results and expert reports, and import editorial calendars.
- What it does
- Wraps the LightSpot public API as MCP tools. It can start an audit on a URL and wait for a summary of score, top actions and main issues, or run it asynchronously and poll status and results. It also lists team sites and their audit history, reads competitor analysis and the latest expert report across eight disciplines, and reads or imports dated editorial calendar slots.
- When to use it
- Useful when you want an assistant to check why a site is or is not cited by AI search engines, to pull prioritized SEO and GEO fixes into a coding or content workflow, or to move an editorial calendar between a planning tool and LightSpot.
- Requirements
- Runs locally via npx, so Node.js 18 or newer is needed. Requires a LightSpot API key (lspai_live_...) set as the LIGHTSPOT_API_KEY environment variable; API access is included in the Zenith plan. An optional LIGHTSPOT_BASE_URL overrides the default API base URL. Network access to the LightSpot API is required.
Installation
In SourceWeft
- Open LightSpot in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@lightspot/mcp
MCP server for LightSpot.ai — run SEO & GEO 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 Zenith plan. - 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:
- Claude Desktop →
claude_desktop_config.json - Claude Code →
claude mcp addor your project's.mcp.json - Cursor →
~/.cursor/mcp.json
Environment variables
Tools
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
Source: README.md at commit 98536cb
Tools
0Version history
1- v0.5.0LatestOct 3, 2026


