Obsidian Sync Mcp
Point your agent at an Obsidian vault—local folder or CouchDB LiveSync—so specs, research, and launch notes stay in sync with coding sessions.
Overview
io.github.es617/obsidian-sync-mcp is a MCP server for the Idea phase that gives AI agents read and write access to your Obsidian vault via local files or CouchDB LiveSync.
What is this MCP server?
- Filesystem mode via VAULT_PATH for direct local Obsidian vault access
- CouchDB mode with COUCHDB_URL, credentials, database, and LiveSync E2E passphrase alignment
- Streamable-http MCP at http://localhost:8787/mcp (npm package obsidian-sync-mcp 0.5.2)
- Supports Self-hosted LiveSync workflows for multi-device builders
- Separates local vault editing from encrypted remote replica semantics
- npm package obsidian-sync-mcp version 0.5.2
- Streamable-http MCP URL documented at localhost:8787/mcp
- 6 named environment variables for vault path and CouchDB LiveSync credentials
Community signal: 21 GitHub stars.
What problem does it solve?
Your best product research lives in Obsidian while the agent in your IDE cannot reliably query or update those markdown files.
Who is it for?
Obsidian-first indie builders who document ideas, validation, and specs in markdown and want one MCP bridge for local or self-hosted sync.
Skip if: Teams on Notion-only stacks, or builders who refuse to run a local MCP HTTP listener near their notes.
What do I get? / Deliverables
After registration, the agent can ground plans and answers in vault notes you already maintain, including synced replicas when CouchDB mode is configured.
- Agent-visible Obsidian note search and updates
- Optional CouchDB-backed sync consistent with LiveSync
- Localhost MCP endpoint for long-running vault sessions
Recommended MCP Servers
Journey fit
Research and decision logs usually start in idea when you capture competitors, audience, and open questions before you commit to a build. Vault read/write is foundational research infrastructure: the agent grounds answers in your own notes, not stale chat context.
How it compares
Vault-backed MCP connector, not an Obsidian plugin marketplace theme or a generic filesystem MCP without LiveSync awareness.
Common Questions / FAQ
Who is io.github.es617/obsidian-sync-mcp for?
It is for solo builders who keep strategy, research, and build logs in Obsidian and want Claude Code, Cursor, or similar agents to read and update that corpus.
When should I use io.github.es617/obsidian-sync-mcp?
Use it from early research through scoping and documentation whenever chat context should cite your vault instead of re-uploading notes each session.
How do I add io.github.es617/obsidian-sync-mcp to my agent?
Install obsidian-sync-mcp from npm, start the server with VAULT_PATH for local mode or CouchDB env vars for LiveSync, add http://localhost:8787/mcp to your MCP client, and verify passphrase matches your plugin in CouchDB mode.