← Explore all mcp servers

SECRETS ADMINISTRATION / HashiCorp

Vault MCP Server

Lets a trusted MCP client operate Vault secrets and mounts using a configured Vault identity.

“Vault for managing secrets and mounts.”

01 / THE REASONING

Why this made the selection.

  • Provides an inspectable integration for a specific secrets-management workflow.
  • The README explicitly identifies secret exposure and limits intended deployments to trusted clients and networks.
  • The page names create_mount, list_mounts, and delete_mount, so the review can cite operations instead of a vendor slogan.
  • The example names VAULT_TOKEN, MCP_TLS_KEY_FILE instead of hiding where credentials come from.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md (installation, capability and permission sections)
  • go.mod
  • cmd/vault-mcp-server/main.go
  • LICENSE
  • 2026-10-14 reread of retained pinned setup/configuration evidence for the specific operational details added in this batch.
  • Documentation README.md
  • Licence file LICENSE

Our findings

  • VAULT_TOKEN is required, with VAULT_ADDR and optional namespace defining the backend.
  • The Go entrypoint supports stdio and Streamable HTTP; no read-only guarantee was established from the inspected configuration.
  • VAULT_ADDR belongs in an HTTP header, not a URL query parameter.
  • The published Docker client configuration forwards Vault credentials; it does not add a separate read-only tool mode.
  • The README names create_mount, list_mounts and delete_mount; these are mount administration operations, not merely secret retrieval. MCP_TLS_KEY_FILE configures listener TLS and is separate from VAULT_TOKEN authorization.
  • The reviewed page names 22 tools, including create_mount, list_mounts, and delete_mount. create_mount is described as Creates a new mount in Vault.
  • The configuration examples start a local process and name stdio as the transport.
  • The configuration example refers to VAULT_TOKEN, MCP_TLS_KEY_FILE for credentials or account selection.
  • The page documents both Streamable HTTP and a local stdio launch.

Not established by this review

  • Server startup, authentication and tool execution were not tested.
  • No authenticated session, installation, permission bypass or package-to-source parity test was performed.
  • The server was not installed or initialised.
  • No tools/list or tool call was made.
  • A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. The README gives no one-line install command: clone the repository and run make build, or use the hashicorp/vault-mcp-server container image named in its VS Code block, then configure Vault address, namespace and a limited token.
  2. Use the documented stdio mode with a trusted client, or follow the network/TLS guidance for a controlled HTTP deployment.

Before you start

  • A Vault deployment and a Vault token limited to the required paths.
  • Docker, or Go 1.24 or later to build from source, per the README.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "vault_token",
      "description": "Vault Token",
      "password": true
    },
    {
      "type": "promptString",
      "id": "vault_namespace",
      "description": "Vault Namespace (optional)",
      "password": false
    },
    {
      "type": "promptString",
      "id": "vault_addr",
      "description": "Vault Address (optional)",
      "password": false
    }
  ],
  "servers": {
    "vault-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VAULT_ADDR=${input:vault_addr}",
        "-e",
        "VAULT_TOKEN=${input:vault_token}",
        "-e",
        "VAULT_NAMESPACE=${input:vault_namespace}",
        "hashicorp/vault-mcp-server"
      ]
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Official documentation ↗Checked

    https://github.com/hashicorp/vault-mcp-server/blob/59f51173a0ed60bb2268b97d1a0c0bea9ebde120/README.md

    Supports: summary, whySelected, bestFor, limitations, install, access, compatibility, transports, configExample, review

  2. https://github.com/hashicorp/vault-mcp-server/blob/59f51173a0ed60bb2268b97d1a0c0bea9ebde120/LICENSE

    Supports: license

  3. Implementation: go.mod ↗Checked

    https://github.com/hashicorp/vault-mcp-server/blob/59f51173a0ed60bb2268b97d1a0c0bea9ebde120/go.mod

    Supports: language, review

  4. https://github.com/hashicorp/vault-mcp-server/blob/59f51173a0ed60bb2268b97d1a0c0bea9ebde120/cmd/vault-mcp-server/main.go

    Supports: language, review

Evidence & Ask