Skip to content

Connectors / Device Management

Device Management MCP connectors for Claude, ChatGPT and Cursor

10+ Device Management connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.

Start 14-day free trial Browse the full catalog
https://api.elaichi.ai/mcp The same for every user.

  • Their own access. An agent never gets more than the person it acts for.

  • One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.

The connectors

Device Management connectors in the catalog

Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.

10 connectors

Browse all 400+ connectors →

In practice

What teams do with Device Management connectors

Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.

IT

  • Microsoft Intune

    Find every device a person is using

    Ask for all the laptops and phones enrolled under one employee and see their model, operating system, and last check-in without opening the admin center.

  • ManageEngine MDM

    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.

  • Snipe-IT

    Find an asset by tag or serial

    Type the asset tag or serial number from the sticker and get the full Snipe-IT record back, including model, status and notes, without opening the console.

Operations

  • Verkada

    Log a point-of-sale event against footage

    Create Helix events for register voids, deliveries, or door props so each one is stamped on the camera timeline, then search those events later by type or time window.

  • Ayla Networks

    Set schedules across a fleet at once

    Update schedules and schedule actions for many devices in one pass in Ayla Networks, rather than opening each device and editing it by hand.

  • Jamf

    Reconcile the hardware list before a refresh

    Compare what Jamf computer inventory says you own against what is on desks, then correct locations, models and owners in one pass.

Security

  • Ninjaone

    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.

  • Iru (formerly Kandji)

    Confirm required software reached every device

    Compare the apps and library items on each Iru (formerly Kandji) device against what should be there, and get a list of the machines that are missing something.

  • Microsoft Intune

    Lock and locate a lost laptop

    Remote lock a device the moment it is reported missing, request its location, and disable lost mode once it turns up on the right desk.

Help desk

  • Microsoft Intune

    Reset a locked-out passcode mid-call

    While the person is still on the phone, reset or recover the passcode on their managed device and confirm the change took.

  • Snipe-IT

    Log new hardware the day it arrives

    Read out the model, serial and purchase details from the box and a new hardware record appears in Snipe-IT before the device reaches anyone's desk.

  • Ninjaone

    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.

Once it is connected

Things to ask

Each of these is answered against the access the person asking already has, in the Device Management account you connected.

The tools

What an agent can call in Device Management

Connectors
10+

in the Device Management catalog

Tools
844

callable the moment you connect

Hosted sign-in
8

connect with nothing to register

Of those 844 tools, 7% delete something. Restricting an agent to reads is not a promise here, it is 310 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.

Read 37%
310 tools · list, get, search
Write 20%
171 tools · create, update, send
Delete 7%
63 tools · delete, remove, archive
Other 36%
300 tools · vendor-specific verbs

One endpoint

https://api.elaichi.ai/mcp

Every connector above answers here.

Every Device Management connector, by depth

Tool counts are what the connector exposes today; the split is what those tools do.

Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect.

Device Management connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
Microsoft Intune 198 Hosted
ManageEngine MDM 157 Your own app
Snipe-IT 145 Hosted
Verkada 135 Hosted
N-able N-central 70 Hosted
Ayla Networks 68 Hosted
Jamf 25 Hosted
Ninjaone 21 Your own app
UniFi 14 Hosted
Iru (formerly Kandji) 11 Hosted

FAQ

Frequently asked questions

How many Device Management connectors does Elaichi have?

10+ Device Management connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.

Can Claude, ChatGPT and Cursor all use Device Management connectors?

Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent all connect to that same address with OAuth. Connecting a Device Management account once makes it reachable from every one of them.

Do Device Management connectors work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Device Management connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.

Do Device Management connectors need me to bring my own OAuth app?

Most do not. 8 of the Device Management connectors use Elaichi's hosted sign-in, with nothing to register. The other 2 ask you to bring your own OAuth app: you register it once with the vendor and connect. Hosted sign-in for those is in progress, a vendor partnership at a time, and when one lands the only thing that changes is that the registration step goes away. Each connector's page says which it is before you start.

Can I stop an agent from writing to Device Management tools?

Yes. Tool restrictions apply at role and individual level, and a restricted tool is never advertised to the model, so it cannot be called or guessed at from the tool list. Read-only access to a Device Management connector is a matter of allowing the reads and leaving the writes out.

Whose access does an agent get on a shared Device Management connection?

The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential.

Nearby

Teams that connect Device Management usually connect these too

Put Device Management connectors in front of your team

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

Start free trial Talk to us
Works with
Claude ChatGPT Cursor 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.