HashiCorp Vault MCP Server
by rccyx
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAULT_ADDR | Yes | URL of the Vault cluster, for example https://vault.internal:8200 or http://127.0.0.1:8200. | |
| VAULT_TOKEN | Yes | Short-lived or renewable Vault token starting with hvs.. Scope it tightly using Vault policies. | |
| VAULT_CACERT | No | Path to a CA bundle used for verifying self-signed certificates. | |
| VAULT_NAMESPACE | No | Optional Vault namespace if your deployment requires it; the server forwards the process environment to the Vault client library. | |
| NODE_TLS_REJECT_UNAUTHORIZED | No | Set to 0 only for testing with self-signed certificates. Prefer adding proper CA bundles instead. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityInactive
ResponsivenessSyncing