vaultwarden-mcp
Related Servers
Alternatives to vaultwarden-mcp
No user-submitted related servers found.
Related Servers
AlicenseBqualityBmaintenanceEnables AI assistants to securely manage Bitwarden vault items, folders, attachments, and organization administration through the Model Context Protocol.59344 npm298GPL 3.0- AlicenseNot gradedqualityDmaintenanceEnables AI agents and automation scripts to securely interact with self-hosted Vaultwarden instances through the Bitwarden CLI, automatically managing vault sessions and providing tools to read, create, update, and delete secrets programmatically.6 npm2MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Bitwarden/Vaultwarden for password and secure note management, including creation, updating, deletion, and search of items and folders.1-
- 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.531,947 npm26MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to securely retrieve passwords, API keys, and other items from a Vaultwarden/Bitwarden vault using MCP tools with fuzzy search and caching.1MIT
- 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
TDQS
Scored across 298 tools
The set is riddled with functionally identical tools: vaultwarden_post_cipher / vaultwarden_put_cipher / vaultwarden_post_cipher_admin all update a cipher, and delete_cipher / delete_cipher_post / delete_cipher_put / delete_cipher_admin all delete one. Dozens of PUT/POST alias pairs (activate_authenticator vs activate_authenticator_put, disable_twofactor vs disable_twofactor_put) and v1/v2/legacy variants give an agent no reliable basis for selection.
Most names are snake_case with a vaultwarden_ prefix, but the ordering convention is mixed: HTTP-verb-first (vaultwarden_post_cipher), resource-first (vaultwarden_ciphers_create_item, vaultwarden_maintenance_rotate_password), and route-path-style (vaultwarden_organizations_rotate_api_key). Generic dispatcher tools (vaultwarden_accounts, vaultwarden_admin, vaultwarden_organizations, vaultwarden_sends) break the pattern entirely by overlapping with the specific tools.
298 tools for one server is an extreme mismatch — roughly a 1:1 mirror of every Vaultwarden HTTP route including aliases, legacy paths, and admin duplicates. This far exceeds any reasonable agent-facing surface and guarantees tool-selection overload.
Coverage of the Vaultwarden domain is essentially exhaustive: ciphers, folders, collections, orgs, members, groups, policies, Sends, attachments, 2FA, emergency access, admin, and diagnostics are all present. The only real gap is that the redundant aliases make it hard to find the canonical operation, not that operations are missing.