vault-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAULT_MCP_ROOT | No | Root of the vault to serve - change to point to any other vault. | ~/vault |
| VAULT_MCP_BLOCKED_FOLDERS | No | CSV of extra top-level folders to block for read/write, in addition to .git/.obsidian/.trash (always blocked). | |
| VAULT_MCP_WRITE_MAX_CHARS | No | Maximum content size in write_note (1-200000). | 20000 |
| VAULT_MCP_SEARCH_MAX_RESULTS | No | Limit of search results (1-500). | 50 |
| VAULT_MCP_SEARCH_CONTEXT_CHARS | No | Size of the snippet returned per match (20-1000). | 120 |
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 |
|---|---|
| search_notesD | – |
| search_by_tagD | – |
| get_backlinksD | – |
| read_noteD | – |
| list_notesD | – |
| list_foldersD | – |
| get_note_metadataD | – |
| write_noteD | – |
| rename_noteD | – |
| move_noteD | – |
| delete_noteD | – |
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 11 tools
Most tools target distinct operations: search, read, write, rename, move, delete, metadata. The only potential overlap is between search_notes and search_by_tag, but they are differentiated by search mechanism (content vs tag).
All tool names follow a consistent verb_noun pattern in lowercase snake_case (e.g., search_notes, read_note, list_folders, delete_note). This is highly predictable and uniform.
With 11 tools, the server is well-scoped for note management. It covers essential operations without redundancy or unnecessary bloat.
The toolset provides comprehensive note lifecycle coverage (create, read, update, delete), plus search, backlinks, metadata, and folder listing. Minor omissions like an explicit tag listing or folder contents are acceptable workarounds.