mcpdirectory.dev
9,129 servers · updated 23 Sept

Vault MCP server

community Active last commit 44 d
{
  "mcpServers": {
    "aiwerk-vault": {
      "command": "npx",
      "args": [
        "-y",
        "@aiwerk/mcp-server-vault@latest"
      ],
      "env": {
        "VAULT_CLIENT_ID": "<vault_client_id>",
        "VAULT_CLIENT_SECRET": "<vault_client_secret>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @aiwerk/mcp-server-vaultversion 0.2.1

What it does

This MCP server connects AI agents to Bitwarden or Vaultwarden vaults, exposing tools to list items, retrieve TOTP codes, generate one-time encrypted secret links (Sends), and save new credentials. It is for developers who want agents to access and manage secrets from a self-hosted or Bitwarden vault without exposing plaintext values.

  • Retrieve API keys and passwords from your vault for use in agent workflows without passing secrets in plaintext.
  • Generate time-limited, one-time encrypted URLs (Bitwarden Sends) to deliver secrets to agents or end users.
  • Save agent-generated credentials (passwords, API keys) back into a dedicated vault collection for future retrieval.

Tools this server exposes

ToolDoes
list_vault_itemsList items from the exposed and agent-created collections, returning metadata only without secret values.
get_vault_metadataRetrieve full metadata for a named vault item including username, URIs, and custom fields, but not passwords or secrets.
reveal_secret_via_sendCreate a Bitwarden Send—an E2E-encrypted one-time URL—to deliver a secret with configurable TTL and maximum views.
get_totp_codeRetrieve the current TOTP code for a login item, including remaining seconds in the current period.
save_generated_secretSave an agent-generated secret as a secure note into the agent-created collection (create-only, no overwrite).
save_login_itemSave sign-in credentials (username, password, optional URL, optional TOTP seed) into the agent-created collection as a login item (create-only).
health_checkCheck server connectivity, authentication status, API version, collection visibility, item counts, and latency.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.