Vault MCP Server
Official HashiCorp Vault MCP server: mounts, KV secrets and PKI certificates from an agent
- 65 ★ on the repository
- Last commit
- MPL-2.0
Broad access
Why this level
- Reads and writes secrets that end up in the model context
- Can delete mounts and secrets
- Issues PKI certificates
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/vault-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Reads and writes secrets that end up in the model context
- Can delete mounts and secrets
- Issues PKI certificates
This is third-party code. Review the repository files before installing.
What it does
The server connects the agent to HashiCorp Vault. The agent creates, lists and deletes KV v1 and v2 mounts, and reads, writes and deletes secrets and individual keys. For PKI it enables the engine, creates issuers and roles and issues certificates. It runs over stdio or Streamable HTTP with CORS, rate limiting and TLS support.
Who it is for. For DevOps and security engineers who run Vault in test and local environments.
Good fit when
- You need to lay out test secrets across KV paths
- You need a certificate for an internal service in a dev environment
- You want to see which mounts and paths exist in Vault
Not a fit when
- A production Vault with real secrets
- The client or model is not fully trusted
Example request
Create a kv2 mount at dev-app and store a test database password thereMCP
- Transport
- stdio, http
- Authentication
- API key
Environment variables
VAULT_ADDR- Vault address, default http://127.0.0.1:8200
VAULT_TOKENrequired, secret- Vault token with the required policies
VAULT_NAMESPACE- Vault Enterprise namespace
MCP_ALLOWED_ORIGINS- Allowed origins for HTTP mode
Limitations
The authors intend it for local use on trusted networks. Secrets that are read end up in the model context. Requires a Vault token with suitable policies. Install by building from source with Go 1.24+ or via a Docker image. HashiCorp and Docker Hub downloads are not always reachable from Russia.
How to disable. Remove the vault-mcp-server block from the MCP config and revoke its token with vault token revoke.
FAQ
How do I pass the token in HTTP mode?
Via VAULT_ADDR, X-Vault-Token and X-Vault-Namespace headers or environment variables. Do not pass the address as a URL query parameter.
Is there a Gemini CLI extension?
Yes: gemini extensions install https://github.com/hashicorp/vault-mcp-server, with address and token in ~/.gemini/.env.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server that gives the agent vulnerability triage: NVD data, EPSS, the CISA KEV catalog, MITRE ATT&CK mapping and one-call CVE risk scoring
A bridge between an MCP client and a Kali Linux terminal so the agent can run nmap, sqlmap, hydra and other tools for authorized pentesting and CTF
Bitrix24 MCP via Keycloak and Vault
Bitrix MCP: Keycloak identity and Vault credentials
A Streamable HTTP MCP server for Bitrix24 that checks a Keycloak token on every request and keeps portal credentials in Vault, never in the model
Official Auth0 MCP server: tenant applications, Actions, logs and users via the Management API
An MCP memory server for agents plus a free gate that stops dangerous commands before they run
An offensive security MCP server: the agent runs 150+ pentest and recon tools and drives automated target assessments
README in short
The README opens with security warnings: local use only, allowed origins must be set in HTTP mode, and secrets may leak into the model. It then covers building, stdio and HTTP modes, environment variables, VS Code and Gemini CLI setup, Docker and the KV and PKI tool list. MPL 2.0 licensed.