Checking on leavers
Maya Okafor, IT manager at Acme Ltd, asked which leavers still had active JumpCloud accounts. Memtro filtered users by state and named two people in Sales still ACTIVATED, with their department and when each account was created.
Who in JumpCloud is suspended, and who failed to sign in today?
JumpCloud holds your company directory and managed devices. Memtro reads users with name, email, state and department, user groups, managed devices with operating system and last agent check-in, and Directory Insights events: sign-ins and admin changes, with whether each succeeded. When asked, and once an administrator has granted the action by name, it can create, activate, suspend or permanently delete users, restore a locked-out user, change their details, manage group membership, which grants or removes access, and lock, restart, shut down or erase a Linux or Windows device, where an erase destroys everything on it. Password state is never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right JumpCloud tool, reads what it needs, and answers with the source cited.
These tools change something in JumpCloud. 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 JumpCloud 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 JumpCloud users are suspended?
Who failed to sign in to Slack today?
Which Macs have not checked in to JumpCloud this week?
What admin changes were made in JumpCloud in the last 24 hours?
Suspend Ben Carter's account, he left today
Maya Okafor, IT manager at Acme Ltd, asked which leavers still had active JumpCloud accounts. Memtro filtered users by state and named two people in Sales still ACTIVATED, with their department and when each account was created.
Dan Fletcher, security lead at Northwind, asked Memtro to suspend the account of a salesperson who had left that afternoon. Memtro confirmed the user with him, then suspended them in JumpCloud, so they lost sign-in to every app and device it manages. The account and its data were kept.
The teams that lean on JumpCloud most, a question each of them asks, and what they connect beside it.
A record in JumpCloud 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 the JumpCloud Admin Console, create a dedicated administrator for Memtro with the narrowest role your plan offers: read-only for reading, Help Desk or Manager for the user and device actions.
Signed in as that administrator, open your name (top right) → API Settings and copy the key. Generating a new one breaks the old.
In Memtro, open Connections → JumpCloud, paste the key as API key, and set Region to us, eu or in to match your console.
Ask: which JumpCloud users are suspended?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The JumpCloud tools are the same everywhere.
Only when you ask, and only what it has been granted: create a JumpCloud user, staged with no access; update a JumpCloud user's name, e-mail, department or job title; activate a staged or suspended JumpCloud user (grants access); suspend a JumpCloud user (removes access); unlock a locked-out JumpCloud user; delete a JumpCloud user (permanent); create a JumpCloud user group; add a user to a JumpCloud user group (grants the group's access); remove a user from a JumpCloud user group; lock a Linux or Windows device in JumpCloud; restart a Linux or Windows device in JumpCloud; shut down a Linux or Windows device in JumpCloud; erase a Linux or Windows device in JumpCloud (permanent). 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.
API key and optional region. In the JumpCloud Admin Console, create a dedicated administrator for Memtro with the narrowest role your plan offers: read-only for reading, Help Desk or Manager for the user and device actions.
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