pypi holster-mcpstdioMITupdated 3mo ago
Local-first API key manager for AI developers.
What can you do with Holster MCP?
Holster
Local-first API key manager for AI developers.
Install
macOS Apple Silicon (M-series)
- Download
holster-cli-macos-arm64.tar.gz+.sha256from the latest release: https://github.com/nauta-ai/holster/releases/latest - Extract:
tar xzf holster-cli-macos-arm64.tar.gz - Verify:
shasum -a 256 -c holster-cli-macos-arm64.tar.gz.sha256 - Install:
sudo mv holster-cli /usr/local/bin/ - If macOS blocks first run:
xattr -d com.apple.quarantine /usr/local/bin/holster-cli - Verify:
holster-cli --version
macOS Intel (x86_64, since v0.7.0)
- Download
holster-cli-macos-x86_64.tar.gz+.sha256from the latest release. - Same extract / verify / install steps as above.
Linux x86_64
- Download
holster-cli-linux-x86_64.tar.gz+.sha256from the latest release. - Extract:
tar xzf holster-cli-linux-x86_64.tar.gz - Verify:
shasum -a 256 -c holster-cli-linux-x86_64.tar.gz.sha256 - Install:
sudo mv holster-cli /usr/local/bin/ - Verify:
holster-cli --version
Password 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.
Windows x86_64 (since v0.7.0)
- Download
holster-cli-windows-x86_64.zip+.sha256from the latest release. - Verify: in PowerShell,
(Get-FileHash -Algorithm SHA256 holster-cli-windows-x86_64.zip).Hashshould match the value in the.sha256file. - Extract:
Expand-Archive holster-cli-windows-x86_64.zip -DestinationPath . - Move
holster-cli.exesomewhere on$env:Path(e.g.C:\Users\<you>\bin\after adding that folder to PATH). - Verify:
holster-cli.exe --version
Password handling on Windows: macOS Keychain is not available. Use --password-env <ENV_NAME> or --password-stdin.
Rotating the master password (since v0.7.0)
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:
- After any suspected credential exposure
- After a team member who knew the master leaves
- Quarterly as routine hygiene
- Whenever the master appears in plaintext somewhere (logs, configs, transcripts)
Password sources (since v0.7.0)
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 Keychain- Interactive TTY prompt (fallback)
This makes Holster scriptable from CI, launchd, systemd, and daemon contexts without requiring an interactive TTY.
Documentation
Read docs/framework/00_README.md to start.
holster guard
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
Status
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.
Install
Add Holster MCP to your client. Pick the one you use.
claude mcp add holster-mcp -- uvx holster-mcpcodex mcp add holster-mcp -- uvx holster-mcpamp mcp add holster-mcp -- uvx holster-mcp{
"mcpServers": {
"holster-mcp": {
"command": "uvx",
"args": [
"holster-mcp"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"holster-mcp": {
"command": "uvx",
"args": [
"holster-mcp"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"holster-mcp","command":"uvx","args":["holster-mcp"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"holster-mcp": {
"command": "uvx",
"args": [
"holster-mcp"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"holster-mcp": {
"command": "uvx",
"args": [
"holster-mcp"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"holster-mcp": {
"command": "uvx",
"args": [
"holster-mcp"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"holster-mcp": {
"type": "local",
"command": "uvx",
"args": [
"holster-mcp"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"holster-mcp": {
"command": {
"path": "uvx",
"args": [
"holster-mcp"
]
}
}
}
}Add to your Zed `settings.json`.
uvx holster-mcpRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation25/25
- Maintenance16/25
- Trust16/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 89 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 0.1.1Latest | May 17, 2026 |