Taproot — the memory layer for your AI. MCP server that connects any AI client (Claude, ChatGPT, Cursor, Windsurf) to your notes.
Taproot — the memory layer for your AI. MCP server that connects any AI client (Claude, ChatGPT, Cursor, Windsurf) to your notes. The synapse obsidian mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
MCP server that connects any AI client — Claude, ChatGPT, Cursor, Windsurf — to your Obsidian vault. Save anything from anywhere, ask questions across your notes, keep the knowledge base your AI reads from.
Everything the assistant can do here goes through one of these:
taproot_plant — Onboarding — scans vault, presents options, configures Taproottaproot_till — Saves your vault preferencestaproot_seed — Save content from a URL or pasted texttaproot_status — Full vault overview with suggested actionstaproot_water — Process a source into organized pagestaproot_cultivate — Find and process all unprocessed sourcestaproot_harvest — Research a question across your knowledge basetaproot_prune — Health-check for broken links, orphans, gapstaproot_sow — Scaffold a new knowledge base from scratchgarden_read — Read any filegarden_plant — Create or update any filegarden_survey — List files in vault or subdirectorysynapse-obsidian on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
node -v) - An Obsidian vault or any folder of markdown files - Any MCP-compatible AI clientThis sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Synapse Obsidian's toolset — taproot_plant, taproot_till, taproot_seed and 11 more — is a fair guide to whether it matches your workflow. It is maintained by tomjrworks; 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 |
|---|---|
| taproot_plant | Onboarding — scans vault, presents options, configures Taproot |
| taproot_till | Saves your vault preferences |
| taproot_seed | Save content from a URL or pasted text |
| taproot_status | Full vault overview with suggested actions |
| taproot_water | Process a source into organized pages |
| taproot_cultivate | Find and process all unprocessed sources |
| taproot_harvest | Research a question across your knowledge base |
| taproot_prune | Health-check for broken links, orphans, gaps |
| taproot_sow | Scaffold a new knowledge base from scratch |
| garden_read | Read any file |
| garden_plant | Create or update any file |
| garden_survey | List files in vault or subdirectory |
| garden_forage | Full-text search |
| garden_measure | File counts and structure |
{
"mcpServers": {
"taproot": {
"command": "npx",
"args": ["-y", "synapse-obsidian", "/path/to/your/obsidian-vault"]
}
}
}Configuration as documented by the project. Restart the client after saving.
node -v) - An Obsidian vault or any folder of markdown files - Any MCP-compatible AI clientYour workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.