obsidian-knowledge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_VAULT_PATH | Yes | The absolute path to the 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| obsidian_search_notesA | Search Markdown notes using deterministic phrase, token, and Chinese 2-gram ranking. Use this first for topical discovery or paraphrased questions. Results include vault-relative
paths, headings, excerpts, tags, scores, and pagination metadata. The tool is local and
read-only.
If results are broad, add |
| obsidian_read_noteA | Read one note or one heading after discovering its path. Paths are resolved inside the configured vault, and traversal outside it is rejected. Use an exact heading to keep long notes concise. Returns content, tags, truncation state, and source path. |
| obsidian_list_notesA | Browse note titles and paths with optional folder and tag filters. Use when you know the folder or tag but not the exact note name. Results are sorted by path and
paginated; continue with |
| obsidian_find_backlinksA | Find notes that link to a target through Obsidian Use after reading a note to discover related decisions, meetings, or follow-up pages. Matching supports note names, vault-relative paths, aliases, and heading anchors. It never edits the graph. |
| obsidian_vault_statsA | Return a compact health snapshot of the configured vault. The response includes note count, wikilink count, distinct tag count, and top tags. Use it to understand vault size before browsing; do not use it for note content retrieval. |
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
Each tool serves a clearly distinct purpose: reading a specific note, searching content, browsing by folder/tag, finding backlinks, and viewing vault stats. There is no meaningful overlap between tools, and the descriptions reinforce when to use each one.
Tool names follow a consistent snake_case pattern with the common `obsidian_` prefix, using clear action-noun combinations like `read_note`, `search_notes`, and `list_notes`. `vault_stats` is the only name that deviates from the verb-object pattern, but the convention remains predictable overall.
Five tools is a well-scoped set for an Obsidian knowledge retrieval server. Each tool adds a distinct capability without redundancy, and the count is neither too thin nor bloated for the domain.
For a read-only knowledge retrieval surface, the tool set covers discovery, browsing, targeted reading, relationship exploration via backlinks, and vault-level stats. Search and list together handle navigation, while backlinks cover knowledge graph traversal; no obvious retrieval workflow is missing.