mcp-obsidian
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_API_KEY | Yes | API key/token from the Local REST API plugin settings. | |
| OBSIDIAN_BASE_URL | Yes | The base URL of the Obsidian Local REST API plugin (e.g. https://127.0.0.1:27124). | |
| NODE_TLS_REJECT_UNAUTHORIZED | No | Set to '0' to disable TLS verification when using the local self-signed certificate. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_notesB | Search notes in the Obsidian vault using Obsidian's search query syntax. Returns matching paths, scores, and snippets. |
| get_noteA | Read the full markdown content of a note by its vault-relative path. |
| create_noteA | Create a new note in the vault with markdown content. Refuses to overwrite an existing note unless overwrite=true. |
| update_noteA | Replace the entire content of an existing note with new markdown content. |
| append_noteA | Append (or prepend) markdown content to an existing note without replacing it. |
| delete_noteA | Permanently delete a note from the vault. |
| list_directoryA | List files and folders under a vault directory. Use directory='' or '/' for the vault root. |
| open_noteA | Open a note in the Obsidian app window by its vault path. |
| list_commandsA | List all available Obsidian commands that can be executed. |
| execute_commandA | Execute an Obsidian command by its id (use list_commands first). |
| get_active_noteA | Get the markdown content of the currently active note in Obsidian. |
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 11 tools
Each tool targets a distinct operation: search, read by path, read active note, create, replace, append, delete, list directory, open in UI, and command management. Even similar tools like get_note and get_active_note are clearly separated by how the note is selected.
All tool names consistently use lowercase snake_case with a verb_noun pattern (search_notes, get_note, create_note, list_commands, execute_command). There are no style deviations or ambiguous generic names.
11 tools is well-scoped for a note management server: it covers search, CRUD, directory listing, UI actions, and Obsidian command execution without bloat or redundancy.
The surface provides full lifecycle coverage for notes—create, read, update, append, delete—plus search, directory browsing, opening notes, and executing commands. No critical dead ends for typical Obsidian automation workflows.