Obsidian MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_PORT | No | HTTP server port (when using http transport) | 3000 |
| MCP_TRANSPORT | No | Transport mode: stdio or http | stdio |
| OBSIDIAN_VAULT_PATH | Yes | Path to Obsidian vault (required) |
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 |
|---|---|
| write_session_reportA | Write a session report to the Obsidian vault. Use this at the end of coding sessions, after completing significant tasks, or when wrapping up work phases. The report will be saved with proper frontmatter and timestamps. |
| write_noteC | Write or create a note in the Obsidian vault. Can be used for documentation, meeting notes, ideas, or any other content. |
| append_to_noteA | Append content to an existing note. Useful for adding entries to running logs, daily notes, or accumulating information. |
| append_to_daily_noteA | Append content to today's daily note. Creates the daily note if it doesn't exist. |
| search_notesB | Search notes in the vault by content, tags, or folder. |
| read_noteC | Read the content of a specific note. |
| list_recent_notesB | List recently modified notes in the vault. |
| find_backlinksC | Find all notes that link to a specific note. |
| create_todoC | Create or add a TODO item. Can create a new TODO note or append to existing TODO list. |
| link_notesC | Get suggestions for notes that might be related to given content or keywords. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| README | Last modified: 2026-01-20T17:13:04.703Z |
TDQS
Scored across 10 tools
Most tools have distinct purposes, but there is some overlap between 'append_to_daily_note' and 'append_to_note' that could cause confusion, as both handle appending content. Additionally, 'create_todo' and 'write_note' might be ambiguous for creating new notes, though their specific focuses help differentiate them.
The naming follows a consistent verb_noun pattern throughout, such as 'append_to_daily_note', 'read_note', and 'search_notes'. Minor deviations like 'find_backlinks' (which could be 'list_backlinks') and 'link_notes' (which suggests linking but is for suggestions) slightly break the pattern, but overall it's highly readable and predictable.
With 10 tools, this server is well-scoped for managing an Obsidian vault, covering key operations like reading, writing, appending, searching, and listing notes. Each tool serves a clear purpose, and the count aligns well with typical MCP server ranges, avoiding bloat or thinness.
The toolset provides strong coverage for core Obsidian workflows, including CRUD operations (create, read, write, append) and utilities like search and backlinks. Minor gaps exist, such as the lack of update or delete operations for notes, which might require workarounds, but agents can handle most tasks effectively with the available tools.