bitwarden-agent-vault-mcp
Related Servers
Alternatives to bitwarden-agent-vault-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for secure AI agent access to Bitwarden/Vaultwarden vaults with BYOK, exposing tools to list items, reveal secrets via encrypted Sends, get TOTP codes, and save credentials.7274 npmMIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted remote MCP server that lets AI agents securely access Bitwarden vaults over HTTPS using OAuth 2.1, without exposing the master password.2Apache 2.0
- AlicenseBqualityDmaintenanceMCP server that enables AI models to securely interact with a Bitwarden password manager vault via the rbw CLI.111MIT
- AlicenseAqualityAmaintenanceMCP server for Vaultwarden/Bitwarden vault management. Enables AI agents to securely create, search, read, and update vault items via the official Bitwarden CLI, with safe-by-default redaction and support for both stdio and SSE transports.53844 npm24MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to request and retrieve credentials from a Bitwarden-compatible vault through MCP tools, with human approvals, short-lived grants, audit logging, and optional OAuth 2.1 authentication. It also supports creating secrets and injecting them into child processes without exposing them to the model.AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceSecret management MCP server for AI coding agents that prevents secrets from entering the LLM context window by returning metadata only and using side-channel injection. Integrates with Bitwarden and offers hooks for auto-capture and leak prevention.1MIT
TDQS
Scored across 7 tools
Each tool serves a distinct purpose: retrieving plaintext secrets, listing metadata, running commands with injected secrets, opening the vault, checking status, and storing secrets. No overlapping functionality.
Most tool names follow a verb_noun pattern (e.g., get_secret, list_projects). The use of 'status' (a noun) and 'run_with_secrets' (verb plus preposition) are minor deviations but still clear.
With 7 tools covering key operations (list, get, store, execute, navigate, check), the count is well-scoped for the server's purpose without superfluous tools.
Core CRUD and lifecycle operations are present, including read, create/update, and execution. Missing a dedicated delete tool, but store_secret can update, so only a minor gap.