Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
PRTG Network Monitor MCP
Overview
Description from the maker (original English)
Every PRTG API v2 endpoint, plus a fleet view across every client's PRTG core: alarms, status
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
- You need to fill in: PRTG_API_KEY, PRTG_SERVER, PRTG_FLEET_KEYS, PRTG_MCP_HTTP_TOKEN
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
PRTG_API_KEY,PRTG_SERVER,PRTG_FLEET_KEYS,PRTG_CORE,PRTG_BASE_URL,PRTG_SKIP_TLS_VERIFY,PRTG_USER_AGENT,PRINTING_PRESS_CLIENT_PROFILE,PRTG_MCP_READ_ONLY,PRTG_NO_LOCAL_DATA,PRTG_MCP_HTTP_TOKEN
Values 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.
Values you fill in
- API key for your PRTG core (Account Settings > My Account > API Keys).
- Your PRTG core's host and API v2 port, for example prtg.example.com:1616.
- Optional. name=key pairs (comma-separated) for cores registered with core add; used by the fleet tools.
PRTG_COREenvOptional. Name of a registered core to point every single-core tool at.PRTG_BASE_URLenvOptional. Full API v2 base URL; overrides PRTG_SERVER when set.PRTG_SKIP_TLS_VERIFYenvOptional. Set to true only for a PRTG core with a self-signed certificate.PRTG_USER_AGENTenvOptional. Overrides the User-Agent the CLI sends to your PRTG core.PRINTING_PRESS_CLIENT_PROFILEenvOptional. Binds the MCP server to one saved client profile.PRTG_MCP_READ_ONLYenvOptional. Set to exactly 1 to expose only read-only tools and refuse any state-changing call.PRTG_NO_LOCAL_DATAenvOptional. Set to 1 to keep no local copy of API responses.- Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account servosity, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32564 servers in this category
- Published to the registry more recently than 96% of the other 32564 servers in this category
- Basic checks equal to or better than 100% of the other 32564 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is PRTG Network Monitor MCP safe?
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.
What keys or codes does it need?
You need to fill in: PRTG_API_KEY, PRTG_SERVER, PRTG_FLEET_KEYS, PRTG_MCP_HTTP_TOKEN
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry yesterday.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Tools MCP
Alternatives
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
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
Tools MCP
by First-CH
Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more
Runs on your computerUpdated today
Install
README from the maker
Open the README
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.
PRTG + AI - for ChatGPT, Claude, GitHub Copilot, Microsoft 365 Copilot, Gemini, and any agent that speaks MCP
Unofficial. Community-built Claude Code Skill and MCP server for the PRTG
API. Not affiliated with, endorsed by, or sponsored by Paessler GmbH.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every PRTG API v2 endpoint, plus a fleet view across every client's PRTG core: alarms, status, handoffs, hygiene and safe bulk actions in one command. 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.
Works with your agent
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the PRTG skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register prtg-mcp (no JSON editing). |
| ChatGPT (paid plans) | Run installer, host prtg-mcp over HTTPS with PRTG_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 prtg-mcp to mcp.json under the servers key, then pick Agent mode. |
For ChatGPT, run prtg-mcp --transport http with PRTG_MCP_HTTP_TOKEN set, on an HTTPS host; every request sends that token. See mcp-install.md.
Also for the Microsoft and Google stacks
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 prtg-mcp over HTTPS with PRTG_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.
Install in 60 seconds
Fastest for Claude Desktop - one-click .mcpb
Download PRTG MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every PRTG 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 prtg@msp-skills
Path A - paste one prompt into your AI agent (recommended)
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the PRTG 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/prtg/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/prtg/install.ps1 | iex. Then authenticate per the README and runprtg-cli --helpto explore.
The same prompt works in any agent that can run shell.
Path B - run the installer yourself
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/prtg/install.ps1 | iexmacOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/prtg/install.sh)The installer drops both prtg-cli (the CLI) and prtg-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
prtg-cli --versionUpgrade to the latest 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/prtg/install.sh)Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/prtg/install.ps1 | iexClaude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update prtg@msp-skills.
Add to Claude Desktop, GitHub Copilot, Gemini CLI, Microsoft 365 Copilot, or another MCP client
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.
Install for Hermes
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/prtg --forceInside a Hermes chat session:
/skills install servosity/msp-skills/skills/prtg --forceHermes speaks MCP natively, so it can also use the prtg-mcp server directly - same install path, same env vars.
Install for OpenClaw
Tell your OpenClaw agent (copy this):
Install the prtg skill from https://github.com/servosity/msp-skills/tree/main/skills/prtg. The skill defines how its required CLI (
prtg-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.
Authenticate
Create an API key in each PRTG core under Account Settings > My Account > API Keys. The PRTG application server answers API v2 on port 1616 by default.
One core - macOS / Linux:
export PRTG_SERVER=prtg.acme.example:1616export PRTG_API_KEY= prtg-cli doctor
One core - Windows (PowerShell):
$env:PRTG_SERVER = "prtg.acme.example:1616"$env:PRTG_API_KEY = " " prtg-cli doctor
Every client core (for the fleet commands) - register each core once, and put every core's key in one variable, PRTG_FLEET_KEYS, as name=key pairs separated by commas:
prtg-cli core add acme --server prtg.acme.example:1616prtg-cli core add globex --server 10.20.0.5:1616 export PRTG_FLEET_KEYS='acme= ,globex= ' prtg-cli core list
prtg-cli core add acme --server prtg.acme.example:1616prtg-cli core add globex --server 10.20.0.5:1616 $env:PRTG_FLEET_KEYS = "acme= ,globex= " prtg-cli core list
core list shows key_set: true for each core whose key variable is set. A core with a self-signed certificate takes core add --insecure-tls (that core only); for a single core use PRTG_SKIP_TLS_VERIFY=true. doctor checks config, paths, and API reachability, and reports whether credentials are loaded - it does not validate them. Run a read command to confirm the credential actually works end-to-end.
What this skill does
Register each client's PRTG core once (prtg-cli core add --server , keys in PRTG_FLEET_KEYS), then ask across all of them:
| Question your MSP keeps asking | Command |
|---|---|
| Which client core is in the worst shape right now? | prtg-cli fleet status --agent |
| What is down and unacknowledged across every core, oldest first? | prtg-cli fleet alarms --status down --unacked --agent |
| What changed overnight: new alarms and recoveries? | prtg-cli fleet handoff --since 12h --agent |
| What has been paused or acknowledged with no end date for over a week? | prtg-cli fleet silenced --indefinite --older-than 7d --agent |
| Which cores are behind on version, have a license or maintenance ending, or a disconnected probe? | prtg-cli fleet drift --within 30d --agent |
| Acknowledge one outage on every client with the ticket number (preview first) | prtg-cli fleet ack --filter 'name = "Ping"' --message 'TKT-4411 ISP outage' --duration 2h |
| Pause a device on every core for patch night (preview first) | prtg-cli fleet pause --kind device --filter 'name = "fw01"' --duration 2h --message 'Patch night' |
The fleet commands ask every registered core live, in one run. A core that fails to answer stays in the result as an error row rather than being counted as healthy; the command exits 0 when some cores fail and non-zero only when all of them do. fleet ack, fleet pause and fleet resume only preview until you add --yes. Every PRTG API v2 operation is also a typed command you can point at one core with --core .
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
What makes this different
Most PRTG integrations talk to one PRTG server with one key. That is fine when you run one core. It stops working when every client has its own core and the question is "what is down for everyone".
This connector is built for one core per client. Each core is registered once with its server and the name of the environment variable that holds its key (the key itself is never written to disk). fleet alarms, fleet status, fleet handoff, fleet silenced and fleet drift ask every core in one run and return one merged, worst-first result with a core column, and fleet exec does the same for any read-only API v2 path. fleet sync refreshes a separate offline mirror per core, for search and analytics without a live call per question.
The pain this closes
Many MSPs give each client its own PRTG core: Paessler's MSP offering says PRTG MSP Edition supports running clients on fully separate instances. Each core then has its own web interface, alarm list and API key, so the start-of-shift question "what is down for every client" means opening each one. Paessler retired its multi-server desktop client, the Enterprise Console, from PRTG 19.4.53 and points users to PRTG Desktop and PRTG MultiBoard, which are viewers for a person at a de
Only the beginning is shown; read the rest in the repo