convez.ai
MCP ServerIntegração & APIsAvançado
theonlytruebigmac

N-able Skills Library para Claude Code

theonlytruebigmac/nable-skills

Skills MSP para gerenciar N-able/N-central com GraphQL e REST

Ver no GitHub
InicialPluginScore · de 0 a 100

Biblioteca de skills MSP para Claude Code integrando as APIs N-able e N-central. Oferece 44+ skills prontos para gerenciar vulnerabilidades, alertas, tickets e monitoramento em tempo real via GraphQL (N-able MCP) e REST (N-central MCP) de forma complementar.

Instalação

$npx convez-ai theonlytruebigmac/nable-skills

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Triage automático de alertas de segurança e vulnerabilidades
  • Gerenciamento de tickets PSA e manutenção de infraestrutura
  • Monitoramento e análise de métricas em tempo real
  • Consultas híbridas combinando dados de GraphQL e REST

Veredito

Solução robusta e bem arquitetada para MSPs que usam N-able/N-central. Requer setup de MCPs e compreensão das diferenças entre as duas APIs, mas compensa com cobertura completa e skills hybrid poderosos.

README

A tradução para o português deste README ainda está na fila.

N-able / N-central MSP Skill Library

MSP skill library for Claude Code, covering two N-able/N-central APIs:

  • N-able MCP (nable-mcp) — the official GraphQL preview endpoint (n-query based).
  • N-central MCP (N-central-mcp) — the classic N-central REST API.

The two are complementary: the GraphQL API is strong on vulnerabilities, per-patch detail, and metrics; the classic REST API is strong on live monitoring alerts, PSA/ticketing, custom properties, maintenance windows, warranty/lifecycle, RBAC, and deployment. A set of hybrid skills uses both at once.

📖 Which MCP should I use? · 📖 N-central MCP tool reference


Install

This repo is a Claude Code plugin marketplace. Install all skills with:

/plugin marketplace add theonlytruebigmac/nable-skills
/plugin install ncentral@nable-skills

Skills are then available namespaced as /ncentral:<skill-name> (e.g. /ncentral:alert-triage). Pull updates later with /plugin marketplace update nable-skills.

The skills call the N-able and/or N-central MCP servers — but this plugin ships skills only, so you connect an MCP yourself. See Connecting an MCP.

Repository layout

This repo is a marketplace (catalog) with one plugin per N-able product. Today that's ncentral; future products (e.g. N-sight, Cove) become sibling plugins under plugins/, each installable on its own.

nable-skills/                     ← marketplace (catalog)
├── .claude-plugin/marketplace.json
├── docs/                         ← shared reference
└── plugins/
    └── ncentral/                 ← the N-central product plugin
        ├── .claude-plugin/plugin.json
        └── skills/               ← all 44 N-central skills

Connecting an MCP

This plugin ships skills only — it does not bundle or configure any MCP server. The skills call tools on the N-able / N-central MCPs, so connect at least one of them yourself; the skills then use whatever's available. An unconnected MCP just means the skills that need it can't run — the rest still work (hybrid-* skills need both).

MCPWhat it isHow to set it up
nable-mcpN-able's official hosted GraphQL MCP (covers N-central + N-sight)Docs: developer.n-able.com/gql/docs/mcp. Generate a token at n-able.app/api-token-management.
N-central-mcpClassic N-central REST MCP — deeper REST coveragetheonlytruebigmac/n-central-mcp; point it at your N-central with a User-API JWT.

Where the config goes depends on the surface:

  • Claude Desktop → Chat / Cowork: ~/Library/Application Support/Claude/claude_desktop_config.json (mcpServers).
  • Claude Code: ~/.claude/mcp.json, or a project-level .mcp.json.

Minimal nable-mcp example (drop into the mcpServers block of either file):

{
  "mcpServers": {
    "nable-mcp": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.n-able.com/mcp", "--header", "Authorization: Bearer YOUR_NABLE_TOKEN"]
    }
  }
}

In Claude Code, run /mcp to check connection status.


MCP tools

N-able MCP (GraphQL)

ToolPurpose
introspectDiscover fields on any schema type
searchFind queryable fields by keyword
validateCheck a query before running — always first
executeRun a GraphQL query against your fleet
get_asset_inventoryPaginated list of managed devices
get_single_asset_details_and_metricsFull detail + CPU/memory for one device
list_script_tasks_for_assetScript execution history for a device
assign_tags_to_assetsBulk-tag devices (write)

Rule: never execute without passing validate first.

Confirmed GraphQL queries (used by current skills): assetSearch, asset(id), assetAggregations, patchInstallationSearch, patchInstallationAggregations, vulnerabilityDetectionSearch, vulnerabilityDetectionAggregations, organizationSearch, taskSearch, taskAggregations, tagSearch. The asset(id) node also exposes nested activitySearch and taskExecutionSearch (used by incident-summary).

N-central MCP (classic REST)

~80 tools spanning devices, live monitoring (list_active_issues, get_device_status), scheduled tasks, custom properties, maintenance windows, warranty/lifecycle, PSA/ticketing, users/roles/access, device notes, deployment, reports, and org provisioning. See the full catalog and call conventions in docs/ncentral-mcp-reference.md.


