device_management
Iru (formerly Kandji)
Connect Iru (formerly Kandji) to Elaichi and hand every teammate a governed MCP endpoint — 11 tools ready to call from Claude, Cursor, or any MCP client, clamped by roles, restrictions, and an audit log.
AI tools
Iru (formerly Kandji) tools for your AI agents
11 tools are ready to mint as an 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.
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 — 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.
Mint
Mint a personal MCP endpoint on that toolbox and paste it into Claude, Cursor, or any MCP client — governed by roles, restrictions, and audit logs.
Give every teammate a governed MCP server
Start a 14-day Gold trial — connect a product, curate a toolbox, and paste an endpoint into Claude or Cursor in minutes.