Always-on MCP server for Obsidian vaults via LiveSync
obsidian-sync-mcp by Es617 is an MCP server that exposes Obsidian vaults to AI agents for remote access. It lets MCP-compatible models read, search, create, and edit notes through a CouchDB-backed Self-hosted LiveSync integration, maintaining access from mobile and web clients when a desktop is offline. Includes always-on CouchDB access for LiveSync, End-to-End Encryption support, and flexible deployment on Fly.io, Docker, or local Node.js environments, aimed at Obsidian power users who need AI-driven note workflows.
What tasks can you actually use it for?
The server serves as a bridge between AI assistants and an Obsidian vault, exposing vault content for programmatic reading, searching, creation, and editing of notes. That enables workflows such as mobile AI note-taking, automated knowledge management, and remote query-and-update agents. The tool accepts MCP requests from compatible clients and maps them to the vault through the Self-hosted LiveSync CouchDB backend, letting external models interact with the note corpus even when the desktop app is not running.
How reliable is remote access and note editing?
Reliability depends on the health of the sync backend and deployment environment. The implementation uses a CouchDB-backed LiveSync store to provide continuous availability, which removes the need for a local client to be open for remote access. Edits and searches reflect the state of the synced database; users should expect behavior to follow their existing LiveSync consistency and replication patterns, and plan verification steps for automated edits.
What do you need to run and connect it?
Connectivity requires MCP-compatible clients and a supported deployment target. The server works with MCP-compliant clients such as Claude Desktop or Cursor and can run on Fly.io, Docker, or a local Node.js/Bun environment. It is optimized for setups that use the Self-hosted LiveSync plugin and CouchDB, and it also provides a local filesystem mode for simpler direct-vault connections when a self-hosted sync backend is not in use.
Is deployment and workflow integration practical for Obsidian power users?
The tool is aimed at technically comfortable power users who operate self-hosted syncs. Early adopters note it solves the common local-only limitation for AI integrations, making vaults accessible from mobile and web agents. The developer maintains the project on GitHub, and the deployment flexibility supports integration into existing self-hosted stacks. Users should allocate time to configure the server and validate synchronization behavior before relying on automated agents for critical edits.
Who should adopt this server and how to approach it
This server suits Obsidian users who run or are willing to run self-hosted sync infrastructure and who need uninterrupted AI access to their notes. Expect a setup-and-validate workflow: deploy the server, confirm sync integrity, and review AI-made edits before merging them into your primary vault. For users comfortable with basic server administration, the tool provides a practical route to remote AI-driven note interactions.
Pros
Always-on vault access without the desktop app running
Supports read, search, create, and edit operations on notes
End-to-End Encryption support for private data handling
Deployable on Fly.io, Docker, or local Node.js environments
Cons
Optimized for Self-hosted LiveSync; less effective without it
Requires server deployment and basic sysadmin skills
Behavior tied to sync health of the CouchDB backend
Laws concerning the use of this software vary from country to country. We do not encourage or condone the use of this program if it is in violation of these laws. Softonic may receive a referral fee if you click or buy any of the products featured here.
