Obsidian Tools 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 |
|---|---|
| create_noteA | Create a new note in the Obsidian vault. Supports nested folder creation. |
| delete_noteC | Delete a note from the Obsidian vault |
| update_noteC | Update/replace the entire content of an existing note |
| append_to_noteC | Append content to the end of an existing note |
| prepend_to_noteA | Prepend content to the beginning of an existing note (after frontmatter if present) |
| rename_noteC | Rename or move a note to a new location |
| read_noteC | Read the content of a single note |
| search_notesC | Search for notes by name pattern (case-insensitive, supports regex) |
| search_contentC | Search for notes containing specific text in their content |
| list_folderB | List all notes and subfolders in a folder |
| get_tagsC | Get all tags used in a note |
| get_linksC | Get all internal links (wikilinks and markdown links) from a note |
| get_backlinksA | Find all notes that link to a specific note |
| insert_at_headingC | Insert content under a specific heading in a note |
| update_frontmatterC | Update or add frontmatter (YAML) properties in a note |
| create_from_templateC | Create a new note from an existing template 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 16 tools
Every tool has a clearly distinct purpose targeting specific operations on notes or vault structure. For example, 'append_to_note' and 'prepend_to_note' handle content addition at different positions, while 'search_content' and 'search_notes' differentiate between text and name searches, avoiding overlap.
All tools follow a consistent verb_noun pattern with snake_case, such as 'create_note', 'delete_note', 'read_note', and 'update_note'. This uniformity makes the tool set predictable and easy to navigate for agents.
With 16 tools, the server provides comprehensive coverage for Obsidian vault management, including CRUD operations, content manipulation, search, and metadata handling. This count is well-scoped for the domain, offering a rich set without being overwhelming.
The tool set offers complete lifecycle coverage for note management, including creation, reading, updating, deletion, renaming, content editing, frontmatter updates, linking, tagging, and search. No obvious gaps exist; agents can perform all essential Obsidian workflows seamlessly.