Iru (Kandji) MCP integration for AI agents.
Connect AI agents to Iru (Kandji) through 4 structured actions, including get blueprint, get user, and list blueprints. Review authentication, inputs, workfl…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Iru (Kandji) integration exposes
The Iru (Kandji) Agent App exposes 4 provider-backed actions for productivity and security work. Its current contract lets an authorized agent get a kandji blueprint by id, get a kandji directory user by id, and list kandji blueprints with optional id, name, and pagination filters. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Iru (Kandji) account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Iru (Kandji) capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_blueprintREADGet a Kandji blueprint by ID.
INPUTS: blueprintId
get_userREADGet a Kandji directory user by ID.
INPUTS: userId
list_blueprintsREADList Kandji blueprints with optional ID, name, and pagination filters.
INPUTS: id / idIn / name / limit / offset
list_usersREADList Kandji directory users with optional filters and cursor pagination.
INPUTS: email / id / integrationId / archived / cursor
INPUT CONTRACTS
Know what the action needs before it runs.
get_blueprint
blueprintIdOPTIONAL- The unique identifier of the Kandji blueprint to retrieve.
get_user
userIdOPTIONAL- The unique identifier of the Kandji directory user to retrieve.
list_blueprints
idOPTIONAL- A Kandji UUID value.
idInOPTIONAL- Blueprint IDs used to filter results.
nameOPTIONAL- The blueprint name used to filter results.
limitOPTIONAL- The maximum number of blueprint records to return.
offsetOPTIONAL- The zero-based offset used for Kandji blueprint pagination.
list_users
emailOPTIONAL- Return users with email addresses containing this value.
idOPTIONAL- A Kandji UUID value.
integrationIdOPTIONAL- A Kandji UUID value.
archivedOPTIONAL- Whether to return archived or non-archived users.
cursorOPTIONAL- The opaque pagination cursor returned by a previous Kandji response.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Blueprint
Get a Kandji blueprint by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_blueprintVerify with Get User
Get a Kandji directory user by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_userSAFETY BOUNDARY
Operate Iru (Kandji) with explicit limits
- Authorize Iru (Kandji) with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Iru (Kandji) data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Iru (Kandji) rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Iru (Kandji) task completed successfully.
CONNECTION MODEL
API key
Kandji tenant-level API token sent as a Bearer token. Create it from Settings > Access in the Kandji web app: https://support.kandji.io/api.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Iru (Kandji).