vault-kv-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAULT_ADDR | No | Vault base URL | http://127.0.0.1:8200 |
| VAULT_TOKEN | Yes | Vault token, sent as the X-Vault-Token header | |
| VAULT_NAMESPACE | No | Optional Vault namespace for Vault Enterprise / HCP Vault | |
| VAULT_SKIP_VERIFY | No | Set to 'true' to skip TLS verification (dev only) |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vault_kv_readA | Read the key/value data stored at a secret path in a Vault KV engine. For KV v2 you may request a specific historical version; omit it to get the latest. |
| vault_kv_listA | List the secret keys/sub-folders under a path. Keys ending in '/' are sub-folders. Use path '' or '/' to list the root of the mount. |
| vault_kv_read_metadataA | KV v2 only: read metadata for a secret, including the full version history, current version, created/updated times, and custom_metadata. |
| vault_list_kv_mountsA | Discover the secret engine mounts available to the current token, including each KV mount's version. Useful to learn which 'mount' values to pass to the other tools. |
| vault_healthA | Check the Vault server's health: whether it is initialized, sealed, and in standby. Good for verifying connectivity and configuration. |
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 5 tools
Each tool has a clearly distinct purpose: health check, listing keys, reading secrets, reading metadata, and discovering mounts. No overlap or ambiguity.
All tools follow the vault_ prefix and verb_noun pattern, but there is slight inconsistency in ordering (e.g., vault_kv_list vs vault_list_kv_mounts). Overall still predictable.
Five tools is well-scoped for a Vault KV server, covering essential operations without bloat or missing necessary categories.
Missing write/update and delete operations for secrets, which are typical in KV management. The tools are read-heavy, leaving notable gaps for lifecycle management.