Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Every PRTG API v2 endpoint, plus a fleet view across every client's PRTG core: alarms, status
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
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_TOKENLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Descargar el archivo .mcpb del creador
El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.
Ejecuta esto en tu terminal
Completa los valores vacíos antes de ejecutarlo.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
PRTG_CORE envPRTG_BASE_URL envPRTG_SKIP_TLS_VERIFY envPRTG_USER_AGENT envPRINTING_PRESS_CLIENT_PROFILE envPRTG_MCP_READ_ONLY envPRTG_NO_LOCAL_DATA envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub servosity, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: PRTG_API_KEY, PRTG_SERVER, PRTG_FLEET_KEYS, PRTG_MCP_HTTP_TOKEN
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.1) llegó al registro ayer.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Toggl 2.0
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Toggl 2.0 MCP server for tasks, projects, time entries, and workspace operations.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.
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.
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.
.mcpbDownload 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
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.
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/prtg/install.ps1 | iex
macOS / 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 --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 | 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 prtg@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/prtg --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/prtg --force
Hermes speaks MCP natively, so it can also use the prtg-mcp server directly - same install path, same env vars.
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.
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:1616
export 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:1616
prtg-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:1616
prtg-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.
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.
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.
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
Solo se muestra el principio; lee el resto en el repo