wtf is obsidian-vault-mcp?

obsidian-vault-mcp lets you run a copy of your Obsidian notes vault on a small always-on machine, like a Raspberry Pi, and make it readable and writable by AI tools over the network. Obsidian is a popular note-taking app, and this project connects it to MCP, a standard way for AI assistants and agents to read and write data from outside services. The setup uses two Docker containers built from the same image. One container keeps a local copy of your vault continuously synced with your Obsidian Sync account in the cloud. The other container reads and writes that same local vault folder and exposes it as an MCP server over HTTP on port 3000, so any MCP capable AI client on your network can connect to it. The two containers never talk to each other directly, they simply share the same folder on disk, which keeps the setup simple. To use it, you need Docker and Docker Compose installed, an Obsidian account with Obsidian Sync turned on for the vault you want to share, and an API key for the plugin the MCP server expects. Setup involves copying an example environment file, filling in your values, and running an interactive setup script that logs into Obsidian Sync, lists your remote vaults, and pulls down an initial copy of the one you choose. After that, starting both containers with one Docker Compose command brings the whole system online. The project is careful about security: your notes, configuration, and API keys are stored in folders that are excluded from version control by default, and the README repeats more than once that these should never be committed to git. If you rotate your API key, you simply update the environment file and restart the containers. The project is released under the MIT License.