vault-kv-mcp
Provides tools for reading secrets and metadata from HashiCorp Vault KV secrets engine, including listing paths, reading secret versions, and checking server health.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@vault-kv-mcp read the secret at path secret/demo"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
vault-kv-mcp
A read-only MCP (Model Context Protocol) server that exposes the HashiCorp Vault KV secrets engine (versions 1 and 2) as tools. Every tool performs only non-destructive reads — there are no write, delete, or destroy operations. It authenticates with a Vault token and speaks MCP over stdio, so it works with local MCP clients such as Claude Desktop.
Tools (all read-only)
Tool | Description |
| Read a secret (latest or a specific KV v2 version). |
| List keys / sub-folders under a path. |
| KV v2: read version history and metadata. |
| Discover available secret mounts and their KV versions. |
| Check Vault server health / connectivity. |
KV v1 vs v2 is auto-detected per mount when kv_version is not supplied (falling back to v2).
For defense in depth, pair this with a Vault token whose policies grant only read/list capabilities on the relevant paths.
Related MCP server: Vault MCP Server (mschuchard)
Configuration
Set these environment variables (see .env.example):
VAULT_ADDR— Vault base URL (defaulthttp://127.0.0.1:8200)VAULT_TOKEN— required Vault token, sent as theX-Vault-TokenheaderVAULT_NAMESPACE— optional, for Vault Enterprise / HCP VaultVAULT_SKIP_VERIFY— optional, settrueto skip TLS verification (dev only)
The token only needs policies granting access to the KV paths you intend to use.
Build
npm install
npm run buildRun / test with the MCP Inspector
VAULT_ADDR=http://127.0.0.1:8200 VAULT_TOKEN=hvs.xxxx npm run inspectorUse with Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"vault-kv": {
"command": "node",
"args": ["/absolute/path/to/vault-mcp/dist/index.js"],
"env": {
"VAULT_ADDR": "http://127.0.0.1:8200",
"VAULT_TOKEN": "hvs.your-token-here"
}
}
}
}Quick local Vault for testing
vault server -dev # prints a Root Token and unseal info
export VAULT_ADDR=http://127.0.0.1:8200
export VAULT_TOKEN=<root-token-from-output>
vault kv put secret/demo username=app password=s3cr3tThen ask your MCP client to read secret/demo.
Security notes
The server only ever reads from Vault; it never writes, deletes, or destroys secrets.
The token is read only from the environment and never logged.
Prefer a short-lived, least-privilege token (read/list only) over a root token.
Available Tools
5 toolsvault_healthVault server healthARead-onlyIdempotent
Check the Vault server's health: whether it is initialized, sealed, and in standby. Good for verifying connectivity and configuration.
Inputs: no named parameters. Returns: initialized, sealed, standby, version
vault_kv_listList KV keysARead-onlyIdempotent
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.
Inputs: mount (required), path, kv_version. Returns: keys, kv_version
vault_kv_readRead a KV secretARead-onlyIdempotent
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.
Inputs: mount (required), path (required), kv_version, version. Returns: data, metadata, kv_version
vault_kv_read_metadataRead KV v2 secret metadataARead-onlyIdempotent
KV v2 only: read metadata for a secret, including the full version history, current version, created/updated times, and custom_metadata.
Inputs: mount (required), path (required). Returns: metadata
vault_list_kv_mountsList KV secret mountsARead-onlyIdempotent
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.
Inputs: no named parameters. Returns: mounts
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
Read-only MCP server for The Quiet Protocol's engines, benchmarks, proof, and business data.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Public read-only MCP server for Genvernium product and developer resources.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables interaction with HashiCorp Vault to read, write, list, and delete secrets through a containerized MCP server with secure token-based authentication.4MIT
- AlicenseNot gradedqualityBmaintenanceA third-party MCP server for interacting with HashiCorp Vault to manage ACL policies, audit devices, and secret engines like KV v2, PKI, and Transit. It provides tools for system backend administration and includes prompts for generating security policy configurations.MIT

wundervaultofficial
AlicenseAqualityBmaintenanceMCP server for Wundervault zero-knowledge secret management. Lets AI Agents use secrets via the Model Context Protocol — secrets are decrypted using a broker that runs on your local computer on a protected account that your agent cannot access the plaintext.11893 npm2AGPL 3.0- AlicenseNot gradedqualityDmaintenanceA read-only MCP server for inspecting and diagnosing HCP Terraform workspaces, runs, and plan summaries from ChatGPT and other MCP clients. It provides tools to list workspaces, inspect runs, and summarize plans without exposing sensitive data.MIT