vault-health-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAULT_HEALTH_LICENSE | No | License key for Pro tier. Also configurable via --license-key CLI flag or config file. |
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 |
|---|---|
| configure_vaultA | Configure the vault path for this server. Call this first if the server started without a --vault argument. |
| check_vault_healthA | Scan the vault for structural issues: broken wikilinks, orphaned notes, missing frontmatter. Returns a categorized list of all issues found. |
| repair_vaultA | [Pro] Auto-repair safe structural issues. Only adds content (frontmatter, plain text replacements for broken links). Never deletes files or content. Requires Pro license. |
| vault_statisticsA | Vault-level analytics: file count, link count, orphans, broken links, frontmatter coverage percentage. |
| find_orphansA | Find all orphaned leaf notes — notes typed as 'leaf' in frontmatter that are not linked from any hub or branch file. |
| find_broken_linksA | Find all broken wikilinks — [[targets]] that don't resolve to any file in the vault. Excludes wikilinks inside code spans. |
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
Tools are mostly distinct, but find_orphans and find_broken_links overlap with check_vault_health which also finds these issues. This could cause confusion about which tool to use.
All tools use snake_case with verb_noun pattern except vault_statistics (noun_noun). Consistent style, but one minor deviation.
6 tools is well-scoped for a vault health MCP: configuration, comprehensive check, repair, statistics, and specific queries. No excess or deficiency.
Core operations (configure, check, repair, statistics) are covered. Minor gap: no tool to individually fix a specific broken link without Pro license, but repair_vault handles auto-fix.