Holster MCP
Holster MCP exposes local Holster Doctor checks to MCP-compatible agents. The server is local-first: free tools shell out to the bundled holster-doctor binary and never send repository contents to a network service.
Install
From PyPI:
pip install holster-mcp
Development install:
cd /path/to/holster/mcp
python3.11 -m pip install -e '.[dev]'
Runtime command:
holster-mcp
MCP client config:
{
"mcpServers": {
"holster": {
"command": "uvx",
"args": ["holster-mcp"]
}
}
}
See the main Holster README for vault and holster-cli release binary installation.
License: MIT for the MCP package.
Binary Resolution
The server locates holster-doctor in this order:
HOLSTER_DOCTOR_BIN- Packaged wheel binary at
holster_mcp/bin/holster-doctor holster-doctoronPATH- Repo-local
target/release/holster-doctor - Repo-local
target/debug/holster-doctor
Free Tools
holster.scan_repo
Input:
{"path": "/absolute/repo/path", "depth": 3}
Output:
{
"ok": true,
"scanned_files": 15,
"findings": [
{
"file": "src/main.py",
"line": 12,
"secret_kind": "openai_api_key",
"severity": "error",
"suggestion": "Rotate this key and move it into a local vault."
}
]
}
holster.check_gitignore
Input:
{"path": "/absolute/repo/path"}
Output:
{
"ok": true,
"missing_patterns": [".env.local"],
"existing_safe": [".env"],
"existing_unsafe": [],
"suggested_append": ".env.local\n*.pem"
}
holster.rotation_playbook
Input:
{"provider": "github"}
Output:
{
"ok": true,
"provider": "github",
"steps": ["Create a replacement token...", "Update local consumers...", "Revoke the old token..."],
"estimated_minutes": 15,
"warnings": ["Do not revoke the old credential until the replacement has been verified."]
}
Platform Wheels
Day 1 wheels are built for:
- macOS ARM (
aarch64-apple-darwin) - Linux x86_64 (
x86_64-unknown-linux-gnu)
The wheels bundle the platform's holster-doctor binary and are intentionally not universal.
Paid Tools
Paid tools are local-only wrappers around holster-cli and are gated by a Holster license.
License Configuration
License lookup order:
license_keyargument passed to a paid MCP toolHOLSTER_LICENSE_KEY~/.holster/config.toml
Supported config.toml shapes:
license_key = "holster_live_ABCDEFGHIJKLMNOPQRSTUVWX"
vault_path = "/absolute/path/to/holster-vault.db"
or:
[license]
key = "holster_live_ABCDEFGHIJKLMNOPQRSTUVWX"
[vault]
path = "/absolute/path/to/holster-vault.db"
License cache:
~/.holster/licenses.db
If no license is configured, the first paid-tool call creates a local 7-day trial key with prefix holster_trial_.
Vault Configuration
Vault path lookup order:
- explicit tool argument where supported
HOLSTER_VAULT_PATH~/.holster/config.toml
holster.vault_add
Input:
{
"provider": "github",
"account": "nauta-ai",
"secret": "user-pasted-secret",
"label": "primary"
}
Output:
{"ok": true, "vault_entry_id": "123e4567-e89b-12d3-a456-426614174000", "error": null}
The secret value is never placed in CLI argv, logs, or structured error output.
holster.vault_rotate
Day 2 supports github and stripe.
Without new_secret, the tool returns the provider playbook and waits for the human to rotate/paste the replacement:
{
"provider": "github",
"account": "nauta-ai",
"vault_entry_id": "old-id"
}
With new_secret, the replacement is added to the local vault and the old entry is marked superseded when the installed CLI supports that command.
holster.audit_log
Input:
{"provider": "github", "account": "nauta-ai", "since_days": 30}
Output:
{"ok": true, "events": [{"ts": "...", "action": "add", "provider": "github", "account": "nauta-ai", "ok": true}]}
License Architecture
flowchart TD
A["Paid MCP tool call"] --> B["Resolve license key from arg/env/config"]
B --> C{"Key present?"}
C -- "No" --> D["Create local 7-day trial in ~/.holster/licenses.db"]
C -- "Yes" --> E["Read ~/.holster/licenses.db"]
D --> F{"Trial valid?"}
E --> G{"Cached license valid?"}
G -- "Valid" --> H["Dispatch paid tool"]
G -- "Expired but within 7-day grace" --> I["Dispatch with license_warning"]
G -- "Missing/stale live key" --> J["Stripe refresh: Customer.retrieve + Subscription.list"]
J -- "Active" --> K["Update cache valid_until + last_checked"]
J -- "Inactive/error/no API key" --> L["Return license_required_or_expired"]
F -- "Valid" --> H
F -- "Expired" --> L
K --> H
I --> H
H --> M["Local holster-cli subprocess"]
The background poller refreshes cached live licenses every 10 minutes after a paid tool validates. There is no webhook receiver in Day 2 and no telemetry in V1.
Metadata
Release files for holster-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| holster_mcp-0.1.1.tar.gz | 18.8 kB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| holster_mcp-0.1.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.17+ x86-64 | Details |
| holster_mcp-0.1.1-cp311-cp311-macosx_11_0_arm64.whl | CPython 3.11 | CPython 3.11 | macOS 11.0+ ARM64 | Details |
Total release size: 2.7 MB
Release files / holster_mcp-0.1.1.tar.gz
| Download URL | holster_mcp-0.1.1.tar.gz |
|---|---|
| Size | 18.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e96319c93a3484c5faff7e39d3e8048ce9fb08b3a0e06dbfa3dd4ec84d0bf85b
|
|
BLAKE2b-256 checksum How to use checksums |
5a36d2140df2f106279ee6c8d0b7a72f66982ba25f138fa300782c9ed0deb4ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 17, 2026.
Transparency logRelease files / holster_mcp-0.1.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | holster_mcp-0.1.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
a618f89973d830bd283347cdb11efee28038b984e60e66aeee1ce144b291e5a7
|
|
BLAKE2b-256 checksum How to use checksums |
fa51b53d13c8e0cc1e9bdab15208f822a8800b02ca266ff69019005ffb8eb110
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 17, 2026.
Transparency logRelease files / holster_mcp-0.1.1-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | holster_mcp-0.1.1-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
50714cef6fa38b51035e86c68a21c9cc1ebd859f3b2e55fecd13698d899caae7
|
|
BLAKE2b-256 checksum How to use checksums |
3652339554fa2977b3b81fcfd804aaee0ecef5d07f037967d77b6e40fa35c313
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 17, 2026.
Transparency log