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) |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/elisjetmax/mcp-vault-hashicorp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server