Vault MCP 서버는 모델 Context Protocol (MCP)입니다. HashiCorp와의 통합을 제공하는 서버 구현 비밀과 산 관리를위한 볼트. 이 서버는 stdio와 StreamableHTTP를 모두 사용합니다. MCP 커뮤니케이션을 위한 수송은, 데스크탑을 위한 Claude와 호환이 되는 그리고 다른 MCP 클라이언트.

보안 참고: 이 단계에서 MCP 서버는 로컬 사용에만 사용됩니다. MCP 서버는 신뢰할 수있는 클라이언트와 신뢰할 수있는 네트워크에 배포해야합니다. StreamableHTTP 전송을 사용하는 경우, 항상 MCP_ALLOWED_ORIGINS] 환경 변수를 구성하여 신뢰할 수 있는 브라우저 기원에 대한 액세스를 제한합니다. 이것은 DNS 재결합 공격 및 기타 크로스 라이진 브라우저 공격을 방지하는 데 도움이됩니다. MCP_ALLOWED_ORIGINS는 CORS 보호 및 not 네트워크 연결 수당입니다.

보안 참고: 쿼리에 따라 MCP 서버는 Vault secrets를 포함한 특정 Vault 데이터를 MCP 클라이언트 및 LLM에 노출할 수 있습니다. MCP 클라이언트 또는 LLMs로 MCP 서버를 사용하지 마십시오.

법적 참고: 제3자 MCP Client/LLM의 사용은 MCP/LLM과 같은 MCP/LLM에 대한 사용의 측면에서 단독으로 적용되며 IBM은 그러한 제3자 도구의 성능을 담당하지 않습니다.

Vault MCP Server

The Vault MCP Server is a Model Context Protocol (MCP) server implementation that provides integration with HashiCorp Vault for managing secrets and mounts. This server uses both stdio and StreamableHTTP transports for MCP communication, making it compatible with Claude for Desktop and other MCP clients.

Security Note: At this stage, the MCP server is intended for local use only. The MCP server should only be deployed in trusted networks with trusted clients. If using the StreamableHTTP transport, always configure the MCP_ALLOWED_ORIGINS environment variable to restrict access to trusted browser origins only. This helps prevent DNS rebinding attacks and other cross-origin browser attacks. MCP_ALLOWED_ORIGINS is a CORS protection and not a network connection allowlist.

Security Note: Depending on the query, the MCP server may expose certain Vault data, including Vault secrets, to the MCP client and LLM. Do not use the MCP server with untrusted MCP clients or LLMs.

Legal Note: Your use of a third party MCP Client/LLM is subject solely to the terms of use for such MCP/LLM, and IBM is not responsible for the performance of such third party tools. IBM expressly disclaims any and all warranties and liability for third party MCP Clients/LLMs, and may not be able to provide support to resolve issues which are caused by the third party tools.

Caution: The outputs and recommendations provided by the MCP server are generated dynamically and may vary based on the query, model, and the connected MCP client. Users should thoroughly review all outputs/recommendations to ensure they align with their organization’s security best practices, cost-efficiency goals, and compliance requirements before implementation.

Features

• Create new mounts in Vault (KV v1, KV v2)
• List all available mounts
• Delete a mount
• Write secrets to KV mounts
• Read secrets from KV mounts
• List all secrets under a path
• Delete a complete secret or a key of a secret
• Comprehensive HTTP middleware stack (CORS, logging, Vault context)
• Session-based Vault client management
• Structured logging with configurable output

Prerequisites

• Go 1.24 or later (if building from source)
• Docker
• HashiCorp Vault server running locally or remotely
• A valid Vault token with appropriate permissions

Setup

1. Clone the repository:

   git clone https://github.com/hashicorp/vault-mcp-server.git
   cd vault-mcp-server
   

2. Build the binary:

   make build
   

3. Run the server:

   Stdio mode (default):

   ./vault-mcp-server
   # or explicitly
   ./vault-mcp-server stdio
   

   HTTP mode:

   ./vault-mcp-server http --transport-port 8080
   # or using make
   make run-http