Device Management
ManageEngine MDM MCP connector
The ManageEngine MDM connector lets Claude, ChatGPT, Cursor, or any MCP client look up managed devices, check encryption and profiles, assign apps, and request locations, all inside each person's own ManageEngine MDM access with every action logged.
-
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.
157 tools
How to connect
How to connect ManageEngine MDM to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect ManageEngine MDM once
-
Open Connections, choose Add connection, and pick ManageEngine MDM.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own ManageEngine MDM app, then approve. ManageEngine MDM 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 ManageEngine MDM 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 ManageEngine MDM 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 ManageEngine MDM 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 ManageEngine MDM 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 ManageEngine MDM through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
IT
Pull up a device before you touch it
Ask for a laptop by name or serial and get its summary, installed apps, assigned profiles, and last check-in time in one answer, without clicking through ManageEngine MDM tabs.
-
Helpdesk
Push a profile while the caller waits
When someone cannot join the office Wi-Fi or set up mail, assign the right configuration profile to their device during the call and confirm it landed.
-
Security
Confirm a Mac is encrypted before sign-off
Check FileVault status, firmware password, and installed certificates on a device before it ships to a new hire or leaves the building.
-
Operations
Find a phone that did not come back
Request a fresh location for a missing tablet or handset and get it back with a street address, not just coordinates.
-
Compliance
List devices missing a required restriction
Walk the device list and pull each one's restriction settings to see which phones still allow camera use or app installs outside policy.
-
IT
Remove an app from a group of devices
Unassign a retired app from every device that still has it, refresh the app status, and check that nothing is left behind.
Try asking
- “Which devices are missing FileVault right now?”
- “Show the profiles installed on our finance laptops.”
- “List devices with certificates expiring in 30 days.”
AI tools
ManageEngine MDM tools for your AI agents
157 tools are ready to call through Elaichi's MCP endpoint the moment you connect ManageEngine MDM, 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 ManageEngine MDM gets you
6 screens from the product, each doing one job for your ManageEngine MDM account.
The agent
Ask about devices, get answers from records.
Plain language questions run against live ManageEngine MDM devices, profiles and locations.
- devices
- profiles
- certificates
- restrictions
Ask Elaichi to work across your apps.
Which devices are missing FileVault right now?
Show the profiles installed on our finance laptops.
List devices with certificates expiring in 30 days.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint serves Claude, ChatGPT and Cursor.
Connect ManageEngine MDM from any MCP client over OAuth, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
157 ManageEngine MDM tools ready to call.
Devices, certificates, restrictions, FileVault, firmware and profiles, with no custom code written.
- List all ManageEngine MDM devices
- Get single ManageEngine MDM device by ID
- Update a ManageEngine MDM device by ID
- ManageEngine MDM devices get summary
ElaichiToolsToolboxes
Every team gets its own MDM toolbox.
Curate one ManageEngine MDM toolbox per team and scope it to that team.
- IT Operations
- Security
- Service Desk
- Onboarding
ElaichiToolboxesShared connections
Teammates use MDM without seeing credentials.
Each ManageEngine MDM connection shows who connected it and which teams and members share it.
- IT EMEA
- Security
- Service Desk
- Retail Stores
ElaichiConnectionsAudit log
Every device call is on the record.
When, who, what happened, type and resource, appended for each ManageEngine MDM 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 and enrolment digests ship.
Fetch ManageEngine MDM devices, group them, draft a digest, approve, post back.
ManageEngine MDM digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch devices
ManageEngine MDM
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
ManageEngine MDM
Queued
Collections and dashboards
Device health arrives before anyone asks.
Four metrics, 14 days of new devices and a team breakdown, refreshed on schedule.
ManageEngine MDM health
Refreshed 4 minutes ago · every 15 minutes · from the devices collection
Devices
1,284 ↓ 12%
Profiles
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Devices created
Last 14 days
By team
Share of activity
IT EMEA 34%
Security 27%
Service Desk 21%
Retail Stores 18%
FAQ
Frequently asked questions
How do I connect ManageEngine MDM to Claude?
Connect ManageEngine MDM in Elaichi, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. ManageEngine MDM requires an OAuth application registered inside your own ManageEngine MDM console, so one administrator brings a client ID and secret into Elaichi once. After that, each person just signs in to ManageEngine MDM with their own account when Claude asks, and nobody else ever handles those credentials.
Does ManageEngine MDM work with ChatGPT and Cursor as well as Claude?
Yes. Once ManageEngine MDM 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 ManageEngine MDM once and every client your team uses picks it up.
What can an AI agent actually do with my ManageEngine MDM data?
With ManageEngine MDM connected, an agent can look up a managed device and report its summary, installed apps, assigned profiles, certificates, FileVault and firmware status, restrictions, and last check-in. It can assign or remove configuration profiles and apps, refresh app status, update device details, and request a current location with an address. ManageEngine MDM has a lot of capabilities, so short concrete asks, like "show restrictions on Priya's iPad", work better than long paragraphs.
Does connecting ManageEngine MDM give the AI access to every device and every action?
No. Every request runs as the person who signed in to ManageEngine MDM, so an agent can only see the devices and take the actions that person's ManageEngine MDM role already allows. Elaichi can narrow that further by team or by action, and it never grants anything the person could not do themselves in ManageEngine MDM.
Can I stop an agent from changing devices or removing apps in ManageEngine MDM?
Yes. Restrictions in Elaichi apply per action, so you can allow reading device summaries and locations while blocking profile changes, app removal, or device updates in ManageEngine MDM. A blocked action is never shown to Claude, ChatGPT, or any other client at all, so no prompt, however worded, can reach it.
What happens to a ManageEngine MDM connection when someone leaves?
Offboarding a person in Elaichi ends their access to ManageEngine MDM through every client at once. If they connected a shared ManageEngine MDM connection, it keeps working for everyone else on the team. Disconnecting ManageEngine MDM once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client in one step.
Put ManageEngine MDM in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.