Obsidian MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_VAULT_PATH | No | The vault location. If unset, it defaults to ~/Obsidian. | ~/Obsidian |
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 |
|---|---|
| obsidian_read_noteA | Read the full markdown content of a note in the vault. Path is relative to the vault root; the .md extension is optional. Read-only. |
| obsidian_write_noteA | Create a new note or overwrite an existing one. Refuses to overwrite unless overwrite=true. Parent folders are created automatically. |
| obsidian_append_to_noteA | Append markdown to the end of a note, creating it if it does not exist. A newline is inserted before appended content when the note already has content. |
| obsidian_list_notesA | List markdown notes in the vault, optionally scoped to a folder. Hidden folders (.obsidian, .git) are skipped. Read-only. |
| obsidian_search_vaultA | Case-insensitive full-text search across note bodies. Returns matching file path, line number, and the matching line. Read-only. |
| obsidian_read_frontmatterA | Parse and return the YAML frontmatter of a note as structured data, plus a short body preview. Read-only. |
| obsidian_resolve_wikilinksA | Extract [[wikilinks]] from a note and resolve each to an actual vault file by basename. Handles [[Note|alias]] and [[Note#heading]]. Unresolved links return target=null. Read-only. |
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 7 tools
Each tool has a clearly distinct purpose: reading, writing, appending, listing, searching, reading frontmatter, and resolving wikilinks. No overlap or ambiguity between tools.
All tools follow the consistent pattern 'obsidian_verb_noun' in snake_case, e.g., obsidian_read_note, obsidian_write_note. Naming is predictable and uniform.
7 tools is a reasonable count for a note-taking vault server. It covers essential operations, though a delete note tool is missing, which slightly reduces appropriateness.
The set covers reading, writing, appending, listing, searching, frontmatter parsing, and wikilink resolution. Missing delete note functionality is a minor gap but core workflows are achievable.