Skip to content

Device Management

Iru (formerly Kandji) MCP connector

The Iru (formerly Kandji) connector brings your Apple device fleet, installed apps, library items, blueprints and users into Claude, ChatGPT, Cursor and any MCP client, so your team can ask about and update devices while every call stays inside their own Iru access.

Connect on Elaichi How to connect

  • How it connects. Connects with an API key. 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.

How to connect

How to connect Iru (formerly Kandji) to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Iru (formerly Kandji) once

  1. Open Connections, choose Add connection, and pick Iru (formerly Kandji).

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste an Iru (formerly Kandji) API key. One person generates a token in Iru (formerly Kandji) and pastes it once. Everyone else works through Share with, and never sees it.

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

Add connection

Choose a connector.

iru (formerly kandji)
Iru (formerly Kandji)
Ayla Networks
BlueTally
Jamf
ManageEngine MDM
Microsoft Intune
2

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.

Iru (formerly Kandji) MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Iru (formerly Kandji) MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Iru (formerly Kandji) MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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 Iru (formerly Kandji) to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Iru (formerly Kandji) on Elaichi See pricing

Use cases

What teams do with Iru (formerly Kandji) through Elaichi

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

  • IT

    Find out who has which Mac

    Ask which devices are enrolled in Iru (formerly Kandji), who each one is assigned to, and when it last checked in, without opening the console or exporting a spreadsheet.

  • Help desk

    Check installed apps before replying to a ticket

    Pull up a colleague's device in Iru (formerly Kandji), see which apps are installed and which library items have reached it, and answer the ticket with facts instead of a guess.

  • Security

    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.

  • IT

    Understand what a blueprint actually sets

    Look at the blueprints in Iru (formerly Kandji), read what a specific one configures, and see which devices sit under it before changing a policy.

  • People

    Clean up when someone leaves

    Look up the departing person's user record and devices in Iru (formerly Kandji), update the device details, and remove the user record once hardware is returned.

  • Operations

    Keep the hardware inventory current

    Update asset tags and assigned users on Iru (formerly Kandji) devices as laptops move between people and offices, so the device list matches what is on desks.

Try asking

  • “List all Iru devices missing their assigned blueprint.”
  • “Which Iru devices have apps out of date?”
  • “Show Iru users with more than two devices.”

See all 17 Iru (formerly Kandji) tools below

Compare

Elaichi vs Zapier MCP vs Composio for Iru (formerly Kandji)

All three can connect Iru (formerly Kandji) 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 Iru (formerly Kandji), 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 Iru (formerly Kandji) tools Allow or restrict single Iru (formerly Kandji) 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 Iru (formerly Kandji) 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

Iru (formerly Kandji) tools for your AI agents

17 tools are ready to call through Elaichi's MCP endpoint the moment you connect Iru (formerly Kandji), governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Iru (formerly Kandji) gets you

6 screens from the product, each doing one job for your Iru (formerly Kandji) account.

The agent

Ask about devices, get answers from Iru.

Plain language questions return live devices, blueprints and users from Iru.

  • devices
  • blueprints
  • users
  • library items

Ask Elaichi to work across your apps.

List all Iru devices missing their assigned blueprint.

Which Iru devices have apps out of date?

Show Iru users with more than two devices.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Iru.

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

17 Iru tools, no custom code.

Devices, device apps, library items, blueprints and users are all covered.

  • List all Iru (formerly Kandji) devices
  • Get single Iru (formerly Kandji) device by ID
  • Update a Iru (formerly Kandji) device by ID
  • Delete a Iru (formerly Kandji) device by ID
ElaichiTools
Tool Action Description
List all Iru (formerly Kandji) devices List Get a list of devices in Kandji. Returns fields including device_id, device_name, model, platform, os_version, serial_number, user, and tags.
Get single Iru (formerly Kandji) device by ID Get Get device details for a specified device in Kandji. Requires device id. Returns device information including hardware, software, and status fields.
Update a Iru (formerly Kandji) device by ID Update Update device information in Kandji using id. Supports updating user assignment, asset_tag, blueprint_id, and tags. Use null to clear asset_tag or user, and empty list to clear tags. Returns updated device fields.
Delete a Iru (formerly Kandji) device by ID Delete Delete a specific device in Kandji using id. This removes the device record, unenrolls it from MDM, and automatically uninstalls the agent on next check-in for macOS and Windows devices. Returns no content.
List all Iru (formerly Kandji) device apps List Get a list of all installed apps for a specified device in Kandji. Requires device_id. The response includes app details, such as name and version.

Toolboxes

Every team gets its own Iru toolbox.

IT, Security and Helpdesk each work from a toolbox scoped to them.

  • IT Operations
  • Security
  • Helpdesk
  • People Ops
