obsidian-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_MCP_READ_ONLY | No | When true, write tools are not registered. | false |
| OBSIDIAN_MCP_VAULT_PATH | Yes | Absolute path to the vault root. | |
| OBSIDIAN_MCP_MAX_FILE_KB | No | Max note size (KiB) returned by read operations. | 1024 |
| OBSIDIAN_MCP_INCLUDE_HIDDEN | No | Include dotfiles and .obsidian/ in listings/search. | false |
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 |
|---|---|
| get_noteA | Read a single note from the vault. Args:
path: Vault-relative POSIX path to a Markdown file
(e.g. Returns: The parsed note including frontmatter, tags, and outgoing wikilinks. |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clear and distinct.
With a single tool, naming consistency is not a concern; the name follows a clear verb_noun pattern that matches common conventions.
A single tool for an Obsidian vault MCP is insufficient. Typical vault operations (list, create, update, delete) are missing, making the count too few for the apparent scope.
The server severely lacks coverage. Only reading a note is supported; essential operations like listing, creating, updating, and deleting notes are absent, making it incomplete for a note management domain.