Can my team share one Ninjaone connection?

Yes. One administrator connects Ninjaone in Elaichi and shares the connection with a team, and nobody else ever sees the client ID or secret. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who asked about which device or ticket.

Device Management

Ninjaone MCP connector

The Ninjaone connector brings devices, alerts, tickets, patch history, software inventory and organizations into Claude, ChatGPT and Cursor, so your team can ask about the fleet in plain language inside the access each person already has.

Connect on Elaichi How to connect

How it connects. Connects over OAuth. 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.

33 tools

How to connect

How to connect Ninjaone to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Ninjaone once

Open Connections, choose Add connection, and pick Ninjaone.
Optionally set Share with to give a team access, then press Connect.
Supply your own Ninjaone app, then approve. Ninjaone needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

ninjaone

All categories

Ninjaone

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.

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

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

Ninjaone 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 Ninjaone 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 Ninjaone on Elaichi See pricing

Use cases

What teams do with Ninjaone through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

IT

Find every device still missing a patch

Ask which laptops and servers have not picked up last month's updates and get the list straight from each device's patch history in Ninjaone, without opening every record by hand.
Help desk

Check a device before picking up the call

Pull up a user's device, its recent alerts, activity log and disk space in one question, so the technician already knows what is wrong when the conversation starts.
Security

Review open alerts across every organization

Ask for all alerts raised in the last day across the clients you manage in Ninjaone, grouped by organization, and decide what needs attention first.
Account management

Set up a new client organization

Create the organization record for a newly signed client in Ninjaone from a chat, then update its details as the onboarding call fills in the gaps.
Operations

Audit installed software across the fleet

Ask which devices are running an outdated browser or an unapproved tool and get the answer from Ninjaone's software inventory, ready to paste into the renewal or compliance report.
Service desk

See what is sitting on each ticket board

Ask how many tickets are waiting on each Ninjaone board and which ones have gone quiet, then read a single ticket in full without leaving the conversation.

Try asking

“Which devices have alerts open longer than three days?”
“Show tickets on the help desk board from this week.”
“List devices missing the latest software patch.”

See all 33 Ninjaone tools below

Compare

Elaichi vs Zapier MCP vs Composio for Ninjaone

All three can connect Ninjaone 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 Ninjaone, 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 Ninjaone tools	Allow or restrict single Ninjaone 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 Ninjaone 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

Ninjaone tools for your AI agents

33 tools are ready to call through Elaichi's MCP endpoint the moment you connect Ninjaone, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Ninjaone gets you

6 screens from the product, each doing one job for your Ninjaone account.

The agent

Ask about devices, get real answers.

Plain language questions answered from live NinjaOne devices, alerts and tickets.

devices
alerts
tickets
activities

Ask Elaichi to work across your apps.

Which devices have alerts open longer than three days?

Show tickets on the help desk board from this week.

List devices missing the latest software patch.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach NinjaOne.

One org MCP endpoint 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

33 NinjaOne tools ready without custom code.

Devices, alerts, tickets, software inventory and patch history, every method listed.

List all Ninjaone users
List all Ninjaone activities
List all Ninjaone alerts
List all Ninjaone devices

ElaichiTools

Tool	Action	Description
List all Ninjaone users	List	List users in Ninjaone. Returns user id, firstName, lastName, email, phone, enabled, administrator, userType, invitationStatus, organizationId, deviceIds, tags, custom fields, and roles if includeRoles is true.
List all Ninjaone activities	List	List activities in Ninjaone. Returns activity log with fields id, activityTime, deviceId, severity, priority, seriesUid, activityType, statusCode, status, activityResult, sourceConfigUid, sourceName, subject, userId, message, type, and data.
List all Ninjaone alerts	List	List active alerts in Ninjaone. Returns alert uid, deviceId, message, createTime, updateTime, sourceType, sourceConfigUid, sourceName, subject, userId, psaTicketId, ticketTemplateId, data, and detailed device information including id, organizationId, locationId, nodeClass, approvalStatus, offline status, displayName, systemName, dnsName, netbiosName, created, lastContact, lastUpdate, tags, maintenance status, and references.
List all Ninjaone devices	List	List devices in Ninjaone. Returns device id, organizationId, locationId, nodeClass, approvalStatus, offline status, displayName, systemName, dnsName, netbiosName, created, lastContact, lastUpdate, tags, maintenance status, and references including organization, location, rolePolicy, policy, role, backupUsage, and warranty.
Get single Ninjaone device by ID	Get	Get device details by id in Ninjaone. Returns id, parentDeviceId, organizationId, locationId, nodeClass, nodeRoleId, rolePolicyId, policyId, approvalStatus, offline, displayName, systemName, dnsName, netbiosName, created, lastContact, lastUpdate, userData, tags, fields, maintenance status, references, ipAddresses, macAddresses, publicIP, notes, and deviceType.

