Project Synapse is an MCP (Model Context Protocol) server that combines a Neo4j 2026.x graph database with an Obsidian Markdown wiki to create a
Project Synapse MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Project Synapse MCP directly instead of describing what you should do. Project Synapse is an MCP (Model Context Protocol) server that combines a Neo4j 2026.x graph database with an Obsidian Markdown wiki to create a persistent, compounding knowledge base. Raw text is processed through a semantic pipeline into.
Once Project Synapse MCP is connected, these are the calls the assistant has available:
sentence — transformers** (default) — runs on GPUPrerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverConfiguration — The Configuration tool exposed by this serverWorkflow — 1. Web research: wiki_fetch_url(url) → fetches, cleans, ingests, archives in one call 2. Manual clip: Drop into raw/, calldefuddle on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: WIKI_VAULT_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
pip install uv) - Obsidian with the Git community plugin - A GitHub repo for the wiki vault (can be private) - Node.js + defuddle (for web content fetching — see below)Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Project Synapse MCP's toolset — sentence, Prerequisites, Installation and 2 more — is a fair guide to whether it matches your workflow. It is maintained by angrysky56; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| sentence | transformers** (default) — runs on GPU |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
| Configuration | The Configuration tool exposed by this server. |
| Workflow | 1. **Web research**: wiki_fetch_url(url) → fetches, cleans, ingests, archives in one call 2. **Manual clip**: Drop into raw/, call wiki_ingest_raw(filename) → auto-archives after ingest 3. **Query**: query_knowledge (gra |
{
"mcpServers": {
"project-synapse": {
"command": "uv",
"args": [
"--directory",
"/path/to/project-synapse-mcp",
"run",
"python",
"-m",
"synapse_mcp.server"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
pip install uv) - Obsidian with the Git community plugin - A GitHub repo for the wiki vault (can be private) - Node.js + defuddle (for web content fetching — see below)| Variable | Description | Required |
|---|---|---|
| WIKI_VAULT_PATH | Filesystem location the server is allowed to use. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.