Obsidian MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_VAULT_PATH | Yes | 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
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 |
|---|---|
| read_noteA | Read the content of a specific note |
| search_notesC | Search for notes by title, content, or tags |
| create_noteB | Create a new note in the vault |
| summarize_noteB | Generate a summary of a note's content |
| organize_noteA | Move a note to a different folder |
| add_tagsA | Add tags to a note's frontmatter |
| get_most_valuable_notesA | Get a list of the most valuable notes for today based on recency, length, and organization |
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: creating, reading, searching, summarizing, moving, tagging, and recommending notes. There is no overlap or ambiguity between them.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_note, read_note, add_tags). Even get_most_valuable_notes fits the verb-noun convention with a descriptive adjective.
Seven tools is a well-scoped count for an Obsidian vault management server, covering common operations without redundancy or bloat. Each tool earns its place.
The toolset covers create, read, search, summarize, organize, and tag operations, but lacks the ability to edit note content or delete notes. These are notable gaps in the note lifecycle, though agents can work around some limitations by using organize_note and add_tags for metadata changes.