Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
N-central REST API with an offline org-tree mirror, cross-tenant search, and a JWT-expiry guardian.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
NCENTRAL_JWT, N_CENTRAL_BASE_URL, N_CENTRAL_NO_CONFIG_WRITEValues 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.
N_CENTRAL_BASE_URL envN_CENTRAL_NO_CONFIG_WRITE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account servosity, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: NCENTRAL_JWT
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).
The GitHub repo last changed –, and the latest version (0.1.8) reached the registry 14 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Context7, Codebase Memory, Exa
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
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
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.
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.
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 severityOnly the beginning is shown; read the rest in the repo