Skip to content

Commit 4c8f8c6

Browse files
authored
Add Vault MCP server (#201)
Claude-Session: https://claude.ai/code/session_01S58U7phvDgphx6ZTXuWMJQ Signed-off-by: Mohammod Al Amin Ashik <maa.ashik00@gmail.com>
1 parent e55f034 commit 4c8f8c6

1 file changed

Lines changed: 91 additions & 0 deletions

File tree

servers/com.vault-mcp-docker.json

Lines changed: 91 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,91 @@
1+
{
2+
"$schema": "../schemas/server-definition.schema.json",
3+
"id": "com.vault-mcp-docker",
4+
"name": "Vault (Docker)",
5+
"alias": "vault",
6+
"description": "Connect to HashiCorp Vault via Docker to manage secrets and secrets engines. Read, write, list, and delete key-value secrets, create and manage mounts, and handle PKI certificates (issuers, roles, certificate issuance) in an isolated container.",
7+
"logo": "https://avatars.githubusercontent.com/u/761456?v=4",
8+
"schema_version": "2.1",
9+
"categories": [
10+
"security"
11+
],
12+
"tags": [
13+
"vault",
14+
"hashicorp",
15+
"secrets",
16+
"secrets-management",
17+
"pki",
18+
"key-value",
19+
"security",
20+
"docker"
21+
],
22+
"transport": {
23+
"type": "stdio",
24+
"command": "docker",
25+
"args": [
26+
"run",
27+
"-i",
28+
"--rm",
29+
"-e",
30+
"VAULT_ADDR",
31+
"-e",
32+
"VAULT_TOKEN",
33+
"hashicorp/vault-mcp-server:latest"
34+
],
35+
"env": {
36+
"VAULT_ADDR": "${input:VAULT_ADDR}",
37+
"VAULT_TOKEN": "${input:VAULT_TOKEN}"
38+
},
39+
"metadata": {
40+
"inputs": [
41+
{
42+
"id": "VAULT_ADDR",
43+
"label": "Vault Address",
44+
"description": "Base URL of your HashiCorp Vault server. Use host.docker.internal instead of localhost to reach a Vault instance running on the host machine (e.g., https://host.docker.internal:8200).",
45+
"type": "url",
46+
"required": true,
47+
"secret": false,
48+
"placeholder": "https://vault.example.com:8200"
49+
},
50+
{
51+
"id": "VAULT_TOKEN",
52+
"label": "Vault Token",
53+
"description": "Vault authentication token used to access secrets and secrets engines. The token's policies determine which paths and operations are permitted.",
54+
"type": "text",
55+
"required": true,
56+
"secret": true,
57+
"placeholder": "hvs.****************************",
58+
"obtain": {
59+
"url": "https://developer.hashicorp.com/vault/docs/commands/token/create",
60+
"instructions": "1. Authenticate to your Vault server (e.g., vault login)\n2. Create a token scoped to the policies you need: vault token create -policy=<policy>\n3. Copy the token value from the output (token field)",
61+
"button_label": "Create Token"
62+
}
63+
}
64+
]
65+
}
66+
},
67+
"auth": {
68+
"type": "api_key",
69+
"instructions": "Provide a Vault token (VAULT_TOKEN) with policies granting access to the paths you want to manage. Create one with `vault token create`."
70+
},
71+
"contributor": {
72+
"name": "HashiCorp",
73+
"github": "hashicorp",
74+
"url": "https://www.vaultproject.io"
75+
},
76+
"links": {
77+
"repository": "https://github.com/hashicorp/vault-mcp-server",
78+
"homepage": "https://www.vaultproject.io",
79+
"documentation": "https://github.com/hashicorp/vault-mcp-server#readme"
80+
},
81+
"platforms": [
82+
"all"
83+
],
84+
"capabilities": {
85+
"tools": true,
86+
"resources": false,
87+
"prompts": false,
88+
"read_only_mode": false
89+
},
90+
"changelog_url": "https://github.com/hashicorp/vault-mcp-server/releases"
91+
}

0 commit comments

Comments
 (0)