vault-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_MCP_VAULT_PATH | No | Path to vault root | . |
| VAULT_BRIDGE_MAX_FILE_SIZE | No | Max file size for operations | 10MB |
| VAULT_BRIDGE_FOLLOW_SYMLINKS | No | Follow symlinks | false |
| VAULT_BRIDGE_DEFAULT_ENCODING | No | Text encoding | utf-8 |
| VAULT_BRIDGE_INDEX_FRONTMATTER | No | Parse YAML frontmatter | true |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_noteB | Read a note from the Obsidian vault. |
| write_noteB | Write a note to the Obsidian vault. |
| list_notesC | List notes in the Obsidian vault. |
| search_notesB | Search notes in the Obsidian vault using regex. |
| search_frontmatterB | Search notes by frontmatter key/value. |
| get_daily_noteB | Get or create a daily note. |
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 6 tools
The tools are mostly distinct: read/write/list/search are clearly separated, and search_notes vs search_frontmatter are differentiated by search type. However, search_notes and search_frontmatter could be confused if an agent doesn't read carefully, though the descriptions clarify the distinction.
Tool names follow a consistent verb_noun pattern (read_note, write_note, list_notes, search_notes, search_frontmatter, get_daily_note). The only minor deviation is get_daily_note, which uses 'get' instead of 'read' and includes a specific noun, but it's still predictable.
Six tools is well-scoped for a vault-bridge server. Each tool covers a distinct core operation for interacting with an Obsidian vault, and none feel redundant or excessive.
The tool set covers the core note lifecycle: read, write, list, search, and daily note handling. Missing operations like delete_note or rename_note are minor gaps since agents can work around them, but the surface is largely complete for typical vault interactions.