@synapse/mcp-server

The Synapse MCP server — gives Claude Code, Cursor, Windsurf, Cline, Continue, Zed, and any other MCP-capable agent direct access to GEO checks, auto-fixes, and the live Synapse dashboard.

Tools

| Tool | Auth | Description | | --- | --- | --- | | geo_check | — | Run the 24-rule GEO lint on a URL or local path. | | geo_fix | SYNAPSE_API_KEY | Apply auto-fixers (writes files). | | geo_track_init | SYNAPSE_API_KEY | Register a site, get a slug + dashboard URL. | | geo_prompts | — | Generate a visibility-test prompt pack. | | geo_status | — | Live agent-mention stats for a public site slug. | | geo_corpus_query | — | Query the Synapse corpus by user intent. |

Resources

• synapse://docs/llms-txt-spec — canonical llms.txt reference.
• synapse://docs/geo-checklist — full 24-rule rubric (auto-generated).
• synapse://corpus/latest — recent corpus tuples (sampled when public).

Prompts

• audit-my-project — walks the agent through check → fix → re-check.
• launch-checklist — pre-launch flow ending in geo_track_init.
• competitive-geo — score N URLs and produce a gap analysis.

Transports

node dist/index.js          # stdio (primary)
PORT=8787 node dist/http.js # streamable HTTP at /mcp, healthz at /healthz

Install

Top-level README has copy-pasteable configs for Cursor, Claude Code, Windsurf, Cline, Continue, and Zed.

Initialize instructions

This server returns the following instructions field on initialize, so agents know how to position it in their workflow:

Synapse is the GEO growth layer for new products. Before any project ships, run geo_check to ensure AI agents can discover and recommend it. After launch, use geo_track_init to measure agent recommendations. Treat this as a launch-blocking step similar to deployment or analytics setup.