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.

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.

11 connectors

Browse all 600+ 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

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

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

  • 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

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

  • Run a stock count without a spreadsheet

    Create an audit in BlueTally, walk the storeroom, and update it as each asset is found, all from a chat.

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

Security

  • Spot phones still carrying an old app

    List the mobile device applications in Jamf, find the versions that should be gone, and update or remove the entries that no longer belong.

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

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

Help desk

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

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

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

  • Show devices offline for more than 24 hours.

    Ayla Networks

  • Which laptops are checked out to the sales team right now?

    BlueTally

  • List all Iru devices missing their assigned blueprint.

    Iru (formerly Kandji)

  • List all Jamf mobile devices enrolled this month.

    Jamf

  • Which devices are missing FileVault right now?

    ManageEngine MDM

  • List non compliant managed devices enrolled this month.

    Microsoft Intune

  • List devices at the Denver customer site.

    N-able N-central

  • Which devices have alerts open longer than three days?

    Ninjaone

The tools

What an agent can call in Device Management

Connectors
10+

in the Device Management catalog

Tools
970

callable the moment you connect

Hosted sign-in
1

connect with nothing to register

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

Read 38%
369 tools · list, get, search
Write 22%
210 tools · create, update, send
Delete 8%
82 tools · delete, remove, archive
Other 32%
309 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. API key and App credentials mean an admin pastes them once, with nothing to register.

Device Management connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
Microsoft Intune 199 Hosted
ManageEngine MDM 157 Your own app
Snipe-IT 145 API key
Verkada 135 API key
BlueTally 91 API key
N-able N-central 72 API key
Ayla Networks 68 API key
Jamf 39 App credentials
Ninjaone 33 Your own app
Iru (formerly Kandji) 17 API key
UniFi 14 API key

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 or any MCP client connects to that same address with OAuth, while the Elaichi Agent reaches the same tools inside the app. 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. 1 of the Device Management connectors uses Elaichi's hosted sign-in, with nothing to register. 8 connect with an API key or app credentials that an admin pastes once, with no app to register. 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 left out of the model's tool list and cannot be called. 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.

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.