JumpCloud MCP integration for AI agents.
Connect AI agents to JumpCloud through 4 structured actions, including get system, get system user, and list system users. Review authentication, inputs, wor…
- 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 JumpCloud integration exposes
The JumpCloud Agent App exposes 4 provider-backed actions for security work. Its current contract lets an authorized agent get a jumpcloud system by id through the v1 systems api, get a jumpcloud system user by id through the v1 systemusers api, and list jumpcloud system users through the v1 systemusers api. 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 JumpCloud account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real JumpCloud capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_systemREADGet a JumpCloud system by ID through the v1 Systems API.
INPUTS: id / fields / filter / orgId / region
get_system_userREADGet a JumpCloud system user by ID through the v1 Systemusers API.
INPUTS: id / fields / filter / orgId / region
list_system_usersREADList JumpCloud system users through the v1 Systemusers API.
INPUTS: fields / filter / limit / orgId / region
list_systemsREADList JumpCloud systems through the v1 Systems API.
INPUTS: fields / filter / limit / orgId / region
INPUT CONTRACTS
Know what the action needs before it runs.
get_system
idREQUIRED- The JumpCloud object identifier.
fieldsOPTIONAL- Space-separated fields to include in the returned JumpCloud records.
filterOPTIONAL- JumpCloud v1 filter expression such as department:$eq:Finance.
orgIdOPTIONAL- Optional JumpCloud organization ID to send with the x-org-id header for multi-tenant admin accounts.
regionOPTIONAL- The JumpCloud data-center region to call.
get_system_user
idREQUIRED- The JumpCloud object identifier.
fieldsOPTIONAL- Space-separated fields to include in the returned JumpCloud records.
filterOPTIONAL- JumpCloud v1 filter expression such as department:$eq:Finance.
orgIdOPTIONAL- Optional JumpCloud organization ID to send with the x-org-id header for multi-tenant admin accounts.
regionOPTIONAL- The JumpCloud data-center region to call.
list_system_users
fieldsOPTIONAL- Space-separated fields to include in the returned JumpCloud records.
filterOPTIONAL- JumpCloud v1 filter expression such as department:$eq:Finance.
limitOPTIONAL- The number of records to return at once. JumpCloud limits this to 100.
orgIdOPTIONAL- Optional JumpCloud organization ID to send with the x-org-id header for multi-tenant admin accounts.
regionOPTIONAL- The JumpCloud data-center region to call.
list_systems
fieldsOPTIONAL- Space-separated fields to include in the returned JumpCloud records.
filterOPTIONAL- JumpCloud v1 filter expression such as department:$eq:Finance.
limitOPTIONAL- The number of records to return at once. JumpCloud limits this to 100.
orgIdOPTIONAL- Optional JumpCloud organization ID to send with the x-org-id header for multi-tenant admin accounts.
regionOPTIONAL- The JumpCloud data-center region to call.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get System
Get a JumpCloud system by ID through the v1 Systems API. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_systemVerify with Get System User
Get a JumpCloud system user by ID through the v1 Systemusers API. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_system_userSAFETY BOUNDARY
Operate JumpCloud with explicit limits
- Authorize JumpCloud with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned JumpCloud 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 JumpCloud rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the JumpCloud task completed successfully.
CONNECTION MODEL
API key
JumpCloud API key sent with the x-api-key header. In the JumpCloud Admin Console, open the username menu in the top-right corner and retrieve it from API Settings: https://console.jumpcloud.com/.
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 JumpCloud.