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

AI-generated 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.
Before you install
The LIGHTSPOT_API_KEY secret is passed in the client configuration and grants access to your team's LightSpot data. The create_editorial_calendar tool writes or updates up to 50 dated slots in your account, though it does not generate, schedule or publish content. Audits consume plan quotas and are subject to per-key rate limits.

Installation

In SourceWeft

  1. Open LightSpot in the dashboard and add it to a workspace.
  2. 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:

json
{  "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.

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.
get_expert_reportRead the latest report from our 8 experts (technical SEO, content, GEO, 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

Source: README.md at commit 98536cb

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.5.0LatestOct 3, 2026