io.github.AIWerk/mcp-server-vault vs kdbx
io.github.AIWerk/mcp-server-vault is an MCP server published by AIWerk. Marketplaces we read that list it: 1 (Official MCP Registry). kdbx is an MCP server published by yarrasys. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  kdbx | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.1 No figure published Not marked · First seen |
Listed Version: 0.3.2 Forks (GitHub): 0 Stars (GitHub): 5 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.AIWerk/mcp-server-vault | kdbx |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 5 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (@aiwerk/mcp-server-vault) | On your machine (ghcr.io/yarrasys/kdbx:0.3.2) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 3 | 2, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/aiwerk/mcp-server-vault | github.com/yarrasys/kdbx |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.AIWerk/mcp-server-vault
Bitwarden/Vaultwarden for agents: list tagged items, TOTP codes, one-time Sends, save new secrets.
kdbx
Read-only access to secrets in a local KeePassXC vault. Runs commands with them injected.
How to run each
io.github.AIWerk/mcp-server-vault As a local MCP server: npm package
claude mcp add --env "VAULT_CLIENT_ID=<YOUR_VAULT_CLIENT_ID>" --env "VAULT_CLIENT_SECRET=<YOUR_VAULT_CLIENT_SECRET>" --env "VAULT_MASTER_PASSWORD=<YOUR_VAULT_MASTER_PASSWORD>" --env "VAULT_REGION=<YOUR_VAULT_REGION>" --transport stdio mcp-server-vault -- npx -y @aiwerk/mcp-server-vaultRequires: VAULT_CLIENT_ID (secret), VAULT_CLIENT_SECRET (secret), VAULT_MASTER_PASSWORD (secret), VAULT_REGION
kdbx As a local MCP server: Docker image
claude mcp add --transport stdio kdbx -- docker run -i --rm -v "<YOUR_PROJECT_DIR>:/work" -v "<YOUR_KEEPASSXC_DIR>:/kpx:ro" -w /work ghcr.io/yarrasys/kdbx:0.3.2 mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.AIWerk/mcp-server-vault asks for
VAULT_API_BASEVAULT_CLIENT_ID (secret)VAULT_CLIENT_SECRET (secret)VAULT_MASTER_PASSWORD (secret)VAULT_REGION
Only kdbx asks for
KDBX_ENVKEEPASSXC_DIR
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.AIWerk/mcp-server-vault · What it can do: kdbx · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.