| name | jump-cloud |
| description | JumpCloud is a cloud directory and identity management platform that provides single sign-on, device management, and access control APIs, allowing IT teams to manage users, endpoints, and authentication policies across applications, networks, and operating systems from a unified service. Read and write JumpCloud data through One: systemusers, applications, systems, commands, usergroups, applemdmdevices and more, 703 actions with real parameter documentation. Use whenever the user asks to look something up in JumpCloud, create or update a record there, or build code against the JumpCloud API. |
JumpCloud through One
JumpCloud is a cloud directory and identity management platform that provides single sign-on, device management, and access control APIs, allowing IT teams to manage users, endpoints, and authentication policies across applications, networks, and operating systems from a unified service.
One exposes JumpCloud through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.
How to run an action
- Find the action in the table below, or call
search_one_platform_actions with platform jump-cloud if it is not listed.
- Call
get_one_action_knowledge with the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters.
- Call
execute_one_action with parameters copied from that knowledge.
Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.
Before you start
Call list_one_integrations once and confirm JumpCloud is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.
