Mcp Server Vault

io.github.AIWerkPublished by GitHub account AIWerkv0.2.1Updated Oct 24, 2026

Bitwarden/Vaultwarden for agents: list tagged items, TOTP codes, one-time Sends, save new secrets.

Overview

AI-generated overview

Lets an AI assistant read and write secrets in a Bitwarden or Vaultwarden vault, including TOTP codes and one-time Sends.

What you can do
Connects an assistant to a Bitwarden or Vaultwarden vault so it can list tagged items, retrieve stored credentials, generate TOTP codes, create one-time Sends, and save new secrets. It runs locally over stdio and authenticates with a Bitwarden personal API key plus the vault master password. No tool list is published, so the exact command set is not documented in the supplied material.
When to use it
Useful when an assistant needs to look up or store credentials during a workflow, for example retrieving an API key or password for a task, producing a TOTP code, or sharing a secret through a one-time Send link. It is aimed at users who already keep their secrets in Bitwarden or a self-hosted Vaultwarden instance.
Requirements
Runs as a local npm package (@aiwerk/mcp-server-vault) over stdio, so Node.js is required. Needs VAULT_CLIENT_ID, VAULT_CLIENT_SECRET and VAULT_MASTER_PASSWORD, plus VAULT_REGION (us, eu, or self-hosted). For self-hosted Vaultwarden, set VAULT_API_BASE to the scheme and host only; omit it for Bitwarden cloud. Network access to the vault server is required.
Before you install
The server handles live vault credentials: VAULT_CLIENT_ID, VAULT_CLIENT_SECRET and VAULT_MASTER_PASSWORD are secrets, and the master password unlocks and decrypts every item in the vault. It can save new secrets, so an assistant may write to the vault. Anything the assistant reads may be passed to the model provider, and one-time Sends create shareable links. Restrict the API key scope and review what the assistant is allowed to access.

Installation

In SourceWeft

  1. Open Mcp Server Vault in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.