KeePassXC Integration

Manage Cursor secrets via KeePassXC and keepassxc-cli across Windows and WSL.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/janjaszczak/cursor --skill keepassxc-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: KeePassXC Integration
Source: https://github.com/janjaszczak/cursor/tree/main/skills/keepass-integration
Command: npx skills add https://github.com/janjaszczak/cursor --skill keepassxc-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

KeePassXC Integration enables secure management of secrets by using KeePassXC as the storage backend for Cursor configurations and runtime secrets, avoiding insecure storage in environment variables or files.

Core Features & Use Cases

  • Securely store passwords, API tokens, and SSH keys in a KeePassXC database.
  • Retrieve secrets at runtime using keepassxc-cli or helper scripts, with a check-before-add workflow for entries.
  • Manage secrets across Windows and WSL with a centralized database and GUI integration.

Quick Start

Configure KeePassXC with the cursor.kdbx database and enable SecretManagement integration to begin securely storing and retrieving secrets.

Frequently Asked Questions about KeePassXC Integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I securely manage API keys and SSH keys in WSL using KeePassXC?

You can securely manage API keys and SSH keys in WSL by using KeePassXC as the storage backend. The integration retrieves secrets via keepassxc-cli, requiring an open KeePassXC database to access SSH keys across projects.

What is the best way to avoid storing secrets in environment variables for Windows workflows?

Using a KeePassXC database is the best way to avoid insecure environment variable storage. This approach enforces an architecture where the database holds all secrets, managed via keepassxc-cli for Windows and WSL workflows.

Do I need keepassxc-cli to retrieve passwords for local development configurations?

Yes, keepassxc-cli is required to retrieve passwords and API tokens for local development. The integration relies on it to interact with the KeePassXC database and execute a check-before-add workflow for secret entries.

Can I use Windows SecretManagement integration to unlock the KeePassXC database?

SecretManagement integration provides the database password to unlock KeePassXC. The architecture relies on SecretManagement for unlocking, while keepassxc-cli handles the actual retrieval of secrets at runtime.

Does retrieving SSH keys from KeePassXC require the database to be open?

Yes, accessing SSH keys requires an open KeePassXC database. The integration architecture mandates that the database remains open to allow keepassxc-cli to securely retrieve SSH keys for your environments.