Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Readable filters, alias-named resources, full exports, and the KPI history MSPbots doesn't keep.
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.
MSPBOTS_API_KEY, MSPBOTS_BASE_URL, MSPBOTS_MCP_HTTP_TOKEN, MSPBOTS_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILE, MSPBOTS_MCP_READ_ONLY, MSPBOTS_NO_LOCAL_DATAAls 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.
MSPBOTS_BASE_URL envMSPBOTS_USER_AGENT envPRINTING_PRESS_CLIENT_PROFILE envMSPBOTS_MCP_READ_ONLY envMSPBOTS_NO_LOCAL_DATA 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: MSPBOTS_API_KEY, MSPBOTS_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.8) 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, Zoo MCP
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.
An MCP server that provides access to the Zoo API for various CAD operations and tools.
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 MSPbots
API. Not affiliated with, endorsed by, or sponsored by MSPbots, Inc.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
The first MSPbots tool we could find anywhere (June 2026) - readable filters, alias-named resources, full exports, and the KPI history MSPbots itself doesn't keep. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. 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 MSPbots skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register mspbots-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add mspbots-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| 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 mspbots-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs mspbots-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote server, which msp-skills does not support yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
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.
.mcpbClaude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companionmspbots-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or setMSPBOTS_CLI_PATHto an existing binary). Details: #331.
Download MSPbots MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every MSPbots 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 mspbots@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the MSPbots 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/mspbots/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/mspbots/install.ps1 | iex. Then authenticate per the README and runmspbots-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/mspbots/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/mspbots/install.sh)
The installer drops both mspbots-cli (the CLI) and mspbots-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
mspbots-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/mspbots/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/mspbots/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 mspbots@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 ChatGPT desktop app. 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/mspbots --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/mspbots --force
Hermes speaks MCP natively, so it can also use the mspbots-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the mspbots skill from https://github.com/servosity/msp-skills/tree/main/skills/mspbots. The skill defines how its required CLI (
mspbots-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 MSPbots portal):
MSPBOTS_API_KEY=<value> mspbots-cli doctor
doctor checks config, paths, and API reachability and reports whether a credential is loaded. The MSPBots API exposes no argument-free GET endpoint, so doctor cannot verify the key itself - it says not verified rather than claiming health. Run any read command to confirm the key works end-to-end.
| Question your MSP keeps asking | Command |
|---|---|
| Is our open-ticket backlog up or down versus last week? | mspbots-cli trend open_tickets --agg count |
| What changed in open tickets since the last snapshot? | mspbots-cli diff open_tickets |
| Pull the open tickets updated since June 1 | mspbots-cli pull open_tickets --where "Update Date >= 2026-06-01" |
| What columns does this dataset have, and what types? | mspbots-cli describe open_tickets |
| Export the entire dataset to CSV for the QBR deck | mspbots-cli export open_tickets --format csv |
| Capture today's KPI snapshot (schedule it - history accrues) | mspbots-cli snapshot open_tickets |
| Stop pasting 19-digit IDs - name the dataset once | mspbots-cli registry add open_tickets 1534956341424005122 |
| Are my API key and resource bindings working? | mspbots-cli doctor |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
There was no MSPbots tool to be different *from* - as of June 2026 we could find no published CLI, SDK, or MCP server for the MSPbots Public API. And a thin wrapper would inherit everything painful about that API: two endpoints, 19-digit resource IDs, comma-encoded filters, no list endpoint, no metadata, no history. It dies the moment you ask "is our backlog up or down versus last week" - the API only knows *now*.
This skill adds the missing layers locally. registry add gives resources names instead of snowflake IDs. pull --where "Update Date >= 2026-06-01" compiles readable predicates into the wire DSL. export walks every page automatically. And snapshot + diff + trend keep timestamped copies in a local SQLite store - the KPI history MSPbots itself doesn't keep, computed offline with zero API calls.
MSPbots' own Public API documentation (the wiki.mspbots.ai Public API article, archived April 2024) describes the entire programmatic surface: two GET endpoints, resource IDs copied one at a time out of Settings > Public API, filters encoded as comma-rules in query params, rate limits with unspecified numbers, and intermittent HTTP 502s on heavy widget fetches. No history, no enumeration, no tooling - not even a curl gist.
So the ops manager who lives in MSPbots dashboards keeps the week-over-week column by hand: screenshot the widget on Monday, paste the count into a spreadsheet, repeat. The trend dies the week someone forgets.
mspbots-cli snapshot open_tickets - capture a timestamped copy of any dataset or widget into local SQLite. Schedule it and history accrues.mspbots-cli trend open_tickets --agg count - the week-over-week answer, computed from your snapshots, offline.mspbots-cli diff open_tickets - row-level added/removed/changed between any two snapshots.mspbots-cli pull open_tickets --where "Update Date >= 2026-06-01" - readable filters compiled into the comma-encoded DSL, correct the first time.mspbots-cli export open_tickets --format csv - the full table, auto-paginated, with an honest partial-dump flag when a page cap is hit.See pain-point.md for the longer narrative.
Yes, in the ChatGPT desktop app. It runs MCP servers locally (STDIO), the way mspbots-mcp
Nur der Anfang wird gezeigt; den Rest findest du im Repo