Skip to main content
Glama
vault-kv-mcp

vault-kv-mcp

by elisjetmax

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

vault_kv_read

Read a secret (latest or a specific KV v2 version).

vault_kv_list

List keys / sub-folders under a path.

vault_kv_read_metadata

KV v2: read version history and metadata.

vault_list_kv_mounts

Discover available secret mounts and their KV versions.

vault_health

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 (default http://127.0.0.1:8200)

  • VAULT_TOKEN — required Vault token, sent as the X-Vault-Token header

  • VAULT_NAMESPACE — optional, for Vault Enterprise / HCP Vault

  • VAULT_SKIP_VERIFY — optional, set true to 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 build

Run / test with the MCP Inspector

VAULT_ADDR=http://127.0.0.1:8200 VAULT_TOKEN=hvs.xxxx npm run inspector

Use 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=s3cr3t

Then 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 tools
vault_healthVault server healthA
Read-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 keysA
Read-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 secretA
Read-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 metadataA
Read-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 mountsA
Read-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

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: health check, listing keys, reading secrets, reading metadata, and discovering mounts. No overlap or ambiguity.

    Naming Consistency4/5

    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.

    Tool Count5/5

    Five tools is well-scoped for a Vault KV server, covering essential operations without bloat or missing necessary categories.

    Completeness3/5

    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

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A 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
    • A
      license
      A
      quality
      B
      maintenance
      MCP 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.
      11
      893 npm
      2
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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