
KeePassBox
io.github.psyb0tPublished by GitHub account psyb0tv0.1.1Updated Nov 22, 2026
Manage KeePass vaults, entries, and TOTP over MCP.
Overview
KeePassBox puts KeePass .kdbx vaults behind a local REST and MCP endpoint, letting an assistant manage vaults, entries and TOTP codes.
- What you can do
- Create, unlock and configure vaults, including cipher, KDF, Argon2 memory, iterations and compression
- Rotate a vault's master password or key file
- Create groups, search entries, move or trash them, and edit passwords, notes, tags, protected fields and small attachments
- Store a TOTP seed or URI in an entry and return the current code and expiry
- Issue bearer tokens scoped to one owner's vaults, with optional custom scope lists
- When to use it
- Useful when you want an assistant to look up or update credentials and TOTP codes in KeePass vaults you already keep, or to script vault maintenance such as password rotation and KDF tuning, without leaving the KeePass format.
- Requirements
- Runs as a local Docker container (Compose, curl and OpenSSL for the installer) on Linux, started as your regular Docker user. MCP is served over Streamable HTTP at a local port; a bearer token from the installer is required. Vaults are stored under the user's config directory by default.
Installation
In SourceWeft
- Open KeePassBox in the dashboard and add it to a workspace.
- 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
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
Quick start
Run this as your regular Docker user on Linux. You need Docker Compose, curl, and OpenSSL.
If your shell can't find the command, run ~/.local/bin/keepassbox start. Run keepassbox token to get the installer-generated bearer token. It can manage its owner's vaults, read passwords, and generate TOTP codes. 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.
- Give each bearer token access to one owner's vaults. Restrict individual tokens with a custom scope list.
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.
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
The tests run in Docker with synthetic KDBX files. The engine tests check encrypted round trips and TOTP. Integration tests call both transports.
Sponsor
License
Source: README.md at commit 59fa70d
Tools
0Version history
1- v0.1.1LatestNov 22, 2026
Score
50% 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
- License10 pts