Org hierarchy

              N-able GraphQL                         N-central REST
Partner                                     Service Organization (soId)
  └── ServiceOrganization                     └── Customer (customerId)
        └── Customer                                └── Site (siteId)
              └── Site                                    └── Device (deviceId)
                    └── Asset

GraphQL assetSearch accepts inOrganizations: [id] at any level. N-central uses numeric orgUnitId/soId/customerId/siteId and string deviceId.

⚠ The two ID spaces are different. Never pass a GraphQL id to N-central or vice versa — join by customer name and device name/hostname. See Cross-MCP correlation.


Skills

N-able MCP — GraphQL skills

Engineer

SkillWhat it doesCadence
alert-triageDisconnected agents + patch errors + critical vulnsDaily / on-call
patch-statusPatch compliance by status across customer or fleetWeekly
patch-approval-queueAVAILABLE and APPROVED patches awaiting actionDaily / patch Tuesday
device-health-checkFull device snapshot with metricsBefore any touch
onboarding-checklistGap analysis vs. MSP baselineAfter agent deploy
incident-summaryTimeline from activity logs + task historyPost-incident
stale-device-auditDisconnected devices + license cleanupMonthly
automation-policy-reviewScript task failures and coverageMonthly
eol-os-reportEOL OS inventory with upgrade priorityQuarterly
network-discovery-reviewUnmanaged and disconnected device gapsMonthly
site-dispatch-briefPre-on-site briefing for field techsBefore every visit
tag-devicesAssign tags in bulk (write)On demand
snapshotSave point-in-time fleet state for trendsWeekly / before QBR

Executive / Sales

SkillWhat it doesCadence
qbr-briefFleet + patch + vuln summary for QBR1 week before QBR
health-scoreWeighted 0–100 environment health scoreMonthly
renewal-risk-reportCustomers with deteriorating signalsWeekly
upsell-opportunity-reportCoverage gaps mapped to service offeringsMonthly
executive-monthly-digestFull-fleet KPI memo for leadership1st of month
new-prospect-baselinePre-sales scoping assessmentBefore SOW
sla-compliance-reportPatch/vuln age vs. SLA thresholdsMonthly
fleet-growth-reportDevice count and composition by customerMonthly

N-central MCP — classic REST skills

Monitoring & ops

SkillWhat it doesCadence
active-issuesLive monitoring-alert triage (the real alerts)Daily / on-call
scheduled-tasksScheduled-task & job-status monitorDaily / weekly
maintenance-windowsReview/create/update patch windows (write)Monthly / onboarding

Asset & lifecycle

SkillWhat it doesCadence
warranty-lifecycleWarranty + hardware-refresh forecast & budgetQuarterly
custom-property-auditMSP metadata completeness + bulk fill (write)Monthly
device-notesRead/add/bulk device runbook notes (write)On demand
asset-inventoryHardware/software asset inventoryQuarterly

Admin & onboarding

SkillWhat it doesCadence
psa-ticketingPSA tickets + customer↔company mapping (write)On demand
deployment-kitTokens/installers/keys to deploy the agentOn onboarding
license-capacityLicense limits vs. usage / headroomMonthly
access-reviewUsers, roles, access groups auditQuarterly
org-hierarchySO→Customer→Site export + ID lookupOn demand
patch-comparisonN-central native patch comparison reportWeekly
fleet-exportFull spreadsheet-ready device exportOn demand
server-healthN-central server version/uptime/clock driftWeekly

Hybrid skills — both MCPs (hybrid-*)

SkillWhat it doesCadence
hybrid-device-360One device's complete picture across both APIsBefore any touch
hybrid-alert-triageN-central live alerts ranked by GraphQL CVE/patch riskDaily / on-call
hybrid-customer-360Full account rollup: ops + business signalsBefore QBR / escalation
hybrid-health-score-plushealth-score + monitoring, warranty, metadata, licenseMonthly
hybrid-onboarding-plusonboarding-checklist + N-central config completenessAfter onboarding
hybrid-incident-bridgeIncident timeline from both, then draft a PSA ticketPost-incident
hybrid-qbr-plusqbr-brief + hardware refresh + tickets + license1 week before QBR
hybrid-patch-reconciliationUnpatched devices × maintenance windows = root causeWeekly / patch Tuesday

Meta / authoring

SkillWhat it doesCadence
create-skillToken-minimal template, token-cost model, and review checklist for authoring a new skill in this libraryOn demand

Gaps & guidance

  • Live alerts live in N-central (list_active_issues), not GraphQL — use the active-issues / hybrid-alert-triage skills for real alert state.
  • CVE vulnerabilities, tags, and CPU/memory metrics live in GraphQL, not REST.
  • Month-over-month deltas: both APIs are current-state — use snapshot to build trends.
  • Ticket response times live in your PSA; N-central can create/read Custom PSA tickets and mappings via psa-ticketing.
  • Writes (tagging, maintenance windows, custom properties, notes, lifecycle, tickets, provisioning) always preview and confirm before executing.
Ver o original no GitHub

Bom para

Relacionados