Device Management
N-able N-central MCP connector
The N-able N-central connector lets Claude, ChatGPT, Cursor, or the Elaichi Agent look up customers, sites, devices, service monitor status, and asset lifecycle records in N-able N-central, with each person signed in as themselves and every call logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
70 tools
How to connect
How to connect N-able N-central to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect N-able N-central once
-
Open Connections, choose Add connection, and pick N-able N-central.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a N-able N-central API key. One person generates a token in N-able N-central and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect N-able N-central to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect N-able N-central to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect N-able N-central to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect N-able N-central to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with N-able N-central through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Service desk
Check a device before calling back
Ask which service monitors are failing on a customer's server while the ticket is still open, so the technician calls back with the answer rather than a promise to look.
-
IT operations
Find every device at a site
List the devices under a customer site or organization unit and see their monitor status in one pass, instead of clicking through the N-able N-central tree.
-
Onboarding
Set up a new customer and their sites
Create the customer record and its sites in N-able N-central from the signed contract, so the first devices have somewhere to land on day one.
-
Asset management
Keep warranty and lifecycle dates current
Update a device's asset lifecycle record after a warranty renewal or a hardware swap, so the next refresh plan starts from accurate dates.
-
Account management
Pull a device inventory for a review
Gather the device assets for one customer ahead of a quarterly review and have a summary drafted in plain language.
-
Procurement
Spot devices coming up for replacement
Ask which devices across a customer's sites are nearing end of life according to their asset lifecycle records, and build the refresh list from that.
Try asking
- “List devices at the Denver customer site.”
- “Which devices have failing service monitor status?”
- “Show devices with asset life cycle expiring this quarter.”
AI tools
N-able N-central tools for your AI agents
70 tools are ready to call through Elaichi's MCP endpoint the moment you connect N-able N-central, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting N-able N-central gets you
6 screens from the product, each doing one job for your N-able N-central account.
The agent
Ask about devices, read the answer.
Plain questions return live N-able N-central devices, sites and service monitor status.
- devices
- customer sites
- service organizations
- device assets
Ask Elaichi to work across your apps.
List devices at the Denver customer site.
Which devices have failing service monitor status?
Show devices with asset life cycle expiring this quarter.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint serves Claude, ChatGPT and Cursor.
Connect N-able N-central over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
70 N-able N-central tools, zero custom code.
Devices, service organizations, customer sites and asset life cycle, listed and callable.
- List all N-able N-central service organizations
- Create a N-able N-central service organization
- Get single N-able N-central service organization by ID
- Create a N-able N-central authentication
ElaichiToolsToolboxes
Every team gets its own toolbox.
Scope N-able N-central tools per team, from NOC to asset management.
- NOC
- Service desk
- Asset management
- Onboarding
ElaichiToolboxesShared connections
Teammates use the connection, never the credential.
See who connected each N-able N-central account and which teams share it.
- NOC North America
- Service desk EMEA
- Asset management
- Field operations
ElaichiConnectionsAudit log
Answer who touched which device.
When, who, what happened, type and resource for every N-able N-central call.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, the digest ships.
Fetch devices, group by site, draft a digest, approve, post to N-able N-central.
N-able N-central digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch devices
N-able N-central
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
N-able N-central
Queued
Collections and dashboards
Device numbers arrive before anyone asks.
Four metrics, 14 days of new devices, per team breakdown, refreshed on schedule.
N-able N-central health
Refreshed 4 minutes ago · every 15 minutes · from the devices collection
Devices
1,284 ↓ 12%
Customer sites
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Devices created
Last 14 days
By team
Share of activity
NOC North America 34%
Service desk EMEA 27%
Asset management 21%
Field operations 18%
FAQ
Frequently asked questions
How do I connect N-able N-central to Claude?
Connect N-able N-central in Elaichi first: you paste an API key from your N-able N-central account, and there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on it can work with your N-able N-central customers, sites, and devices as you.
Does N-able N-central work with ChatGPT and Cursor as well as Claude?
Yes. Once N-able N-central is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect N-able N-central once and every client uses it.
What can an AI agent actually do with my N-able N-central data?
It can look up customers, sites, and organization units, list the devices under any of them, and check which service monitors on a device are healthy or failing. It can also read and update asset lifecycle records, pull device asset details for an inventory, and create new customers and sites in N-able N-central. Because N-able N-central has a large set of actions, short specific asks such as 'monitor status for the Acme file server' work better than long paragraphs.
Does connecting N-able N-central give the AI access to every customer and device?
No. The AI works inside the access of the person who signed in, so it sees only the N-able N-central customers, sites, and devices that person can already see. Elaichi can narrow that further, for example to read-only lookups, but it can never grant more than the person already has in N-able N-central.
Can I stop an agent from deleting or changing things in N-able N-central?
Yes. Restrictions in Elaichi apply per action, so you can allow looking up devices and monitor status while blocking the creation of customers or edits to asset lifecycle records in N-able N-central. A blocked action is never shown to the AI client at all, so no prompt, however worded, can reach it.
What happens to a N-able N-central connection when someone leaves?
Offboarding a person in Elaichi ends their access to N-able N-central through every AI client at once. If they shared a connection, it keeps working for everyone else on the team. Disconnecting N-able N-central once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client in one step.
Put N-able N-central in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.