
LightSpot
io.github.nmarijanePublished by GitHub account nmarijanev0.6.0Updated Nov 8, 2026
Audit a website for SEO and AI search visibility (ChatGPT, Perplexity, Gemini) and read the fixes.
The publisher's own server: Spot
Overview
Runs LightSpot SEO and AI-visibility audits on a website and returns scores, issues, expert reports and competitor analysis to an assistant.
- What you can do
- Run audits on a URL, either waiting for the result or starting one and polling its status
- Read audit results as a trimmed summary or the full payload, and browse a site's audit history
- List team sites with their latest scores and view site metadata
- Read competitor analysis and the latest expert report, by chapter or in full
- Read and import dated editorial calendar slots for a site
- When to use it
- Useful when you want an assistant to audit a site's SEO and AI search visibility, explain why assistants such as ChatGPT or Perplexity may not cite it, and turn the findings into concrete fixes or an editorial plan.
- Requirements
- Runs locally via npx, so Node.js 18 or newer is needed. Requires a LightSpot API key in the LIGHTSPOT_API_KEY environment variable, created in the LightSpot app; API access is included in the Eclat, Halo and Zenith plans. An optional LIGHTSPOT_BASE_URL overrides the API endpoint. Network access to LightSpot 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 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:
- Claude Desktop →
claude_desktop_config.json - Claude Code →
claude mcp addor your project's.mcp.json - Cursor →
~/.cursor/mcp.json
Environment variables
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
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 cbbda32
Tools
0Version history
3- v0.6.0LatestOct 4, 2026
- v0.5.1Oct 3, 2026
- v0.5.0Oct 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Spot integrations
Spot
inc.spotOfficial publisher
Spot is a remote MCP server that lets an assistant create events, sell tickets, approve guests, invite people and find events from plain text.

Drop Spot
Published by GitHub account officialdropspot
Drop Spot's local MCP server for passwordless client document intake, checklist tracking and one-click file reviews.

HubSpot MCP by AdPlug
Published by GitHub account danielpopamd
Remote HubSpot MCP connector exposing 9 tools across client portals, with write actions previewed before they run.

HubSpot Auditor
Published by GitHub account M-Pineapple
Read-only HubSpot portal audit that scores what works, what is broken, what is missing and what needs confirmation, with a 30/60/90-day fix plan.

SpotGPU
Published by GitHub account flowtestpro-svg
A discontinued MCP server that looked up spot GPU rental prices from Vast and RunPod through the SpotGPU API.