Because it works on the vault directly rather than through a plugin API, everything it writes is a normal Markdown file that Obsidian and its plugins keep treating as their own — and nothing is lost if you stop using this. The write access is real write access: `write_note` overwrites, so the backup toggle in the config is worth turning on before pointing an agent at notes you care about.
An MCP server that operates on an Obsidian vault as files on disk. You give it a vault path and it can read any note, write or append to one, list notes by directory, and search across the whole vault with context excerpts. It ships with a folder structure aimed at family and daily-note organisation, created automatically.
- `read_note` — read any note by path
- `write_note` — create or overwrite a note, with folders created as needed
- `append_to_note` — add a section to an existing note rather than rewriting it
- `list_notes` — list everything, or just one directory
- `search_notes` — search content across the vault and get matching excerpts with context
- `vault_status` — check the vault configuration and stats
- Templates for the note paths — daily notes, per-person notes and theme notes — configurable in `config.yaml`
No API key: the file operations are local and the model doing the thinking is the client's. A clone plus `npm install`, then set `vault_path` in `config.yaml` to your vault's absolute path and point the client at `src/index.js`. Optional settings there include the people list, the path templates, and toggles for auto-creating folders, daily notes and backups of modified files. The package is `obsidian-nexus` (1.0.0 in package.json). Obsidian itself may hold file locks; the troubleshooting section covers the permission errors that produces. MIT licensed.