Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Local-first secret scanning, rotation, vault, and audit-log tools for AI agents.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"holster": {
"command": "uvx",
"args": [
"holster-mcp"
]
}
}
}Run this in your terminal
claude mcp add holster -- uvx holster-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"holster": {
"command": "uvx",
"args": [
"holster-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"holster": {
"type": "stdio",
"command": "uvx",
"args": [
"holster-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026
The registry name was verified against the domain nautaai.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 6 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Beefi
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
US public company data from SEC EDGAR: financials, insider trades, 13F holdings, filings and macro.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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.
The server locates holster-doctor in this order:
HOLSTER_DOCTOR_BINholster_mcp/bin/holster-doctorholster-doctor on PATHtarget/release/holster-doctortarget/debug/holster-doctorholster.scan_repoInput:
{"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_gitignoreInput:
{"path": "/absolute/repo/path"}
Output:
{
"ok": true, "missing_patterns": [".env.local"], "existing_safe": [".env"], "existing_unsafe": [], "suggested_append": ".env.local\n*.pem" }
holster.rotation_playbookInput:
{"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."] }
Day 1 wheels are built for:
aarch64-apple-darwin)x86_64-unknown-linux-gnu)The wheels bundle the platform's holster-doctor binary and are intentionally not universal.
Paid tools are local-only wrappers around holster-cli and are gated by a Holster license.
License lookup order:
license_key argument passed to a paid MCP toolHOLSTER_LICENSE_KEY~/.holster/config.tomlSupported 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 path lookup order:
HOLSTER_VAULT_PATH~/.holster/config.tomlholster.vault_addInput:
{
"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_rotateDay 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_logInput:
{"provider": "github", "account": "nauta-ai", "since_days": 30}
Output:
{"ok": true, "events": [{"ts": "...", "action": "add", "provider": "github", "account": "nauta-ai", "ok": true}]}
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.