Bitwarden/Vaultwarden for agents: list tagged items, TOTP codes, one-time Sends, save new secrets.
Bitwarden / Vaultwarden MCP server — BYOK vault access for AI agents.
Exposes 6 tools over stdio. Secret values are never sent in plaintext through list_vault_items or get_vault_metadata — secrets are delivered only through Bitwarden Sends (E2E-encrypted one-time URLs).
npx -y @aiwerk/mcp-server-vault
| Variable | Required | Default | Description |
|---|---|---|---|
VAULT_API_BASE | ✅ | — | Base URL of your Bitwarden/Vaultwarden instance (no trailing slash), e.g. https://pass.aiwerk.ch |
VAULT_CLIENT_ID | ✅ | — | Personal API key client_id (e.g. user.abc-def-1234) |
VAULT_CLIENT_SECRET | ✅ | — | Personal API key client_secret |
VAULT_MASTER_PASSWORD | ✅ | — | Vault master password (used for E2E decryption key derivation) |
VAULT_EXPOSED_COLLECTION | — | mcp-exposed | Name of the collection visible to agents |
VAULT_AGENT_CREATED_COLLECTION | — | mcp-agent-created | Name of the collection for agent-created secrets |
VAULT_API_TIMEOUT_MS | — | 15000 | HTTP timeout in milliseconds |
DRY_RUN | — | 0 | Set 1 to log write operations without executing them |
READ_ONLY | — | 0 | Set 1 to block all write operations (Send creation and save) |
client_id and client_secretBefore using this server, create two collections in your Vaultwarden organization:
mcp-exposed — items you want to expose to agents (your existing secrets: API keys, passwords, etc.)mcp-agent-created — items written by agents via save_generated_secretAdd items to mcp-exposed via the Vaultwarden web UI.
Optionally add these custom fields to items in mcp-exposed for fine-grained control:
| Field | Type | Purpose |
|---|---|---|
mcp-scope | text | Comma-separated glob list of tool/server names allowed to use this item (e.g. stripe.*,openai) |
mcp-chat-reveal-allowed | text | "true" to allow chat delivery of the Send URL |
mcp-delivery-channel | text | "chat" (default), "telegram", or "email" |
| Tool | Description |
|---|---|
list_vault_items | List items from mcp-exposed and mcp-agent-created. Returns metadata only — no secret values. |
get_vault_metadata | Get full metadata for a named item (name, type, username, URIs, custom fields, expiry). No password/secret. |
reveal_secret_via_send | Reveal a secret via a Bitwarden Send (E2E-encrypted one-time URL with configurable TTL and max-views). |
get_totp_code | Get the current TOTP code for a login item, including remaining seconds in the period. |
save_generated_secret | Save an agent-generated secret (password / api-key) into mcp-agent-created as a secure note. CREATE-only — no overwrite. |
save_login_item | Save sign-in credentials (username + password + optional URL + TOTP seed) into mcp-agent-created as a real login item. CREATE-only — no overwrite. |
health_check | Check connectivity: auth status, API version, collection visibility, item counts, latency. |
mcp-exposed or mcp-agent-created are accessible; all other items return item_not_visibleupdate_*, delete_*, or change_* tools existlist_vault_items and get_vault_metadata never return passwords, TOTP seeds, or api-key valuessave_generated_secret and save_login_item are CREATE-only into the dedicated mcp-agent-created collectionNote: Actual
{{vault:NAME}}placeholder resolution in tool call arguments happens in the AIWerk hosted bridge, not in this server. The bridge's resolution uses the same BYOC credentials. See the bridge-patch companion document for details.
MIT — AIWerk kontakt@aiwerk.ch
Homepage: https://aiwerkmcp.com
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @aiwerk/mcp-server-vaultMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-aiwerk-mcp-server-vault": {
"command": "npx",
"args": [
"-y",
"@aiwerk/mcp-server-vault"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceio.github.AIWerk/mcp-server-vault works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.