LightSpot vs Scrivener MCP — MCP Server Comparison | AllMCPs
LightSpot vs Scrivener MCP
A side-by-side look at the LightSpot and Scrivener MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose LightSpot for marketing work as a local process; choose Scrivener 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?
L
Choose 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.
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.
Scrivener MCP tools
No tool names declared yet. Check the project README from the listing page.
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 is categorized under Marketing and uses a local stdio subprocess. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick LightSpot for marketing work and Scrivener 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. Scrivener MCP is listed as free. Auth: no auth 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 writerslogic-scrivener-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. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.