MCP Vaultwarden MCP Server

MCP pour interagir avec Vaultwarden via la CLI Bitwarden. The mcp vaultwarden mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.

What it actually does

Un serveur MCP (Model-Context-Protocol) qui expose une interface simple et robuste pour interagir avec une instance Vaultwarden auto-hébergée. Il agit comme un wrapper autour de la CLI officielle de Bitwarden (bw), permettant à des agents IA ou des scripts d'automatisation de gérer des secrets de manière programmatique.

Its toolset

Everything the assistant can do here goes through one of these:

• get_secret — The get_secret tool exposed by this server
• list_secrets — The list_secrets tool exposed by this server
• get_secret_template — The get_secret_template tool exposed by this server
• create_secret — The create_secret tool exposed by this server
• update_secret — The update_secret tool exposed by this server
• delete_secret — The delete_secret tool exposed by this server
• sync — Force la synchronisation du coffre local avec le serveur distant

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration

You will need 4 environment variables: BITWARDEN_HOST, BW_CLIENTID, BW_CLIENTSECRET, BW_MASTER_PASSWORD. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Vaultwarden's toolset — get_secret, list_secrets, get_secret_template and 4 more — is a fair guide to whether it matches your workflow. It is maintained by fkom13; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp vaultwarden mcp server does with a few real requests.