obsidian-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_VAULT_PATH | No | Path to the Obsidian vault root. The vault must already exist. | ~/Documents/Obsidian Vault |
| OBSIDIAN_PROJECTS_DIR | No | Directory name (relative to the vault root) where project subfolders are created. | Projects |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_projectA | Report which project folder notes will go to, and how that was decided. Use this to check the inference before writing. |
| write_noteA | Create a note in the project's vault folder. Refuses to clobber an existing note unless overwrite is true. Creates the project folder on first write. |
| read_noteA | Read a note's full contents from the project's vault folder. |
| append_noteA | Append markdown to the end of a note, creating it if absent. Use this for running logs instead of rewriting the whole note. |
| list_notesB | List note paths in the project's folder, or across the whole vault. |
| search_notesA | Case-insensitive text search over note contents, returning matching lines with their note path and line number. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool serves a clearly distinct purpose: resolving project routing, writing, reading, appending, listing, and searching notes. Even write_note and append_note are well differentiated by their overwrite and append semantics.
All tool names follow a consistent verb_noun snake_case pattern: resolve_project, write_note, read_note, append_note, list_notes, search_notes. This makes the API predictable and easy to navigate.
Six tools is a well-scoped set for an Obsidian note management server. Each tool covers a distinct operation without redundancy or bloat.
The core note lifecycle is well covered: create/write, read, append, list, and search. Missing delete, move, or rename operations are noticeable gaps, but agents can still accomplish most note workflows.