I
io.github.yarrasys/kdbx
Read-only access to secrets in a local KeePassXC vault. Runs commands with them injected.
No known CVEs
MIT license
Actively maintained
Last commit 7d ago
Works with most clients
Transport: stdio, sse
5 tools · ~186 tok
Grade A · 0.1% of 200K ctx
MCPpedia last refreshed this data
io.github.yarrasys/kdbx is an MCP server that read-only access to secrets in a local KeePassXC vault. Runs commands with them injected. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 72/100 on MCPpedia's security, maintenance and efficiency rubric.
Step 1
Install in your client
Config is the same across clients — only the file and path differ.
CD
Supported in Claude Desktopstdio, sse · Node 18+
Paste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"io-github-yarrasys-kdbx": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Embed in your READMEAbout badges →
[](https://mcppedia.org/s/io-github-yarrasys-kdbx)
Read me
What io.github.yarrasys/kdbx does
kdbx keeps a project's secrets in a per-project, per-environment KeePassXC vault (KDBX4, unlocked by a key file only — no master password) and gets them into the tools that need them **without kdbx ever printing them into a transcript, a log file, or your shell Discovery is automatic: kdbx walks up from your current directory to a committed .keepassxc.json pointer file, works out which environment is active, and takes it from there. The headline command is kdbx run -- , which resolves that
Test This Server
No automated test available for this server. Check the GitHub README for setup instructions.
Scored, not listed
Why this score
Five weighted categories — click any category to see the underlying evidence.
Score breakdown
72/100across 5 weighted dimensions
0255075100
15
12
20
15
10
−28
Security
Maintenance
Efficiency
Documentation
Compatibility
Categoriesclick a row to see evidence
Security
OSV.devNo known CVEs.
No package registry to scan.
Inventory
Tools (5)
Click any tool to inspect its schema.
~186 tokens total
Community
Reviews
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
How easy was setup?Did it work reliably?How was the documentation?
Sign in to write a review.
Frequently Asked Questions
- Is io.github.yarrasys/kdbx safe to use?
- io.github.yarrasys/kdbx has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
- How do I install io.github.yarrasys/kdbx?
- io.github.yarrasys/kdbx can be installed by cloning its GitHub repository and following the setup instructions in the README.
- What can io.github.yarrasys/kdbx do?
- io.github.yarrasys/kdbx provides 5 tools: Operations, Security, Origin, Contributing, License. See the full tools list on the server page for descriptions and parameters.
- What AI clients work with io.github.yarrasys/kdbx?
- io.github.yarrasys/kdbx is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse transport.
- Is io.github.yarrasys/kdbx actively maintained?
- io.github.yarrasys/kdbx is actively maintained — last commit was 7 days ago. It has 4 GitHub stars.
Related
Similar servers
Others in other
Headroom95Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
67.6k 3
T
Transport Stdio95Transport for TMCP using STDIO
197 14
Flare95The graph based agentic IDE
167 3
A
app.fojin/fojin-mcp94Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.
332 8
MCP Security Weekly
Get CVE alerts and security updates for io.github.yarrasys/kdbx and similar servers.
Community
Discussion
Start a conversation
Ask a question, share a tip, or report an issue.
Has anyone used this with Cursor?How do you handle auth?Any alternatives?
Sign in to join the discussion.