Vaultwarden is an unofficial Bitwarden server implementation written in Rust, formerly known as bitwarden_rs. It provides a lightweight alternative to the official Bitwarden server with compatible API for Bitwarden clients.
Enables programmatic management of Vaultwarden vaults, allowing agents to create, search, read, update, and move vault items, manage attachments, and handle organization or collection operations.
MCP 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.
53
1,478 npm
26
MIT
Why this server?
Allows the agent to fill usernames, passwords, and authenticator codes from the owner's Vaultwarden vault into web page fields, without exposing the secret values to the agent.
Let AI agents act for a person on websites, with the person's approval on their phone. The agent's browser runs in a sandboxed vault it cannot read into; when a site asks for a password, CAPTCHA or 2FA, the owner takes over from their phone.
13
6
MIT
Why this server?
Provides tools for interacting with a Vaultwarden vault, including listing items, retrieving metadata, revealing secrets via Bitwarden Sends, getting TOTP codes, and saving generated secrets or login items.
MCP 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.
7
274 npm
MIT
Why this server?
Provides a standardized interface to a Vaultwarden (Bitwarden-compatible) server, enabling management of accounts, ciphers, folders, organizations, sends, two-factor, emergency access, events, and admin operations, plus decrypted vault access, deduplication, and password rotation.
Enables AI agents to interact with and manage a Vaultwarden/Bitwarden-compatible server via the Model Context Protocol, covering account, cipher, folder, organization, send, admin, and vault maintenance operations.
298
MIT
Why this server?
Integrates with Vaultwarden as a live secret provider, enabling search and metadata access to accessible vault entries, secret creation and updates, folder management, field-level secret reveal, and migration of built-in secrets without exposing values to the agent.
Enables AI assistants to deploy and manage apps on blitz.cloud, including databases, environment variables, DNS records, and logs.
MIT
Why this server?
Provides tools for managing secrets in a self-hosted Vaultwarden instance, including retrieving, creating, updating, and deleting secrets (logins, notes, cards, identities), with automatic session management and vault synchronization.
Enables 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 npm
2
MIT
Why this server?
Provides the same vault integration for self-hosted Vaultwarden instances, enabling remote MCP access to search, reveal, generate, and manage vault items over HTTPS with OAuth authorization.
A self-hosted remote MCP server that lets AI agents securely access Bitwarden vaults over HTTPS using OAuth 2.1, without exposing the master password.
175 npm
3
Apache 2.0
Why this server?
Integrates with Vaultwarden (alongside OS keychain and SecretFabric) as an encrypted secret store for mail account credentials, keeping credentials out of the model, chat, logs, and normal application storage.
Enables AI agents to run real email operations across multiple IMAP/SMTP and provider OAuth accounts — syncing, searching, reading, drafting, attaching, and sending mail — while requiring explicit human approval for sending, deleting, or forwarding and recording an inspectable audit trail.
