Obsidian MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| readNoteC | Read the contents of a specific note |
| readActiveNoteB | Read the contents of the current active note |
| listNotesA | Recursively lists files and folders in the entire Vault or under a specified folder and returns the result as a tree-format string |
| patchNoteC | Inserts content into an existing note relative to a heading, block reference, or frontmatter field. |
| searchWithJsonLogicB | Search Obsidian notes using JsonLogic format queries. Using logical conditions expressed in JSON, you can flexibly filter note metadata and content. Suitable for programmatically generated searches, allowing complex conditions to be expressed in a structured way. |
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 5 tools
Most tools have distinct purposes: listNotes for browsing, readNote/readActiveNote for reading, patchNote for editing, and searchWithJsonLogic for querying. However, readNote and readActiveNote could potentially be confused as they both read notes, though one targets a specific note and the other the active note, which is clarified in their descriptions.
The naming is mixed: listNotes, readNote, and searchWithJsonLogic follow a verb_noun pattern, but patchNote uses a verb_noun format with a different verb style, and readActiveNote includes an adjective, breaking consistency. While readable, it lacks a uniform convention across all tools.
With 5 tools, the count is reasonable for an Obsidian vault management server, covering core operations like listing, reading, editing, and searching notes. It's slightly lean but functional, as it includes essential CRUD-like actions without being overwhelming.
The tool set covers reading, editing, listing, and searching notes, but lacks explicit create and delete operations for notes, which are common in file-based systems. This creates gaps in full lifecycle management, though patchNote can modify existing notes and agents might work around missing create/delete by other means.