notinferred/keypaste

What it solves

Teams and developers need to keep passwords and project secrets in one place, and when they use AI coding agents, they need to give those agents access to credentials without handing over the whole vault. keypaste solves this by storing logins and environment variables in a local, open KDBX file and adding an approval step so an agent can only receive a secret if you explicitly allow it.

How it works

keypaste stores everything in a KeePass-compatible KDBX 4 file on your disk, with no account and no network. You can add logins, generate strong passwords or passphrases, and import or edit the same file with KeePassXC. For developers, it defines projects with per-environment values (dev, staging, prod) and can inject those values into a command's environment without writing them to disk. An MCP bridge connects to AI clients like Claude: when the agent requests a specific secret, you get a prompt with the agent's reason and choices to deny, allow once, allow for an hour, or always allow. Every request is stored in a hash-chained audit log.

Who it’s for

Developers who use AI coding assistants and need to pass API keys, database URLs, or other secrets to the agent without putting them in .env files. It's also for anyone who wants a local, open password manager that works with KeePass and can sync via existing file-sync services.

Highlights

• Local, KeePass-compatible vault (KDBX 4) with no account or network.
• Agent approval via MCP: deny, allow once, allow for 1 hour, or always for a project+profile.
• Inject-only runs that put secrets in a command's environment, never on disk.
• Project profiles (dev, staging, prod) with automatic prompting for prod.
• .env.keypaste files with references like KEY=kp://project/profile/KEY that are safe to commit.
• Scoped, expiring tokens for CI (e.g., read:acme-api/staging/*).
• Encrypted share links for one field or an entry's login, with open limits.
• Built-in password generator (8–256 chars) and passphrase generator (6–32 words).
• Audit log with a hash chain for every agent request.