Can my team share one N-able N-central connection?

Yes. One administrator connects N-able N-central in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every lookup or change.

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.

Connect on Elaichi How to connect

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.

72 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.

n-able n-central

All categories

N-able N-central

Ayla Networks

BlueTally

Jamf

Iru (formerly Kandji)

ManageEngine MDM

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.

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 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.

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.

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.

Connect N-able N-central on Elaichi See pricing

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.”

See all 72 N-able N-central tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for N-able N-central, by what to check
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	$15 per user per month.	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.

AI tools

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.

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 clients

Claude

ChatGPT

Cursor

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emily Carter	• Connected	4 minutes ago
Cursor	M Megan Brooks	• Connected	2 hours ago
ChatGPT	R Ryan Hayes	• Connected	Yesterday

Tool catalog

72 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

ElaichiTools

Tool	Action	Description
List all N-able N-central service organizations	List	List all service organizations in N-able N-central. Returns fields such as soId, soName, orgUnitType, contactFirstName, and contactLastName for each organization.
Create a N-able N-central service organization	Create	Create a new service organization in N-able N-central using required fields contactFirstName, contactLastName, and soName. Returns the soId of the created service organization in the response.
Get single N-able N-central service organization by ID	Get	Get a service organization in N-able N-central using id. Returns fields such as soId, soName, orgUnitType, parentId, contactFirstName, contactLastName, contactEmail, and address details. Endpoint is in preview stage.
Create a N-able N-central authentication	Create	Obtain access and refresh tokens in N-able N-central using a User-API Token (JWT). Returns access and refresh token objects with fields token, type, and expirySeconds in the response.
List all N-able N-central devices	List	List devices in N-able N-central for the logged-in user. Returns fields like deviceId, longName, deviceClass, osId, customerName, siteName, and lastApplianceCheckinTime for each device.

Toolboxes

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

ElaichiToolboxes

Name	Source template	Tools	Created
NOC toolbox N-able N-central · devices and service monitor status	N-able N-central starter	18	Mar 4, 2026
Service desk toolbox N-able N-central · device lookups and customer sites	—	9	Mar 2, 2026
Asset management toolbox N-able N-central · device assets and life cycle	—	24	Feb 27, 2026
Onboarding toolbox N-able N-central · service organizations and org units	N-able N-central starter	6	Feb 19, 2026
Field operations toolbox N-able N-central · appliance tasks and sites	—	31	Jan 30, 2026
Security toolbox N-able N-central · authentications and device access	—	12	Jan 22, 2026

Shared 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

ElaichiConnections

Connection	Scope	Status	Access
N- N-able N-central (NOC North America) Connected by Emily Carter	Personal	• Active	1 team · 6 members
N- N-able N-central (Service desk EMEA) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
N- N-able N-central (Asset management) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
N- N-able N-central (Field operations) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
N- N-able N-central (Managed customers) Connected by Ryan Hayes	Personal	• Active	Not shared
N- N-able N-central (Internal IT) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Audit 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 log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emily Carter emily.carter@northwind.io	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J Jake Morgan jake.morgan@northwind.io	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	M Megan Brooks megan.brooks@northwind.io	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	T Tyler Reed tyler.reed@northwind.io	N-able N-central Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes ryan.hayes@northwind.io	N-able N-central Devices Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker ashley.parker@northwind.io	N-able N-central Devices List	Toolbox

Launching 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 Emily Carter

Run now

✓

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 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

Live

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%

Related connectors

More from the catalog

Browse all 600+ connectors →

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.

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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Connect N-able N-central Talk to us

Works with: and any other MCP client, or the Elaichi Agent.
When the trial ends: Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.