There is now an official Vault MCP Server from Hashicorp. Therefore, the alternative third-party Vault MCP Server will continue to exist and be
Connect Vault to Claude, Cursor or any other MCP client and it stops being a tab you switch to. There is now an official Vault MCP Server from Hashicorp. Therefore, the alternative third-party Vault MCP Server will continue to exist and be updated with features and fixes, but no attempt will be made to compete with the official. The vault mcp server is what makes that connection.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
PKI — TransitClaude — The Claude tool exposed by this serverVSCode — The MCP: Add Server --> Docker Image command can also streamline this configuration. The values below can be entered into the input prompts, and thenConfiguration is passed through the environment: ENV_VAR, ENV_VAR_TWO, VAULT_AUTH_PATH, VAULT_ROLE_ID, VAULT_SECRET_ID, VAULT_TOKEN, VAULT_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Vault's toolset — PKI, Claude, VSCode — is a fair guide to whether it matches your workflow. It is maintained by mschuchard; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| PKI | Transit |
| Claude | The Claude tool exposed by this server. |
| VSCode | The MCP: Add Server --> Docker Image command can also streamline this configuration. The values below can be entered into the input prompts, and then the mcp.json file is automically opened within a pane afterward for fu |
{
"mcpServers": {
"vault": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ENV_VAR",
"-e",
"ENV_VAR_TWO",
"matthewschuchard/vault-mcp-server"
],
"env": {
"ENV_VAR": "<ENV VAR VALUE>",
"ENV_VAR_TWO": "<ENV VAR TWO VALUE>",
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ENV_VAR | Configuration value read at startup. | Optional |
| ENV_VAR_TWO | Configuration value read at startup. | Optional |
| VAULT_AUTH_PATH | Filesystem location the server is allowed to use. | Optional |
| VAULT_ROLE_ID | Configuration value read at startup. | Optional |
| VAULT_SECRET_ID | Credential the server authenticates with. | Yes |
| VAULT_TOKEN | Credential the server authenticates with. | Yes |
| VAULT_URL | Endpoint or connection string the server talks to. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.