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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| obsidian_configureA | Configure the Obsidian vault path and settings. Run this first to set up your vault. |
| obsidian_readB | Read the contents of a note from the Obsidian vault. Returns the full markdown content. |
| obsidian_writeA | Create or overwrite a note in the Obsidian vault. Creates parent folders if needed. |
| obsidian_appendA | Append content to an existing note, or create it if it doesn't exist. Prefer this over obsidian_write when adding to existing project documentation. |
| obsidian_searchA | Search for notes containing specific text. Returns matching file paths and snippets. Use before creating new notes to find existing relevant documentation. |
| obsidian_listB | List notes and folders in the vault. Use at the start of sessions to discover project folders and available documentation. |
| obsidian_dailyA | Read or append to today's daily note. Creates the note if it doesn't exist. Use this at the end of work sessions to document accomplishments, decisions, and open questions. |
| obsidian_statusA | Show current configuration and vault status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| session-start | Review context from Obsidian before starting work. Checks daily notes, project folders, and recent activity. |
| session-end | Document what was accomplished during this work session. Updates daily note and project notes. |
| project-checkin | Review and update project documentation in Obsidian. Read existing notes and append new findings. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: append vs write, daily for daily notes, list for browsing, read for viewing, search for finding, configure/status for setup. No overlapping functionality.
All tools follow the 'obsidian_<verb>' pattern in snake_case, creating a predictable and uniform naming scheme. Even 'daily' fits as a verb-like noun.
With 8 tools, the set covers all essential note-taking operations (CRUD, search, daily notes, configuration) without excess or deficiency.
The tool set covers create, read, update (append), search, list, and configuration. However, it lacks a delete or trash operation, which is a minor gap for full lifecycle management.