Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Every NinjaOne report, plus a local store that answers fleet-wide questions no single API call can
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.
NINJAONE_BASE_URL, NINJAONE_CLIENT_ID, NINJAONE_CLIENT_SECRET, NINJAONE_OAUTH_SCOPE, NINJAONE_TOKEN_URL, NINJAONE_NO_CONFIG_WRITE, PRINTING_PRESS_CLIENT_PROFILE, NINJAONE_MCP_READ_ONLY, NINJAONE_NO_LOCAL_DATA, NINJAONE_MCP_UPLOAD_ROOT, NINJAONE_USER_AGENT, NINJAONE_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.
NINJAONE_BASE_URL envNINJAONE_TOKEN_URL envNINJAONE_NO_CONFIG_WRITE envNINJAONE_MCP_READ_ONLY envNINJAONE_NO_LOCAL_DATA envNINJAONE_MCP_UPLOAD_ROOT envNINJAONE_USER_AGENT 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: NINJAONE_CLIENT_ID, NINJAONE_CLIENT_SECRET, NINJAONE_OAUTH_SCOPE, PRINTING_PRESS_CLIENT_PROFILE, NINJAONE_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.22) llegó al registro anteayer.
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, Fomu MCP
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.
Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.
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 NinjaOne
API. Not affiliated with, endorsed by, or sponsored by NinjaOne, LLC.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Comparing backup vendors? One of our MSP partners told us, "My guys now spend a tenth of the time on backups." Fixing is included in every Servosity co-managed backup plan, and our engineers tell you what they did. See how co-managed backup works
Every NinjaOne report, plus a local store that answers fleet-wide questions no single API call can: patch compliance, backup gaps, AV blast-radius, health, drift. 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 NinjaOne skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register ninjaone-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add ninjaone-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 ninjaone-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs ninjaone-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. Setup steps: mcp-install.md.
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 companionninjaone-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 setNINJAONE_CLI_PATHto an existing binary). Details: #331.
Download NinjaOne MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every NinjaOne 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 ninjaone@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the NinjaOne 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/ninjaone/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/ninjaone/install.ps1 | iex. Then authenticate per the README and runninjaone-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/ninjaone/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/ninjaone/install.sh)
The installer drops both ninjaone-cli (the CLI) and ninjaone-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
ninjaone-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/ninjaone/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/ninjaone/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 ninjaone@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/ninjaone --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/ninjaone --force
Hermes speaks MCP natively, so it can also use the ninjaone-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the ninjaone skill from https://github.com/servosity/msp-skills/tree/main/skills/ninjaone. The skill defines how its required CLI (
ninjaone-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 NinjaOne portal):
NINJAONE_CLIENT_ID=<value> NINJAONE_CLIENT_SECRET=<value> NINJAONE_OAUTH_SCOPE=<value> ninjaone-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 organizations are below 95% patch compliance? | ninjaone-cli patch-compliance --min-pct 95 |
| Which endpoints across the fleet have no backup at all? | ninjaone-cli backup-coverage |
| Which devices is a given threat on, fleet-wide? | ninjaone-cli av-sweep --threat "Trojan.Generic" |
| Which devices have AV definitions older than a week? | ninjaone-cli av-sweep --definition-stale-days 7 |
| What is each organization's overall health score, and why? | ninjaone-cli fleet-health |
| Which devices have not checked in for two weeks? | ninjaone-cli stale-devices --days 14 |
| Which devices are running an end-of-life OS? | ninjaone-cli os-eol |
| Where is a software title sprawling across too many versions? | ninjaone-cli software-audit --min-versions 3 |
| Did patch compliance get better or worse since last week? | ninjaone-cli drift --metric patch |
| Search every synced device, org, and alert for a string? | ninjaone-cli search "disk full" |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most NinjaOne integrations and MCP servers proxy each question into a live API call. That's fine for one device. It dies at scale, when you're asking "which of my 40 client organizations are below 95% patched, and which endpoints across all of them have no backup" - a question the API only answers as per-device rows you have to fetch, cache, and total yourself.
This skill syncs NinjaOne 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 patch-compliance, backup-coverage, fleet-health, and drift join devices against the organization map, the patch and backup reports, and the previous snapshot - cross-fleet rollups a stateless API wrapper can't do.
NinjaOne is one of the most-loved RMMs for real-time, per-device work. The recurring owner complaint is the layer above one device: reporting and the cross-client rollup. Independent reviews note NinjaOne's built-in reports are "not consistently executive-ready" and that client-facing reporting often needs a third-party BI overlay - a gap still open in 2026 - alongside the lack of a single unified multi-tenant view (Flamingo, *NinjaOne Review* and *NinjaOne vs Intune*, 2026).
So the questions you ask every week aren't one click - they're a per-org report run N times and re-totaled by hand. This skill makes them one command:
| The weekly question | One command |
|---|---|
| Who's behind on patches? | ninjaone-cli patch-compliance --min-pct 95 |
| Who has no backup? | ninjaone-cli backup-coverage |
| How far did that threat spread? | ninjaone-cli av-sweep --threat "Trojan.Generic" |
|
Solo se muestra el principio; lee el resto en el repo