Context7
Up-to-date docs for AI agents
Descripción del creador (original en inglés)
N-central REST API with an offline org-tree mirror, cross-tenant search, and a JWT-expiry guardian.
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.
NCENTRAL_JWT, N_CENTRAL_BASE_URL, N_CENTRAL_NO_CONFIG_WRITELos 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.
N_CENTRAL_BASE_URL envN_CENTRAL_NO_CONFIG_WRITE 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: NCENTRAL_JWT
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.8) llegó al registro hace 14 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: Context7, Codebase Memory, Exa
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
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
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 N-able N-central
API. Not affiliated with, endorsed by, or sponsored by N-able, Inc.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every N-central REST endpoint, plus an offline SQLite mirror of your whole org tree, cross-tenant search, issue-triage rollups, and a JWT-expiry guardian no other N-central tool has. 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 put this
connector behind the
supergatewaybridge or any other stdio-to-HTTP bridge,
not even on localhost. The bridge adds no password, so anyone who can reach
its port can use the MCP tools with your credentials. Use the default stdio
transport. If you set up a bridge or 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 N-able N-central skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register n-central-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add n-central-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 n-central-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs n-central-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server. This connector speaks stdio only, and the bridge it would need 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.
.mcpbClaude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companionn-central-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 setN_CENTRAL_CLI_PATHto an existing binary). Details: #331.
Download N-able N-central MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every N-able N-central 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 n-central@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the N-able N-central 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/n-central/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/n-central/install.ps1 | iex. Then authenticate per the README and runn-central-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/n-central/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/n-central/install.sh)
The installer drops both n-central-cli (the CLI) and n-central-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
n-central-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/n-central/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/n-central/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 n-central@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/n-central --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/n-central --force
Hermes speaks MCP natively, so it can also use the n-central-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the n-central skill from https://github.com/servosity/msp-skills/tree/main/skills/n-central. The skill defines how its required CLI (
n-central-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 N-able N-central portal):
NCENTRAL_JWT=<value> n-central-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 |
|---|---|
| What's red right now, grouped by customer and ranked by severity? | n-central-cli triage --by customer |
| Where is EXCHANGE01 - server, service org, customer, site? | n-central-cli whereis EXCHANGE01 |
| Find anything named acme across every server we run | n-central-cli fanout "acme" |
| Which devices are missing the Backup Plan custom property? | n-central-cli props audit --required "Backup Plan" |
| Which devices have no maintenance window before the patch wave? | n-central-cli maint coverage --before 2026-06-15 |
| Is the JWT healthy, and when does the API user's password kill it? | n-central-cli guardian --password-set 2026-03-01 |
| Hardware and software inventory for one device | n-central-cli devices assets 987654321 |
| Every device, exported for the QBR or your documentation tool | n-central-cli export "devices" --format jsonl |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most N-able N-central 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 "where is this device across our three N-central servers" or "what's red right now across every customer" - org-tree pagination, per-endpoint concurrency caps (N-able documents 429s beyond 3-50 concurrent calls), and a JWT that silently dies on password rotation.
This skill syncs the org tree into a local SQLite mirror with full-text search. Compound commands like whereis (device name fragment to full server > service org > customer > site path), fanout (one query unioned across every server's mirror), and triage (active issues grouped by customer, device, or monitor and ranked by severity) join across the org tree - work a stateless API wrapper can't do. And guardian turns the silent JWT failure mode into a CI-wireable warning.
N-able's own REST API documentation admits the two traps every N-central integrator hits: per-endpoint concurrency caps (429 beyond 3-50 concurrent calls, per the official known-issues page) and error messages that arrive inside a 200 OK response. The community-maintained NC-API-Documentation project on GitHub documents the third: the API user's password expiry - 90 days by default - silently invalidates the JWT, and the integration just stops.
Meanwhile the daily questions stay manual: the morning NOC sweep is a per-customer console walk, "where is that machine" means knowing its customer and site already, and a multi-server MSP repeats all of it in each console.
n-central-cli triage --by customer - the NOC sweep as one command, ranked by severitySolo se muestra el principio; lee el resto en el repo