keepassxc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KEEPASSXC_HOST | No | TCP host to use instead of a Unix socket, for a forwarded socket. | |
| KEEPASSXC_PORT | No | TCP port to use instead of a Unix socket, for a forwarded socket. | |
| KEEPASSXC_SOCKET | No | Unix socket path. If omitted, the socket is auto-detected. | |
| KEEPASSXC_TIMEOUT | No | Timeout in seconds. Default is 30; association waits up to 120 seconds. | 30 |
| KEEPASSXC_MCP_IDENTITY | No | Identity file path. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| associateA | Associate this MCP server with the unlocked KeePassXC database. KeePassXC shows a confirmation dialog; the user must accept it. Usually needed only once — the association is stored locally for later sessions. |
| statusA | Report whether KeePassXC is reachable and this client is associated. |
| get_loginsA | Look up saved credentials whose URL field matches. KeePassXC's browser protocol matches on URL, not title. Pass a full URL such as https://github.com or https://console.aws.amazon.com. Returns username, password, name, uuid, and TOTP when present. |
| get_totpA | Get the current TOTP code for an entry UUID (from get_logins). |
| set_loginB | Save a new login, or update an existing one when uuid is provided. KeePassXC may still prompt the user to confirm the write. Prefer generating the password with generate_password first rather than inventing one. |
| unlockA | Ask KeePassXC to open a locked database, raising its unlock prompt. The master password is typed by the user in the KeePassXC window; this server never sees it. Other tools call this automatically when they hit a locked database, unless KEEPASSXC_MCP_AUTO_UNLOCK=0. |
| generate_passwordA | Generate a password using KeePassXC's generator settings. On some KeePassXC versions this opens the generator dialog and waits for the user to accept it. |
| get_database_groupsA | List the group/folder tree of the unlocked database. |
| create_groupC | Create a group (path, e.g. 'Root/MCP' or 'Work/API keys'). |
| lock_databaseB | Lock the currently open KeePassXC database. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a distinct role: association/status, unlock/lock lifecycle, group listing/creation, credential lookup/save, TOTP retrieval, and password generation. Although associate, unlock, and status all relate to database state, their descriptions clearly separate initial setup, user-driven unlock, and reachability reporting.
Most tools follow a clear verb_noun pattern such as generate_password, get_database_groups, create_group, get_logins, get_totp, set_login, and lock_database. The bare verbs associate/unlock and the noun status are minor deviations but remain readable and unambiguous.
Ten tools is well within the expected range for a focused KeePassXC integration. Each tool covers a distinct operation in the connection, database, group, credential, and TOTP workflows without obvious redundancy.
The surface covers setup, unlock/lock, group listing/creation, credential lookup/save, TOTP, and password generation, but lacks deletion operations for logins and groups, and has no group update/rename. These are notable gaps for managing a password database, though core retrieval and creation workflows are present.