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.
-
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.
21 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.
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 Ninjaone 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 Ninjaone 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 Ninjaone 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 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.
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.”
AI tools
Ninjaone tools for your AI agents
21 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.
No tools match your search.
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 clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
21 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
ElaichiToolsToolboxes
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
ElaichiToolboxesShared 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
ElaichiConnectionsAudit 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 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 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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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
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%
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.
Put Ninjaone in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.