Validates API credentials, returns the real device-enrollment steps with Connect key guidance, and permanently removes a custom role by ID.
2actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Lyro guides an IT admin through system enrollment in JumpCloud during onboarding support. New machines join the directory immediately without manual credential entry or ticket delays.
Each card is one request a support team gets, and the Jumpcloud actions Lyro runs to close it.
Lyro validates the API credentials and returns JumpCloud's agent-installation instructions with documentation links and Connect key guidance, so the person asking gets the real process rather than a wrong answer.
Once it is clear no administrator still holds the role, Lyro deletes it by ID. The call is idempotent, so re-running it against a role that is already gone returns success rather than an error.
The enrollment action performs a credential validation check on its own, so Lyro can confirm the connection is authorized and working before it attempts anything destructive like removing a role.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Jumpcloud actions it has and picks the ones a request needs.
Authorize the Jumpcloud account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Lyro maps it to the Jumpcloud actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeJumpcloud · Lyro
What can you do in Jumpcloud without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Lyro can do inside Jumpcloud.
No, and neither can anything else over the API. JumpCloud does not support creating systems through its REST API - devices are enrolled by installing the JumpCloud Agent on each one. The Create System action validates your credentials and returns the enrollment instructions, documentation links, and Connect key guidance instead.
All 2 actions your agent can call on Jumpcloud, straight from the live MCP connection.
Validates credentials and provides guidance for enrolling systems in JumpCloud.
Deletes a specific custom role from JumpCloud by its ID.
Same connection, same setup. Pick the next one your team already uses.
Checks whether a service is actually up, acknowledges and escalates open incidents, publishes status page updates, and maintains the on-call rota.
Looks up current Context7 MCP documentation and triggers updates without leaving the conversation.
GitHub Gist is a service for sharing code snippets and notes.
Lists branches, reads schemas and connection strings, provisions branches, databases, and compute endpoints, and reports project consumption.
Reports Sauce Labs status, pulls test job history, and confirms supported platforms, tunnel versions, and Appium end-of-life dates.
Reads back every configured check with its status and settings, and returns the current monitoring node list with IPv4 and IPv6 addresses.

Authorize the account and your agent has all 2 actions from the first conversation.
