N-able N-central MCP connector
The N-able N-central connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- Connects with an API key
- Free 14-day trial
- No credit card
List devices at the Denver customer site.
Working in N-able N-central with Elaichi
-
List all N-able N-central service organizations
-
Get single N-able N-central service organization by ID
-
List all N-able N-central devices
How to connect N-able N-central to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
N-able N-central MCP connector for 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.
N-able N-central MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
N-able N-central MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
N-able N-central MCP connector for 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.
N-able N-central MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with N-able N-central through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in N-able N-central is logged.
-
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.”
What connecting N-able N-central gets you
6 screens from Elaichi, each doing one job for your N-able N-central account.
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, Cursor or Microsoft Copilot
The agent
Ask about devices, read the answer.
Plain questions return live N-able N-central devices, sites and service monitor status.
Copy the endpoint
AI apps
One endpoint serves Claude, ChatGPT, Cursor and Microsoft Copilot.
Connect N-able N-central over OAuth, no SDK and no shared API key.
Tool catalog
72 N-able N-central tools, zero custom code.
Devices, service organizations, customer sites and asset life cycle, listed and callable.
Toolboxes
Every team gets its own toolbox.
Scope N-able N-central tools per team, from NOC to asset management.
Shared connections
Teammates use the connection, never the credential.
See who connected each N-able N-central account and which teams share it.
Audit log
Answer who touched which device.
When, who, what happened, type and resource for every N-able N-central call.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
N-able N-central digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
N-able N-central
Queued
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 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%
Collections and dashboards
Device numbers arrive before anyone asks.
Four metrics, 14 days of new devices, per team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for N-able N-central
All three can connect N-able N-central to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over N-able N-central tools | Allow or restrict single N-able N-central tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per N-able N-central call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
N-able N-central tools for your AI agents
72 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.
Questions, answered
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, Microsoft Copilot, 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 restricting the creation of customers or edits to asset lifecycle records in N-able N-central. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client in one step.
Does the N-able N-central MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. N-able N-central is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for N-able N-central?
Yes. Both let Claude, ChatGPT or Cursor use N-able N-central. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every N-able N-central call.
How is Elaichi different from Composio for N-able N-central?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to N-able N-central: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put N-able N-central in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot