Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Readable filters, alias-named resources, full exports, and the KPI history MSPbots doesn't keep.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
MSPBOTS_API_KEY, MSPBOTS_BASE_URL, MSPBOTS_MCP_HTTP_TOKEN, MSPBOTS_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILE, MSPBOTS_MCP_READ_ONLY, MSPBOTS_NO_LOCAL_DATA标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
链接指向作者自己的文件;我们不托管也不重新打包它。打开文件后,Claude Desktop 会进行安装。
在终端中运行这条命令
运行前请先填写空着的值。
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
MSPBOTS_BASE_URL envMSPBOTS_USER_AGENT envPRINTING_PRESS_CLIENT_PROFILE envMSPBOTS_MCP_READ_ONLY envMSPBOTS_NO_LOCAL_DATA env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 servosity 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:MSPBOTS_API_KEY, MSPBOTS_MCP_HTTP_TOKEN
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.8)于昨天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:Spec Driven Development, Remote Desktop Commander, FlyDocs
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
只显示了开头部分;其余内容请在仓库中阅读