Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
ConnectWise RMM (Asio) MCP: offline agents, patch posture, and script runs across every client.
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.
CONNECTWISE_RMM_CLIENT_ID, CONNECTWISE_RMM_CLIENT_SECRET, CONNECTWISE_RMM_OAUTH_SCOPE, CONNECTWISE_RMM_BASE_URL, CONNECTWISE_RMM_TOKEN_URL, CONNECTWISE_RMM_USER_AGENT, CONNECTWISE_RMM_MCP_READ_ONLY, CONNECTWISE_RMM_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILELos 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.
CONNECTWISE_RMM_OAUTH_SCOPE envCONNECTWISE_RMM_BASE_URL envCONNECTWISE_RMM_TOKEN_URL envCONNECTWISE_RMM_USER_AGENT envCONNECTWISE_RMM_MCP_READ_ONLY 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 7 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: CONNECTWISE_RMM_CLIENT_ID, CONNECTWISE_RMM_CLIENT_SECRET, CONNECTWISE_RMM_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
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.3) llegó al registro hace 15 días.
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, Foliosio
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.
Read your support inbox, tag conversations and save draft replies from your AI agent. Never sends.
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 ConnectWise RMM
(Asio) partner API. Not affiliated with, endorsed by, or sponsored by ConnectWise, LLC.
Full skill page - install, outcomes, safety model.
66 ConnectWise RMM (Asio) partner API operations, plus a local fleet database, patch-compliance rollups, and script runs you can preview, schedule and watch in one command. 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.
Security note (until this connector is reprinted). Do not run HTTP mode
(
--transport http), not even on localhost. This build checks a token, but it
predates the fix release's request size and time limits. The MCP tools can
also make changes with your credentials. Use the default stdio transport. If
you set up a tunnel for a remote agent, shut it down. A fix is on the way.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the ConnectWise RMM skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register connectwise-rmm-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add connectwise-rmm-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 connectwise-rmm-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs connectwise-rmm-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it 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.
.mcpbDownload ConnectWise RMM MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every ConnectWise RMM 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 connectwise-rmm@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the ConnectWise RMM 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/connectwise-rmm/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/connectwise-rmm/install.ps1 | iex. Then authenticate per the README and runconnectwise-rmm-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/connectwise-rmm/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/connectwise-rmm/install.sh)
The installer drops both connectwise-rmm-cli (the CLI) and connectwise-rmm-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
connectwise-rmm-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/connectwise-rmm/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/connectwise-rmm/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 connectwise-rmm@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/connectwise-rmm --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/connectwise-rmm --force
Hermes speaks MCP natively, so it can also use the connectwise-rmm-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the connectwise-rmm skill from https://github.com/servosity/msp-skills/tree/main/skills/connectwise-rmm. The skill defines how its required CLI (
connectwise-rmm-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 client under Integrations > API Access in the ConnectWise portal, then set its ID and secret:
CONNECTWISE_RMM_CLIENT_ID=<value> CONNECTWISE_RMM_CLIENT_SECRET=<value> connectwise-rmm-cli doctor
A client ID starting 0e30, 0e31 or 0e32 picks North America, Europe or Australia for you; if yours starts differently, set CONNECTWISE_RMM_BASE_URL to your region's API host. If your key was not granted every scope this connector uses, run connectwise-rmm-cli scopes --agent and set the CONNECTWISE_RMM_OAUTH_SCOPE line it prints - ConnectWise rejects a whole token request that asks for one scope the key lacks. Then pull the fleet into the local mirror:
connectwise-rmm-cli sync --resources companies,sites,endpoints,tickets
doctor mints a token from your client ID and secret and verifies it against the API, so a wrong secret, a missing scope or a wrong host shows up as a failed Credentials line. It exits 0 even when a check fails, so scripts should add --fail-on error.
| Question your MSP keeps asking | Command |
|---|---|
| Which endpoints are offline or silent for more than a day, by client? | connectwise-rmm-cli fleet stale --older-than 24h --agent |
| Which clients are behind on patches, worst first? | connectwise-rmm-cli fleet patch-posture --min-compliance 90 --agent |
| Which machines need a reboot this patch week, and who is logged on? | connectwise-rmm-cli fleet reboot-due --agent |
| Which machine is this user logged on to? | connectwise-rmm-cli fleet whois "jsmith" --agent |
| Give me one client's health card for the review. | connectwise-rmm-cli fleet scorecard "Acme Corp" --agent |
| Why did last night's script fail, and on which machines? | connectwise-rmm-cli fleet task-failures " " --agent |
Run a script on endpoints - preview first, then schedule with --confirm. | connectwise-rmm-cli run --script "Restart Print Spooler" --endpoint " " |
| Which OAuth scopes did my API key actually get? | connectwise-rmm-cli scopes --agent |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most ConnectWise RMM integrations and MCP servers - the open-source connectwise-asio-mcp and asio-cli among them - work against the live API with no persistent local copy. That's fine for one device. It dies at scale, when you're asking "which agents are offline across all 40 clients" or "who's behind on patches before this morning's client review", because Asio returns per-endpoint rows keyed by IDs, never a per-client roll-up, and caps availability checks at 400 endpoints per call.
This skill syncs ConnectWise RMM into a local SQLite mirror with full-text search, batches the live availability checks, and caches patch summaries. Aggregate questions become one local join, and the AI sees the answer, not the raw data. Compound commands like fleet patch-posture, fleet scorecard, and fleet task-failures join companies, sites, endpoints, patch summaries, tickets and task results - work a stateless API wrapper can't do.
ConnectWise RMM (the cloud RMM on the ConnectWise Asio platform, formerly Command and Continuum) is built around a per-client, per-device view, and its partner API is the same shape: ConnectWise's own docume
Solo se muestra el principio; lee el resto en el repo