vault-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAULT_DIR | No | Root directory for markdown files | ./vault |
| VAULT_EMBEDDING_MODEL | No | Sentence-transformers model name. Enables semantic search when set |
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 |
|---|---|
| vault_writeA | Create or overwrite a note in the vault. Args: path: Note path relative to vault root (e.g. "skill/timeout-diagnosis") frontmatter: YAML metadata dict. Required fields: type, confidence. body: Markdown body content. Should start with "# Title". Returns warnings if the note has structural issues. |
| vault_write_batchA | Write multiple notes atomically in a single transaction. Args: entries: List of dicts, each with "path", "frontmatter", "body" keys. All notes are written together — if one fails, none are committed. |
| vault_readA | Read a note from the vault. Returns its frontmatter and body. Args: path: Note path (e.g. "concept/connection-pooling") |
| vault_editA | Apply an incremental edit to an existing note without rewriting the full content. Args: path: Note path to edit. operation: One of "replace_string", "set_frontmatter", "replace_section", "append_section". params: Operation-specific parameters: - replace_string: {"old": "...", "new": "..."} - set_frontmatter: {"field": "value", ...} (merge update) - replace_section: {"heading": "## Section", "body": "new content"} - append_section: {"heading": "## Section", "content": "appended text"} Returns warnings if the edit introduces structural issues. |
| vault_deleteA | Delete a note and remove it from all indexes. Args: path: Note path to delete. |
| vault_renameA | Rename or move a note. All [[backlinks]] in other notes are rewritten automatically. Args: old_path: Current note path. new_path: New note path. |
| vault_listA | Browse notes under a path. Args: path: Directory path (e.g. "skill"). Use "" for vault root. depth: How many levels deep to list (default 1). type_filter: Only return notes of this type (e.g. "skill", "concept"). |
| vault_searchA | Search the vault by keyword, semantic similarity, or both. Args: query: Search query text. filters: Optional filters: {"type": "skill", "confidence": "fact", "tags": ["db"]}. mode: "keyword" (FTS5), "semantic" (vector), or "hybrid" (both, default). limit: Max results (default 10). Returns rich results with path, score, title, type, confidence, tags, and snippet. |
| vault_backlinksA | Find all notes that contain a [[wikilink]] to the given path. Args: path: Target note path. |
| vault_traverseA | Explore the link graph around a note via BFS traversal. Args: start: Starting note path. depth: How many hops to follow (default 2). direction: "forward" (outgoing links), "backward" (incoming), or "both". Returns nodes with depth and directed edges (source → target). |
| vault_lintA | Check vault health: find dead [[wikilinks]] and orphan notes with no connections. |
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
Tools are mostly distinct with clear purposes, but vault_backlinks and vault_traverse (backward direction) both return incoming links, which could cause misselection. However, descriptions clarify the difference: backlinks is a direct lookup, while traverse explores the graph with depth.
All tools share the vault_ prefix, and most follow a verb pattern (write, read, edit, delete, list, search, lint, traverse). However, vault_backlinks and vault_write_batch deviate from the verb-only convention, making the set slightly inconsistent.
11 tools cover a complete note management workflow: CRUD, batch, search, list, lint, and graph exploration. The number is well-scoped, neither overwhelming nor thin.
The tool set provides full coverage of the vault lifecycle: create, read, update, delete, rename, batch operations, search, and health/link analysis. There are no obvious dead ends or missing core operations.