ElaichiToolboxes
Name Source template Tools Created

IT Operations toolbox

Iru (formerly Kandji) · devices and blueprints

 Iru (formerly Kandji) starter 18 Mar 4, 2026

Security toolbox

Iru (formerly Kandji) · library items and compliance

 — 9 Mar 2, 2026

Helpdesk toolbox

Iru (formerly Kandji) · device lookups by user

 — 24 Feb 27, 2026

People Ops toolbox

Iru (formerly Kandji) · users and onboarding

 Iru (formerly Kandji) starter 6 Feb 19, 2026

Asset Management toolbox

Iru (formerly Kandji) · device inventory and returns

 — 31 Jan 30, 2026

Engineering toolbox

Iru (formerly Kandji) · laptop apps and configuration

 — 12 Jan 22, 2026

Shared connections

Share the Iru connection, not the token.

Teammates manage devices and blueprints through a connection without seeing a credential.

  • IT EMEA
  • IT Americas
  • Security
  • Helpdesk
ElaichiConnections
Connection Scope Status Access
IR

Iru (formerly Kandji) (IT EMEA)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
IR

Iru (formerly Kandji) (IT Americas)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
IR

Iru (formerly Kandji) (Security)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
IR

Iru (formerly Kandji) (Helpdesk)

Connected by Tyler Reed

 Personal • Needs re-auth 1 team · 3 members
IR

Iru (formerly Kandji) (People Ops)

Connected by Ryan Hayes

 Personal • Active Not shared
IR

Iru (formerly Kandji) (Contractors)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Audit log

Every Iru call is written down.

When, who, what happened, type and resource for each device action.

  • 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

 Iru (formerly Kandji) Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

ryan.hayes@northwind.io

 Iru (formerly Kandji) Devices Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

ashley.parker@northwind.io

 Iru (formerly Kandji) 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 fires, Iru work gets done.

Devices are fetched, grouped, drafted into a digest, approved, then posted back.

Iru (formerly Kandji) digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch devices

    Iru (formerly Kandji)

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s

  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve

  6. Post the digest

    Iru (formerly Kandji)

    Queued

Collections and dashboards

Iru device health, computed on a schedule.

Four metrics, 14 days of devices enrolled, and a breakdown by team.

Iru (formerly Kandji) health

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

Live

Devices

1,284 ↓ 12%

Blueprints

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Devices created

Last 14 days

By team

Share of activity

IT EMEA 34%

IT Americas 27%

Security 21%

Helpdesk 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect Iru (formerly Kandji) to Claude?

Connect Iru (formerly Kandji) in Elaichi first, which asks you to paste an API key from your Iru settings. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi as yourself, and your Iru devices, users and blueprints are available from then on.

Does Iru (formerly Kandji) work with ChatGPT and Cursor as well as Claude?

Yes. Once Iru (formerly Kandji) 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 Iru once and every client you use picks it up.

What can an AI agent actually do with my Iru (formerly Kandji) data?

An agent connected to Iru (formerly Kandji) can list your enrolled devices, open a single device and report who it is assigned to and when it last checked in, and show which apps and library items are on it. It can read your blueprints, look up users, update device details such as asset tag or assigned user, and remove a device or user record when you ask it to. It cannot do anything in Iru that you could not do yourself.

Does connecting Iru (formerly Kandji) give the AI access to my whole device fleet?

No. Every call to Iru (formerly Kandji) runs inside the access of the person who signed in, so the AI sees the devices, users and blueprints that person's Iru permissions allow and nothing more. Elaichi can narrow that further by hiding actions like deleting devices, but it can never grant more than the person already has in Iru.

Can my team share one Iru (formerly Kandji) connection?

Yes. One administrator connects Iru (formerly Kandji) with the API key and shares the connection with a team in Elaichi, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who looked up a device or updated a user, not a shared account.

Can I stop an agent from deleting or changing things in Iru (formerly Kandji)?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Iru (formerly Kandji) devices, apps and blueprints while blocking updates and deletions of devices or users. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.

What happens to an Iru (formerly Kandji) connection when someone leaves?

When you offboard a person in Elaichi, their access to Iru (formerly Kandji) through every AI client ends at once. If they had shared an Iru connection with a team, it keeps working for everyone else. If you want Iru gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

Does the Iru (formerly Kandji) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Iru (formerly Kandji) 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 Iru (formerly Kandji)?

Yes. Both let Claude, ChatGPT or Cursor use Iru (formerly Kandji). 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 Iru (formerly Kandji) call.

How is Elaichi different from Composio for Iru (formerly Kandji)?

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

Put Iru (formerly Kandji) in front of your team

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

Connect Iru (formerly Kandji) 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.