Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Every NetSapiens v2 endpoint plus a reseller-wide fleet view: seat limits, offline phones, unrouted
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.
NETSAPIENS_API_KEY, NETSAPIENS_SERVER, NETSAPIENS_BASE_URL, PRINTING_PRESS_CLIENT_PROFILE, NETSAPIENS_MCP_READ_ONLY, NETSAPIENS_NO_LOCAL_DATA, NETSAPIENS_MCP_HTTP_TOKEN, NETSAPIENS_USER_AGENT, NETSAPIENS_MCP_UPLOAD_ROOTValues 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.
NETSAPIENS_BASE_URL envNETSAPIENS_MCP_READ_ONLY envNETSAPIENS_NO_LOCAL_DATA envNETSAPIENS_USER_AGENT envNETSAPIENS_MCP_UPLOAD_ROOT 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: NETSAPIENS_API_KEY, NETSAPIENS_SERVER, PRINTING_PRESS_CLIENT_PROFILE, NETSAPIENS_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.1) 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, Reelsaw
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.
Drive a self-hosted Reelsaw: turn long videos into vertical clips, edit, re-render and export them.
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 NetSapiens
API. Not affiliated with, endorsed by, or sponsored by Crexendo, Inc.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every NetSapiens v2 endpoint plus a reseller-wide fleet view: seat limits, offline phones, unrouted numbers and E911 gaps across every client at once. 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 NetSapiens skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register netsapiens-mcp (no JSON editing). |
| ChatGPT (paid plans) | Run installer, host netsapiens-mcp over HTTPS with NETSAPIENS_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 netsapiens-mcp to mcp.json under the servers key, then pick Agent mode. |
For ChatGPT, run netsapiens-mcp --transport http with NETSAPIENS_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 netsapiens-mcp over HTTPS with NETSAPIENS_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 NetSapiens MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every NetSapiens 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 netsapiens@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the NetSapiens 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/netsapiens/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/netsapiens/install.ps1 | iex. Then authenticate per the README and runnetsapiens-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/netsapiens/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/netsapiens/install.sh)
The installer drops both netsapiens-cli (the CLI) and netsapiens-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
netsapiens-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/netsapiens/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/netsapiens/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 netsapiens@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/netsapiens --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/netsapiens --force
Hermes speaks MCP natively, so it can also use the netsapiens-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the netsapiens skill from https://github.com/servosity/msp-skills/tree/main/skills/netsapiens. The skill defines how its required CLI (
netsapiens-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 NetSapiens portal):
NETSAPIENS_API_KEY=<value> NETSAPIENS_SERVER=<value> netsapiens-cli doctor
doctor checks config, paths and API reachability, and makes one authenticated call to report whether the server accepted the credential. A scope-limited key shows as a warning; run a read command to confirm the access you need.
Credentials the API hands back, such as the key from apikeys create or the tokens from jwt create, print as : read a new key's value in the NetSapiens portal.
| Question your MSP keeps asking | Command |
|---|---|
| Which clients are over or near a user, queue, auto attendant or conference limit? | netsapiens-cli fleet seats --flagged --agent |
| Which phones are unregistered, high-latency or never provisioned? | netsapiens-cli fleet offline --agent |
| Which phone numbers route to a missing or unreachable user, queue or attendant? | netsapiens-cli fleet dids --problems-only --agent |
| Which domains, users and devices are missing E911 caller ID or address data? | netsapiens-cli fleet e911 --agent |
| Which users had unanswered inbound calls this week? | netsapiens-cli fleet missed --window 7d --agent |
| Which call queues are dropping callers, and are their agents reachable? | netsapiens-cli fleet queues --window 7d --agent |
| What was added, removed or re-pointed since my last check? | netsapiens-cli fleet changes --agent |
| Whose number is this, and which phones ring for it? | netsapiens-cli trace 6025550142 --agent |
The fleet audits read a local mirror: run netsapiens-cli sync first (each audit prints the exact sync --resources ... line it needs when the mirror is missing or stale). fleet missed and fleet queues read CDRs and queue statistics live.
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most NetSapiens 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 of my 40 client domains are over their seat limit, and which of their numbers route nowhere?"
This skill syncs NetSapiens 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 dids, fleet e911 and trace join across domains, users, devices, phone numbers, call queues, auto attendants and E911 addresses - work a stateless API wrapper can't do.
A NetSapiens reseller runs dozens of client domains on one platform, and the reseller portal answers one domain at a time. Seat true-ups, offline phones and numbers that still point at a departed user are all found by opening every client, or by the client calling to complain.
E911 is where that gap costs money. IPComms' E911 terms, a SIP trunking carrier's, bill an unregistered-911 fee of $250 per call placed from a number with no registered address, and Kari's Law and RAY BAUM's Act put the dispatchable-location duty on whoever runs the phone system. MSPs are asking AI agents to reach NetSapiens: phoneware/netsapiens-mcp and MSPbots' oitvoip-mcp both exist, and both are under a year old.
fleet seats --flagged: every client over or near a limit, ready for the monthly true-up.fleet offline: unregistered, stale or high-latency phones before the client notices.fleet dids --problems-only: numbers that ring nowhere.fleet e911: caller-ID and address gaps, as input to a Kari's Law / RAY BAUM's Act review (it checks the data, not 911 dialing).fleet changes: what was added, removed or re-pointed since last week.See 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 NetSapiens MCP server runs locally over stdio by default. Its HTTP mode (netsapiens-mcp --transport http) serves `ht
Only the beginning is shown; read the rest in the repo