Vault MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAULT_ROOT | No | Path to the folder of Markdown notes to serve. Can also be set with the --vault command-line option; without either, the bundled toy-vault/ is served. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Read-only access to a folder of Markdown notes. Paths are relative to the vault root. There are no tools that create, change or delete files.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_pagesB | List every Markdown page in the vault with its title. Args: folder: Optional subfolder to list, relative to the vault root (for example "lca"). |
| read_pageA | Return the full Markdown text of one page. Args: path: Path relative to the vault root, as returned by list_pages (for example "lca/Allocation.md"). |
| searchA | Find pages containing all the words in the query (case-insensitive). Results are ranked by how often the words occur and show up to three matching lines. Args: query: One or more words; a page must contain every word to match. limit: Maximum number of pages to return (1 to 50). |
| broken_linksA | List [[wikilinks]] that point to a page that does not exist in the vault. Links inside code blocks and inline code are ignored. Each result gives the page the link is on, the line number and the missing target. |
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 4 tools
Each tool has a clearly distinct purpose: listing pages, reading a page, full-text searching, and finding broken wikilinks. Although list_pages and search both help locate pages, one is structural and the other content-based, so an agent can easily choose between them.
Two tools follow a verb_noun pattern (list_pages, read_page), but 'search' is a bare verb and 'broken_links' is a noun phrase. The mixed conventions are still readable, but they prevent a fully predictable pattern.
Four tools are well-scoped for a read-only Markdown vault interface. Each tool covers a distinct operation and none feels redundant or extraneous.
The surface covers listing, reading, searching, and link validation, but there are no write operations such as create_page, update_page, or delete_page. If the vault is intended to be editable, this is a notable gap; if strictly read-only, it is closer to complete.