LightSpot vs Optifeed Radar
A side-by-side look at the LightSpot and Optifeed Radar 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 Optifeed Radar for marketing 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 Optifeed Radar 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:
OPENAI_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L LightSpot | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 53/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | BYOK (pay the provider) |
| Required env vars | LIGHTSPOT_API_KEYLIGHTSPOT_BASE_URL |
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.
Optifeed Radar 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
{
"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"
}
}
}
}
Optifeed Radar
{
"mcpServers": {
"optifeed-optifeed-radar": {
"command": "npx",
"args": [
"-y",
"optifeed-radar"
],
"env": {
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE"
}
}
}
}
Frequently asked questions
LightSpot is categorized under Marketing and uses a local stdio subprocess. Optifeed Radar belongs to Marketing and uses a local stdio subprocess. Pick LightSpot for marketing work and Optifeed Radar for marketing.
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. Optifeed Radar is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 optifeed-optifeed-radar 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. Optifeed Radar has 53/100 (Good) with 3 views, 0 installs and 5 GitHub stars.
