Exposes Markdown documentation from a project's /docs directory as MCP resources, providing AI agents with stable and up-to-date context to reduce hallucinations.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SynapseSummarize the project conventions from the /docs folder"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Synapse
Project-agnostic MCP server that turns your /docs folder into a shared “brain” for AI agents.
Synapse exposes your project’s documentation as Model Context Protocol (MCP) resources, so any MCP-capable client (e.g. Cursor, Claude Desktop) can use them as stable, up-to-date context. The goal is to reduce hallucinations and keep agents aligned with your project’s vision, conventions, and goals.
Why Synapse?
Agnostic — Works with any repo. No product-specific logic; you bring the docs, Synapse serves them.
Convention over config — Put Markdown in
/docsat the project root; the server discovers and exposes it.OSS — MIT license. You can use, change, and contribute.
Status
Early stage. The repo has the basic TypeScript + MCP SDK setup and a stub entrypoint. Next steps:
Implement MCP resources: list and read all
.mdfiles under/docs(URIs likesynapse://docs/...).Optional config (e.g. custom docs path, handoffs) later.
Requirements
Node.js ≥ 18
pnpm (recommended) or npm
Installation
# Clone the repo
git clone https://github.com/gabriel-romero-poza/synapse-mcp.git
cd synapse-mcp
# Install dependencies
pnpm install
# Build
pnpm buildOr use as a dependency in another project:
pnpm add synapse-mcp # when published to npm
# or from git
pnpm add github:gabriel-romero-poza/synapse-mcpUsage
Run the server (stdio transport). The project root is the directory from which the MCP client runs the process (e.g. your repo root when Cursor starts Synapse).
pnpm start
# or after npm/pnpm link / global install:
synapseEnvironment (optional):
Variable | Description |
| Override project root (default: |
Cursor
Settings → Tools & MCP → Add new MCP server
Add a server with:
Name:
synapse(or any name)Type:
commandCommand:
nodeArguments:
path/to/synapse/dist/index.js
(orpnpm exec synapseif run from the synapse repo / a workspace that has it)
Ensure the server is started with cwd = your project root (where
/docslives).
(Exact Cursor UI may vary; refer to Cursor MCP docs.)
Project layout
synapse-mcp/
├── .cursor/rules/ # Cursor rules (commits, TypeScript, agentic workflow)
├── .github/ # PR template, issue templates
├── docs/ # Project vision and design (source of truth)
├── src/
│ └── index.ts # Entrypoint (MCP server stub)
├── AGENTS.md # Context for AI agents
├── CONTRIBUTING.md # Commit conventions, PR process, guardrails
├── package.json
├── tsconfig.json
├── pnpm-lock.yaml
├── README.md
└── LICENSEContributing
Contributions are welcome. See CONTRIBUTING.md for commit conventions (Conventional Commits), PR process, and guardrails. Open an issue for bigger changes; use pull requests for patches and small features. Keep the scope agnostic: no product-specific logic inside Synapse; conventions and optional config only.
License
MIT. See LICENSE.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.