Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
docker run -i --rm ghcr.io/yarrasys/kdbx:0.3.2Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
KEEPASSXC_DIR=<value> KDBX_ENV=<value> claude mcp add yarrasys-kdbx -- docker run -i --rm ghcr.io/yarrasys/kdbx:0.3.2Run in a terminal.
{ "mcpServers": { "yarrasys-kdbx": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/yarrasys/kdbx:0.3.2" ], "env": { "KEEPASSXC_DIR": "<value>", "KDBX_ENV": "<value>" } } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Jalankan di PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
BukaTools
No tool list yet. Remote servers get one after the first health check.
FAQ
Per-project secrets in local KeePassXC vaults, injected into commands without ever printing them. Agent-safe: PreToolUse guard hook + read-only MCP server. Single Go binary.
{ "mcpServers": { "yarrasys-kdbx": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/yarrasys/kdbx:0.3.2" ], "env": { "KEEPASSXC_DIR": "<value>", "KDBX_ENV": "<value>" } } }}Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: KEEPASSXC_DIR, KDBX_ENV.
Kdbx runs locally over stdio.
Last checked 2026-10-26. Per-project secrets in local KeePassXC vaults, injected into commands without ever printing them. Agent-safe: PreToolUse guard hook + read-only MCP server. Single Go binary.
From the publisher
README is not crawled yet. Open the repository
Per-project secrets in local KeePassXC vaults, injected into commands without ever printing them. Agent-safe: PreToolUse guard hook + read-only MCP server. Single Go binary.