Skip to main content
Glama
KeePassBox

KeePassBox

by psyb0t

KeePassBox

CI version license Docker Pulls

Put KeePass behind REST and MCP. Create a vault, rotate its master password, turn Argon2 up to 512 MiB, or grab a TOTP code from the terminal. You can open the same .kdbx in KeePassXC.

Contents

Related MCP server: Warden MCP Server

Quick start

Run this as your regular Docker user on Linux. You need Docker Compose, curl, and OpenSSL.

curl -fsSL https://raw.githubusercontent.com/psyb0t/docker-keepassbox/main/install.sh | bash
keepassbox start

If your shell can't find the command, run ~/.local/bin/keepassbox start. The installer generates your bearer token. Run keepassbox token to read it. REST is at http://localhost:8000/v1, and MCP is at http://localhost:8000/mcp.

The installer puts the Compose files and vaults in ~/.config/keepassbox/ by default and uses the published psyb0t/keepassbox:latest image. See the install guide to pin a version, change the port, or upgrade.

What it does

  • Create and unlock multiple vaults with a master password, a configured key file, or both.

  • Change the KDBX 4 cipher, KDF, Argon2 memory, iterations, parallelism, and compression. Rotate the password or key file separately.

  • Create groups, search entries, move or trash them, and edit passwords, notes, tags, protected fields, and small attachments.

  • Save a TOTP seed or URI inside an entry and return the current code and expiry.

  • Scope each bearer token to one owner and a set of permissions. REST and MCP use the same checks.

Ordinary edits preserve entry history. The API reference lists the supported operations and file formats.

Agent integrations

Connect a Streamable HTTP MCP client to http://localhost:8000/mcp and configure its bearer token. See MCP configuration.

openclaw skills install @psyb0t/docker-keepassbox
openclaw plugins install clawhub:@psyb0t/keepassbox

Configure KEEPASSBOX_URL and KEEPASSBOX_TOKEN for the OpenClaw bridge.

Documentation

Read the KeePassBox docs for install options, vault security settings, and the REST and MCP commands.

Development

make lint
make test
make sec
make build

The tests run in Docker with synthetic KDBX files. The engine tests check encrypted round trips and TOTP. Integration tests call both transports.

Sponsor

Sponsor on GitHub

License

GPL-3.0. The vault engine uses PyKeePass.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables secure management of agent-scoped secrets in HashiCorp Vault through MCP protocol. Provides per-agent namespacing, multiple authentication methods (API key, JWT, mTLS), and optional encryption/decryption capabilities with built-in rate limiting.
      3
      -
    • A
      license
      A
      quality
      B
      maintenance
      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
      30
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible AI assistants and clients to generate, store, search, fill, and reveal website credentials through scoped per-client access, while keeping secrets encrypted at rest and out of logs.
      MIT