Stale devices
Priya Sharma, IT manager at Acme Ltd, asked which Macs had not checked in for a week. Memtro listed them with assigned user, OS version and blueprint, and noted one already in Lost Mode.
Which Macs have not checked in this week, and who are they assigned to?
Kandji, now Iru, connects Memtro to your Apple device management. It reads devices with model, platform, OS version, last check-in, assigned user, asset tag, blueprint, agent and Lost Mode state and tags, device notes, directory users, the audit log, blueprints, threat detections and vulnerability detections by CVE. When asked, and once an administrator has granted the action by name, it can lock, erase, restart or shut down a device, toggle Lost Mode, clear a passcode, release a locked Mac account, refresh inventory, rename, note or retag a device, move its blueprint, or delete its record. Serial numbers are not returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Kandji tool, reads what it needs, and answers with the source cited.
These tools change something in Kandji. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Kandji is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which Macs have not checked in this week?
Which devices are still on an old macOS version?
Which critical vulnerabilities are open across the fleet?
Who changed the engineering blueprint last week?
Lock Tom's MacBook and show our support number
Priya Sharma, IT manager at Acme Ltd, asked which Macs had not checked in for a week. Memtro listed them with assigned user, OS version and blueprint, and noted one already in Lost Mode.
Dan Fletcher, IT administrator at Northwind, asked Memtro to lock a laptop reported lost on a train and show the help desk number. Memtro sent the lock command through Kandji. The PIN that releases the lock stayed in the Kandji console and was never shown in Memtro.
The teams that lean on Kandji most, a question each of them asks, and what they connect beside it.
A record in Kandji is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Kandji, open Settings → Access → API tokens → Add Token, name it Memtro and create it. Copy the token, as it is shown once.
Configure permissions: grant the device read permissions and only the device actions you want Memtro to take. Do not grant the device secrets permissions.
In Memtro, open Connections → Kandji and paste Subdomain (the first part of the API URL shown on that page), Region (us or eu) and API token.
Ask your first question: which Macs have not checked in this week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Kandji tools are the same everywhere.
Only when you ask, and only what it has been granted: lock a device (the unlock PIN stays in the Kandji console); erase a device (all data lost, permanent); restart a device; shut down a device; turn on Lost Mode on an iPhone or iPad; turn off Lost Mode; clear an iPhone or iPad passcode; unlock a Mac's locked local account; delete a device record (it stops being managed); ask a device to check in and refresh its inventory; rename a device; add a note to a device; change a device's asset tag, assigned user or tags; move a device to another blueprint (changes its apps and settings). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Subdomain, region and API token. In Kandji, open Settings → Access → API tokens → Add Token, name it Memtro and create it. Copy the token, as it is shown once.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time