MCP Server Vault

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-server-vault -- npx -y @aiwerk/mcp-server-vault

{
  "mcpServers": {
    "mcp-server-vault": {
      "args": [
        "-y",
        "@aiwerk/mcp-server-vault"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.mcp-server-vault]
command = "npx"
args = ["-y", "@aiwerk/mcp-server-vault"]

{
  "mcpServers": {
    "mcp-server-vault": {
      "args": [
        "-y",
        "@aiwerk/mcp-server-vault"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "mcp-server-vault": {
      "args": [
        "-y",
        "@aiwerk/mcp-server-vault"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: VAULT_REGION (Bitwarden region or self-hosted mode (e.g. us, eu, or self-hosted).), VAULT_API_BASE (Base URL for self-hosted Vaultwarden, scheme+host only (e.g. https://pass.example.com). Omit for Bitwarden cloud.), VAULT_CLIENT_ID (Bitwarden API client_id (personal API key).), VAULT_CLIENT_SECRET (Bitwarden API client_secret (personal API key).), VAULT_MASTER_PASSWORD (Vault master password, used to unlock and decrypt items.). The author declared them in the registry entry; get the values from the project itself.