Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
The first non-PowerShell client for the Nerdio Manager for MSP API - cross-account AVD fleet
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.
NERDIO_BASE_URL, NERDIO_TOKEN_URL, NERDIO_CLIENT_ID, NERDIO_CLIENT_SECRET, NERDIO_OAUTH_SCOPE, NERDIO_NO_CONFIG_WRITE, NERDIO_MCP_READ_ONLY, NERDIO_NO_LOCAL_DATA, NERDIO_MCP_HTTP_TOKEN, NERDIO_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILEValues 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.
NERDIO_NO_CONFIG_WRITE envNERDIO_MCP_READ_ONLY envNERDIO_NO_LOCAL_DATA envNERDIO_USER_AGENT 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 6, 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: NERDIO_BASE_URL, NERDIO_TOKEN_URL, NERDIO_CLIENT_ID, NERDIO_CLIENT_SECRET, NERDIO_OAUTH_SCOPE, NERDIO_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
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.9) reached the registry today.
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, HotCodePush
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.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
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 Nerdio Manager
API. Not affiliated with, endorsed by, or sponsored by Nerdio, Inc.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
The first non-PowerShell client for the Nerdio Manager for MSP API - cross-account AVD fleet audits, async-job plumbing, and offline search no other Nerdio tool has. 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 Nerdio Manager skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register nerdio-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add nerdio-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 nerdio-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs nerdio-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 companionnerdio-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 setNERDIO_CLI_PATHto an existing binary). Details: #331.
Download Nerdio Manager MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Nerdio Manager 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 nerdio@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Nerdio Manager 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/nerdio/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/nerdio/install.ps1 | iex. Then authenticate per the README and runnerdio-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/nerdio/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/nerdio/install.sh)
The installer drops both nerdio-cli (the CLI) and nerdio-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
nerdio-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/nerdio/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/nerdio/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 nerdio@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/nerdio --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/nerdio --force
Hermes speaks MCP natively, so it can also use the nerdio-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the nerdio skill from https://github.com/servosity/msp-skills/tree/main/skills/nerdio. The skill defines how its required CLI (
nerdio-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 Nerdio Manager portal):
NERDIO_BASE_URL=<value> NERDIO_TOKEN_URL=<value> NERDIO_CLIENT_ID=<value> NERDIO_CLIENT_SECRET=<value> NERDIO_OAUTH_SCOPE=<value> nerdio-cli doctor
doctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.
| Question your MSP keeps asking | Command |
|---|---|
| Which host pools have autoscale off or drifting across every customer? | nerdio-cli fleet autoscale-audit |
| What is running right now across all accounts, and where? | nerdio-cli fleet host-estate |
| What did each customer get billed this period, and who is unpaid? | nerdio-cli fleet billing-rollup --period 2026-05-01:2026-05-31 --unpaid-only |
| Which customers' Azure usage spiked month-over-month? | nerdio-cli usages drift --from 2026-04-01:2026-04-30 --to 2026-05-01:2026-05-31 |
| List every customer account I manage | nerdio-cli accounts |
| Show the host pools for one account | nerdio-cli host-pools list |
| Which Intune devices does this account have? | nerdio-cli devices list |
| Did that backup or provisioning job actually finish? | nerdio-cli job wait |
| Run one scripted action across many accounts and wait for all of them | nerdio-cli scripted-actions fan-run --accounts 101,102,103 --wait |
| Search everything I have synced, offline | nerdio-cli search |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most Nerdio Manager integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking "which host pools across all 40 of my customers have autoscale turned off this quarter" - because the NMM API only returns one account, or one billing period, per call.
This skill syncs Nerdio Manager into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like fleet autoscale-audit, fleet billing-rollup, and usages drift join across customer accounts, host pools, invoices, and usage windows - work a stateless API wrapper can't do. And because every NMM change is async, job wait turns "did it finish?" into a scriptable primitive that exits non-zero when the job actually failed.
On r/msp, the recurring Nerdio refrain is that autoscale is the whole reason to buy it - and the hardest thing to keep honest across a fleet. There's no single view of which host pools, in which customer tenants, actually have scaling enabled, so idle session hosts quietly bleed Azure spend until the invoice lands. Every NMM install is per-tenant, so even "how many hosts are running right now across all clients" means logging into each portal one at a time. And because every change is async, the portal makes you babysit the Jobs page to know whether anything finished.
This skill answers those at the fleet level:
Only the beginning is shown; read the rest in the repo