Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Read-only Keeper MSP posture across every client, with history, a change feed and no path to a
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
KEEPER_API_KEY, KEEPER_BASE_URL, KEEPER_MCP_READ_ONLY, KEEPER_NO_LOCAL_DATA, KEEPER_MCP_HTTP_TOKEN, KEEPER_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILEAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Die .mcpb-Datei des Entwicklers herunterladen
Der Link führt zur Datei des Entwicklers selbst; wir hosten sie nicht und verpacken sie nicht neu. Öffne die Datei, dann installiert Claude Desktop sie.
Führe das in deinem Terminal aus
Trag die leeren Werte ein, bevor du ihn startest.
Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
KEEPER_MCP_READ_ONLY envKEEPER_NO_LOCAL_DATA envKEEPER_USER_AGENT envPRINTING_PRESS_CLIENT_PROFILE envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto servosity bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: KEEPER_API_KEY, KEEPER_BASE_URL, KEEPER_MCP_HTTP_TOKEN
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.1.0) kam gestern in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du MCPB auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, topo^alpin
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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.
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Unofficial. Community-built Claude Code Skill and MCP server for the Keeper Security
API. Not affiliated with, endorsed by, or sponsored by Keeper Security, Inc.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Read-only Keeper MSP posture across every client, with history, a change feed and no path to a vault secret. Works with the AI you already use - ChatGPT (Plus/Pro+), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Microsoft 365 Copilot / Copilot Studio and Google Gemini via the remote path. Free, open source, runs on your laptop. Built for MSP owners. No code required.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Keeper Security skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register keeper-mcp (no JSON editing). |
| ChatGPT (paid plans) | Run installer, host keeper-mcp over HTTPS with KEEPER_MCP_HTTP_TOKEN set, then register it as a Developer Mode connector if your connector settings can send the bearer token. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add keeper-mcp to mcp.json under the servers key, then pick Agent mode. |
For ChatGPT, run keeper-mcp --transport http with KEEPER_MCP_HTTP_TOKEN set, on an HTTPS host; every request sends that token. See mcp-install.md.
Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not self-serve. Host keeper-mcp over HTTPS with KEEPER_MCP_HTTP_TOKEN set, then wire it into Copilot Studio (Tools > Add a tool > Model Context Protocol > Server URL) or a declarative agent, if it can send the bearer token. Needs a Copilot Studio license + tenant admin. See mcp-install.md. |
| Google Gemini | Gemini CLI is local - same as Claude Code. The Gemini app is remote - same HTTPS path as ChatGPT. See mcp-install.md. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).
Run more than one agent? Install across all 51+ supported agents in one command:
npx skills add Servosity/msp-skills@latest(requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.
.mcpbDownload Keeper Security MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Keeper Security release on the releases page.)
Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:
/plugin marketplace add Servosity/msp-skills
/plugin install keeper@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Keeper Security Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/keeper/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/keeper/install.ps1 | iex. Then authenticate per the README and runkeeper-cli --helpto explore.
The same prompt works in any agent that can run shell.
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/keeper/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/keeper/install.sh)
The installer drops both keeper-cli (the CLI) and keeper-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
keeper-cli --version
The installer always fetches the current release - re-run it to upgrade:
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/keeper/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/keeper/install.ps1 | iex
Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update keeper@msp-skills.
After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the remote Microsoft 365 Copilot / Copilot Studio path. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/keeper --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/keeper --force
Hermes speaks MCP natively, so it can also use the keeper-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the keeper skill from https://github.com/servosity/msp-skills/tree/main/skills/keeper. The skill defines how its required CLI (
keeper-cli) can be installed via theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Set the credentials the CLI needs (from your Keeper Security portal):
KEEPER_API_KEY=<value> KEEPER_BASE_URL=<value> keeper-cli doctor
doctor checks config and paths, then tests the API key with one read of Service Mode's queue status, so it tells a working key from a rejected one and a wrong base URL. A Service Mode in legacy mode has no queue status, so there doctor says it could not test the key. That read runs no Commander command, so run a real read such as keeper-cli companies list to confirm the key's -c allowlist.
| Question your MSP keeps asking | Command |
|---|---|
| How is every client doing on 2FA, weak passwords and BreachWatch? | keeper-cli posture report --days 90 --agent |
| Which clients have users without 2FA, admins first? | keeper-cli users risk --kind no-2fa --agent |
| What changed since the last posture run, by client and by user? | keeper-cli posture diff --agent |
| Which invites went stale, and who is inactive or locked? | keeper-cli users hygiene --kind invited,inactive --agent |
| Which managed company does this user belong to? | keeper-cli users find jane@example.com --agent |
| How many seats does each client have allocated and active? | keeper-cli companies list --agent |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most password-manager integrations, and an MCP server that only forwards each tool call, answer about one tenant now. That's fine for one user. It stops working when a QBR asks which of 40 clients have admins without 2FA and what moved since last quarter.
posture report reads every managed company in one run through your own Commander Service Mode host and stores the run in a local SQLite file. posture diff, users risk, users hygiene, users find and events list then answer from that file: instant, offline, and the AI sees the answer. Typed reads such as users list go live and are not saved.
Every command it can send is on a short fixed allowlist (keeper-cli allowlist), each with fixed read-only flags, and arguments cannot add a flag or a second command. There is no path to a vault record.
Keeper's password-health and 2FA views are read per tenant (one 2026 review for MSPs describes them as "per tenant"), and comparing against last quarter means keeping the earlier numbers yourself.
posture report: every client's 2FA, password health, BreachWatch, inactivity and seats, in one runposture diff: per-company deltas and per-user changes, such as 2FA turned offusers risk --kind no-2fa: users with 2FA off across every client, admins firstusers hygiene: stale invites, locked, inactive and pending-transfer usersevents list: change events once each, for automationSee pain-point.md for the longer narrative.
Yes, on Plus, Pro, Team, Business, Enterprise, and Education plans (Free tier does not yet expose Developer Mode). ChatGPT connects to remote MCP servers over HTTPS, not local stdio binaries. The Keeper Security MCP server runs locally over stdio by default. Its HTTP mode (keeper-mcp --transport http) serves http://127.0.0.1:7777/mcp, refuses to start until KEEPER_MCP_HTTP_TOKEN is set, requires Authorization: Bearer on every request, and needs --tls-cert/--tls-key for any other address. See mcp-install.md. Step-by-step in mcp-install.md.
Yes - all of them speak MCP. Cross-tool install commands are in the matrix above and the deep-dive in docs/which-agent.md.
No. The recommended install is to paste one sentence into Claude Code or Codex - your agent reads SKILL.md and does the install. The fallback is a one-line installer per OS (bash or PowerShell). Neither path requires writing code. You'll enter your Keeper Security credentials once.
Your data stays on your machine and your own Service Mode host. Typed reads print and are not saved; only posture report saves metrics and per-user facts to a local SQLite file under your user account. The AI agent only sees what
Nur der Anfang wird gezeigt; den Rest findest du im Repo