Toolboxes

Every team gets its own NinjaOne toolbox.

Curate one toolbox for the help desk, another for security and asset teams.

Help desk
IT operations
Security
Asset management

ElaichiToolboxes

Name	Source template	Tools	Created
Help desk toolbox Ninjaone · tickets and ticket boards	Ninjaone starter	18	Mar 4, 2026
IT operations toolbox Ninjaone · devices and alerts	—	9	Mar 2, 2026
Security toolbox Ninjaone · patch history and activity logs	—	24	Feb 27, 2026
Asset management toolbox Ninjaone · software inventory and devices	Ninjaone starter	6	Feb 19, 2026
Field support toolbox Ninjaone · single device lookups and updates	—	31	Jan 30, 2026
Compliance toolbox Ninjaone · users and activity logs	—	12	Jan 22, 2026

Shared connections

Teammates use NinjaOne without holding credentials.

See who connected each account and which teams and members it reaches.

IT Operations
Help Desk
Security
Field Support EMEA

ElaichiConnections

Connection	Scope	Status	Access
NI Ninjaone (IT Operations) Connected by Emily Carter	Personal	• Active	1 team · 6 members
NI Ninjaone (Help Desk) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
NI Ninjaone (Security) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
NI Ninjaone (Field Support EMEA) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
NI Ninjaone (Asset Management) Connected by Ryan Hayes	Personal	• Active	Not shared
NI Ninjaone (Compliance) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Audit log

Every NinjaOne call has a name on it.

When, who, what happened, type and resource, in an append only log.

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	Ninjaone Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes ryan.hayes@northwind.io	Ninjaone Devices Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker ashley.parker@northwind.io	Ninjaone 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 turns alerts into an approved digest.

Fetch NinjaOne alerts, group them, draft a digest, approve, post back as a ticket.

Ninjaone 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

Ninjaone

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

Ninjaone

Queued

Collections and dashboards

Device health arrives before anyone asks.

Four metrics, 14 days of tickets created and a team breakdown, refreshed on schedule.

Ninjaone health

Refreshed 4 minutes ago · every 15 minutes · from the devices collection

Live

Devices

1,284 ↓ 12%

Alerts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Devices created

Last 14 days

By team

Share of activity

IT Operations 34%

Help Desk 27%

Security 21%

Field Support EMEA 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect Ninjaone to Claude?

First connect Ninjaone in Elaichi. Ninjaone requires an API application registered inside your own Ninjaone account, so an administrator creates one there once and enters its client ID and secret into Elaichi, then signs in with their own Ninjaone login over OAuth. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Nobody else on the team has to handle that client ID or secret again.

Does Ninjaone work with ChatGPT and Cursor as well as Claude?

Yes. Once Ninjaone 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 Ninjaone once and every client sees it.

What can an AI agent actually do with my Ninjaone data?

With Ninjaone connected, an agent can look up devices, read their alerts, activity logs, disks, installed software and patch history, list open alerts and tickets across your ticket boards, and browse organizations, users and roles. It can also update a device's details, and create or update an organization. It cannot open or close tickets, and it cannot remove anything from Ninjaone.

Does connecting Ninjaone give the AI access to every organization and device?

No. Every request runs as the person who signed in to Ninjaone, so a technician who can only see two client organizations gets answers about those two and nothing more. Elaichi can narrow that further with restrictions, and it can never widen access beyond what Ninjaone itself grants that person.

Can I stop an agent from changing things in Ninjaone?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Ninjaone devices, alerts and tickets while blocking device updates or the creation of organizations. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.

What happens to a Ninjaone connection when someone leaves?

Offboarding a person in Elaichi ends their access to Ninjaone through every AI client at once, including any shared connection they were using. A connection they set up and shared keeps working for everyone else on the team. If you disconnect Ninjaone in Elaichi, it disappears from Claude, ChatGPT, Cursor and every other client in one step.

Does the Ninjaone MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Ninjaone 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 Ninjaone?

Yes. Both let Claude, ChatGPT or Cursor use Ninjaone. 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 Ninjaone call.

How is Elaichi different from Composio for Ninjaone?

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 Ninjaone: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Ninjaone in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

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