Device Management
Iru (formerly Kandji)
Connect Iru (formerly Kandji) once and hand every teammate a governed MCP endpoint with 11 tools ready to call from Claude, ChatGPT, Cursor, or any MCP client, inside the same permissions they already have, with every call checked and logged.
Automations & dashboards
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 ship on the Black plan.
Automations
Put Iru (formerly Kandji) work on a schedule.
A trigger starts a sequence of steps: call a Iru (formerly Kandji) tool, transform the result, branch, wait, and ask a person when it matters.
Iru (formerly Kandji) digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch devices
Iru (formerly Kandji)
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
Iru (formerly Kandji)
Queued
Collections and dashboards
Report on Iru (formerly Kandji) without asking.
Collections hold your own data, written by an automation and read by a dashboard that refreshes on a schedule.
Iru (formerly Kandji) health
Refreshed 4 minutes ago · every 15 minutes · from the devices collection
Devices
1,284 ↓ 12%
Users
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Devices created
Last 14 days
By workspace
Share of activity
Engineering 34%
Product 27%
Support 21%
Sales 18%
AI tools
Iru (formerly Kandji) tools for your AI agents
11 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.
list_all_kandji_devices
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_kandji_device_by_id
Get device details for a specified device in Kandji. Requires device id. Returns device information including hardware, software, and status fields.
update_a_kandji_device_by_id
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_kandji_device_by_id
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_kandji_device_apps
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.
list_all_kandji_device_library_items
Get all library items and their statuses for a specified device in Kandji. Returns fields including library item status indicating availability, installation state, and compatibility.
list_all_kandji_blueprints
Get a list of blueprints in Kandji. Returns blueprint records with details such as id and name.
get_single_kandji_blueprint_by_id
Get information about a specific blueprint in Kandji using id. Returns blueprint details including configuration and metadata.
list_all_kandji_users
List users in Kandji. Returns an array of users with key details such as id, email, name, active, archived, created_at, updated_at, department, job_title, device_count, and integration information.
get_single_kandji_user_by_id
Get details for a specific user in Kandji using id. Returns key fields including name, email, active status, department, job_title, device_count, and integration details such as id, name, and type.
delete_a_kandji_user_by_id
Delete a specific user in Kandji by id. Returns no content on success. If the user is still assigned to one or more devices, a 400 error with 'detail' explaining the assignment issue is returned.
No tools match your search.
How it works
From Iru (formerly Kandji) account to governed MCP endpoint
Connect
Link a Iru (formerly Kandji) account through Elaichi's hosted connect flow. Credentials are vaulted, so nobody, including the AI, ever sees them.
Compose
The connection becomes a toolbox instantly. Curate which Iru (formerly Kandji) tools are exposed, rename them, or freeze arguments.
Authorize
Point Claude, ChatGPT, Cursor, or any MCP client at the one Elaichi endpoint and sign in with OAuth, governed by roles, restrictions, and audit logs.
Put your agents to work in the tools you already use
Start a 14-day Gold trial. Connect a product, curate a toolbox, and paste a governed MCP endpoint into Claude, ChatGPT, or Cursor in minutes.