VaultPilot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAULT_ROOT | Yes | Path to your Obsidian vault | |
| VAULTPILOT_HTTP | No | Set to 1 to enable HTTP transport | |
| VAULTPILOT_TOKEN | No | Bearer token used for HTTP authentication when VAULTPILOT_HTTP is enabled | |
| VAULTPILOT_READONLY | No | Set to 1 to hide write tools |
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 |
|---|---|
| notes_readB | Read a markdown note from the vault by relative path. |
| search_queryC | Full-text search markdown notes in the vault. |
| search_by_tagC | Search notes containing a tag (with or without leading #). |
| capture_quickC | Create a quick capture note in 00-Inbox. |
| capture_learningB | Create a learning note with a knowledge/* tag. Topic 'fastmcp' writes to 03-Knowledge/FastMCP. |
| capture_workB | Create a work note in Inbox with #work/ tag for Auto Note Mover. |
| capture_distillB | Summarize long chat/source text via client LLM sampling, then save as a vault note. kind: learning | work | quick topic_or_domain: for learning use topic (e.g. fastmcp); for work use domain (e.g. auth). |
| daily_appendB | Append a bullet to today's daily note (default section: Notes). |
| bug_startC | Start a bug-session note in Inbox and remember it as the active bug. |
| bug_appendB | Append to a bug note section (Timeline, Hypothesis, Fix, Symptom, Root cause). Uses active bug if path omitted. |
| bug_closeA | Close the active (or given) bug note after confirmation. Writes Fix + Root cause and sets status=fixed. |
| list_resourcesA | List all available resources and resource templates. Returns JSON with resource metadata. Static resources have a 'uri' field, while templates have a 'uri_template' field with placeholders like {name}. |
| read_resourceA | Read a resource by its URI. For static resources, provide the exact URI. For templated resources, provide the URI with template parameters filled in. Returns the resource content as a string. Binary content is base64-encoded. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| bug_capture | Outline a structured bug note for VaultPilot / Obsidian. |
| learning_outline | Outline a learning note from an exploration session. |
| weekly_review | Draft a weekly review from daily note bullets. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| vault_info | Return vault root, writable folders, and Phase 5 capabilities. |
| bug-session/SKILL.md | How to run a debugging session with VaultPilot bug tools |
| bug-session/_manifest | File listing for bug-session |
| vaultpilot-capture/SKILL.md | How to capture notes into the Obsidian vault with VaultPilot |
| vaultpilot-capture/_manifest | File listing for vaultpilot-capture |
TDQS
Scored across 13 tools
The bug_* tools form a clear workflow, capture_* variants target different note types, and search_query vs search_by_tag have distinct scopes. However, search_query/search_by_tag and notes_read/read_resource have some overlapping read/search intent, and the four capture_* variants could be confused without careful reading.
Names mix conventions: bug_* uses prefix_verb, while list_resources, read_resource, search_query, and capture_* use verb_noun. notes_read and daily_append use noun_verb, and search_by_tag uses verb_by_noun, so the set is readable but not consistently patterned.
13 tools for a vault assistant covering capture, search, bug tracking, daily notes, and resource access is well-scoped. Each category earns its place, and the four capture variants are granular but not excessive.
Creation, reading, searching, and specialized bug/daily appends are covered, but generic note editing, deletion, moving, and listing vault notes are absent. Agents can work around some gaps but will hit dead ends for common note lifecycle operations.