LightSpot vs Moxie Docs MCP
A side-by-side look at the LightSpot and Moxie Docs MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LightSpotMarketing · Local subprocess (stdio)Audit a website for SEO and AI search visibility (ChatGPT, Perplexity, Gemini) and read the fixes.53GoodAuth: api key requiredVerdict: choose LightSpot for marketing work as a local process; choose Moxie Docs MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
LChoose LightSpot when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
LIGHTSPOT_API_KEY, LIGHTSPOT_BASE_URL. - You want tools like
audit_and_wait, run_audit, get_audit_status.
Choose Moxie Docs MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L LightSpot | |
|---|---|---|
| Category | Marketing | Knowledge & Memory |
| Quality signal | 53/100 · Good | 80/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | Freemium |
| Required env vars | LIGHTSPOT_API_KEYLIGHTSPOT_BASE_URL | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 36 views 25 installs 4 upvotes |
| Tools | 11 | 12 |
| Full listing | View LightSpot | View Moxie Docs MCP |
Tools & capabilities
LightSpot tools 11
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:…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.
Moxie Docs MCP tools 12
moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.moxie.get_doc_impactGiven the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.moxie.get_api_contextGiven paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.moxie.review_changeSelf-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.moxie.get_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).moxie.list_docsPaginated, section-grouped table of contents of every generated doc.moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.moxie.propose_doc_removalRemove a Moxie-tracked doc your change makes obsolete; returns the path to delete in your branch.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
LightSpot
{
"mcpServers": {
"lightspot": {
"command": "npx",
"args": [
"-y",
"@lightspot/mcp"
],
"env": {
"LIGHTSPOT_API_KEY": "YOUR_LIGHTSPOT_API_KEY_HERE",
"LIGHTSPOT_BASE_URL": "YOUR_LIGHTSPOT_BASE_URL_HERE"
}
}
}
}
Moxie Docs MCP
{
"mcpServers": {
"moxie-docs-mcp": {
"command": "npx",
"args": [
"-y",
"moxie-docs"
]
}
}
}
Frequently asked questions
LightSpot is categorized under Marketing and uses a local stdio subprocess. Moxie Docs MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick LightSpot for marketing work and Moxie Docs MCP for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
LightSpot is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add lightspot and moxie-docs-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, LightSpot has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Moxie Docs MCP has 80/100 (Excellent) with 36 views, 25 installs and 2 GitHub stars.
