Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Readable filters, alias-named resources, full exports, and the KPI history MSPbots doesn't keep.
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.
MSPBOTS_API_KEY, MSPBOTS_BASE_URL, MSPBOTS_MCP_HTTP_TOKEN, MSPBOTS_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILE, MSPBOTS_MCP_READ_ONLY, MSPBOTS_NO_LOCAL_DATAValues marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
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.
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.
MSPBOTS_BASE_URL envMSPBOTS_USER_AGENT envPRINTING_PRESS_CLIENT_PROFILE envMSPBOTS_MCP_READ_ONLY envMSPBOTS_NO_LOCAL_DATA envThese 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 7, 2026
The registry name was verified with the GitHub account servosity, which owns the repo
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.
You need to fill in: MSPBOTS_API_KEY, MSPBOTS_MCP_HTTP_TOKEN
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.8) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Python MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ 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.
Local-only Python MCP server for the Files.com API.
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.
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
Only the beginning is shown; read the rest in the repo