Obsidian Nexus

What it is

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.

What you get

• 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

Requirements

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.

Setup effort

Build from source — git clone https://github.com/nkriman/obsidian-nexus

Tools you get

6 tools named in the project's documentation.

Where it runs

The documented client runs the server on your machine.