Local-first secret scanning, rotation, vault, and audit-log tools for AI agents.
Local-first API key manager for AI developers.
holster-cli-macos-arm64.tar.gz + .sha256 from the latest release: https://github.com/nauta-ai/holster/releases/latesttar xzf holster-cli-macos-arm64.tar.gzshasum -a 256 -c holster-cli-macos-arm64.tar.gz.sha256sudo mv holster-cli /usr/local/bin/xattr -d com.apple.quarantine /usr/local/bin/holster-cliholster-cli --versionholster-cli-macos-x86_64.tar.gz + .sha256 from the latest release.holster-cli-linux-x86_64.tar.gz + .sha256 from the latest release.tar xzf holster-cli-linux-x86_64.tar.gzshasum -a 256 -c holster-cli-linux-x86_64.tar.gz.sha256sudo mv holster-cli /usr/local/bin/holster-cli --versionPassword handling on Linux: macOS Keychain is not available. Use --password-env <ENV_NAME> to read the vault password from an environment variable, or --password-stdin to pipe it via stdin.
holster-cli-windows-x86_64.zip + .sha256 from the latest release.(Get-FileHash -Algorithm SHA256 holster-cli-windows-x86_64.zip).Hash should match the value in the .sha256 file.Expand-Archive holster-cli-windows-x86_64.zip -DestinationPath .holster-cli.exe somewhere on $env:Path (e.g. C:\Users\<you>\bin\ after adding that folder to PATH).holster-cli.exe --versionPassword handling on Windows: macOS Keychain is not available. Use --password-env <ENV_NAME> or --password-stdin.
Holster lets you change the vault's master password without re-creating the vault or losing entries:
holster-cli rotate-master /path/to/vault
# Prompts for OLD master, then NEW master twice (confirm)
This re-encrypts every entry under the new master and regenerates the vault salt under a single SQLite transaction. If the rotation fails or is interrupted, the vault remains intact under the old master.
If you cache the master password in macOS Keychain (common for daemon usage), pass --keychain-update SERVICE,ACCOUNT to update the cached entry in the same command:
holster-cli rotate-master /path/to/vault \
--keychain-update holster-personas-vault,admin
For unattended / scripted rotation:
# OLD pw from Keychain, NEW pw from env
holster-cli rotate-master /path/to/vault \
--old-password-keychain-service holster-personas-vault \
--old-password-keychain-account admin \
--new-password-env NEW_HOLSTER_MASTER
# Both from stdin (one line each, OLD first then NEW)
printf '%s\n%s\n' "$OLD_PW" "$NEW_PW" | \
holster-cli rotate-master /path/to/vault \
--old-password-stdin --new-password-stdin
Rotate the master password:
get, add, rotate-master, and exec-env now accept the master password from multiple sources. Precedence (first non-None wins):
--password-env <NAME> — read from an environment variable--password-stdin — read first line of stdin--password-keychain-service <SVC> [--password-keychain-account <ACCT>] — macOS KeychainThis makes Holster scriptable from CI, launchd, systemd, and daemon contexts without requiring an interactive TTY.
Read docs/framework/00_README.md to start.
holster guard . preflights a repo before you run an AI agent against it or share/commit it. It prints a local RUN verdict, a SHARE verdict, and a ranked fix list without exposing raw secret values.
RUN VERDICT: CAUTION
SHARE VERDICT: RISKY
Why:
1. [SHARE/RISK] OPENAI_API_KEY in .env.local:3
2. [SHARE/RISK] .env.local not gitignored — will be committed
3. [RUN/CAUTION] MCP server "cursor" inherits full shell environment
Fix order:
1. Add .env.local and *.pem to .gitignore
2. Move live keys into the Holster vault (holster add ...)
3. Pin or approve the MCP wrapper command
For a redacted report that is safe to paste into a review thread:
holster guard . --share-report holster-guard-report.md
v0.7.0 — early access. Holster includes the local vault CLI, rotate-master, scriptable password sources, Windows/macOS-x86_64 builds, and early holster guard preflight checks. Vault crate stable since M1.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx holster-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-nautaai-holster-mcp": {
"command": "uvx",
"args": [
"holster-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceHolster MCP works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.