Obsidian MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_VAULT_PATH | Yes | Absolute path to your Obsidian vault |
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 |
|---|---|
| query_vaultC | Process natural language queries about your Obsidian vault |
| search_notesC | Search for notes by filename or content |
| get_noteC | Get the full content of a specific note |
| get_backlinksC | Get all notes that link to a specific note |
| write_noteC | Write or overwrite a note with new content |
| create_noteC | Create a new note with frontmatter and content |
| append_to_noteC | Append content to an existing note |
| update_note_sectionC | Update a specific section of a note by heading |
| list_directoriesC | List directories and files in vault or specific directory |
| intelligent_searchC | Advanced search using link analysis, tag hierarchies, and structural context |
| guided_pathC | Generate a narrative tour through linked notes starting from a seed note |
| audit_recent_notesA | Highlight recently modified notes that are missing required frontmatter or structure |
| contextual_companionsC | Suggest adjacent notes related to a topic or seed note based on links, keywords, and recency |
| fresh_energyB | Find recently updated notes that lack backlinks or link coverage so you can integrate them |
| initiative_bridgeC | Identify initiative-tagged notes with outstanding tasks so nothing slips between systems |
| pattern_echoB | Search for notes that reuse a phrasing, bullet pattern, or framework fragment |
| synthesis_readyC | Flag clusters of notes that reference each other but lack a synthesis/summary note |
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 17 tools
Most tools have distinct purposes, such as 'create_note' for creation, 'get_note' for retrieval, and 'append_to_note' for updates, with clear boundaries. However, some overlap exists between 'search_notes' and 'intelligent_search', where the latter's advanced features might cause confusion if an agent needs basic search functionality, but descriptions help differentiate them.
The naming is mixed, with some tools using verb_noun patterns like 'create_note' and 'update_note_section', while others use more descriptive phrases like 'contextual_companions' and 'synthesis_ready'. This inconsistency makes the set less predictable, but the names remain readable and convey intent, avoiding chaotic styles.
With 17 tools, the count is slightly high but reasonable for managing an Obsidian vault, covering operations from basic CRUD to advanced analytics and workflow management. It feels comprehensive without being overwhelming, though it borders on heavy for a note-taking domain, with some tools possibly overlapping in functionality.
The tool set provides complete coverage for note management, including creation, retrieval, updating, and deletion (implied via overwrite), along with advanced features like search, linking analysis, and workflow integration. There are no obvious gaps; agents can perform full lifecycle operations and complex queries without dead ends.