Skip to content
JumpCloud logo

JumpCloud MCP server

Manage JumpCloud users, devices, groups and applications.

JumpCloud is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
16
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
October 2026

About the JumpCloud MCP server

Connect JumpCloud once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches JumpCloud and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

JumpCloud tools your AI can run

Once connected, your assistant can call any of these JumpCloud actions by asking in plain language.

  • Create Object

    Create a user, group or application. Devices join JumpCloud by installing the agent, so they cannot be created here.

    3 fields

  • Update Object

    Change fields on a user, device, group or application. Fields you leave empty keep their current value.

    4 fields

  • Delete Object

    Permanently delete a user, device, group or application.

    2 fields

  • Get Object by ID

    Get a user, device, group or application, with its main fields and the full JumpCloud record.

    2 fields

  • List Objects (Batch)

    List users, devices, groups or applications, one page at a time or all pages at once.

    5 fields

  • List Objects by ID (Batch)

    Get many users, devices, groups or applications at once from a list of IDs.

    6 fields

  • Search Objects (Batch)

    Find users, devices, groups or applications by text or by a field value.

    9 fields

  • Create Association

    Link two JumpCloud objects, such as adding a user to a group or giving a user group access to an application or device.

    4 fields

  • Delete Association

    Unlink two JumpCloud objects, such as removing a user from a group or revoking a user group's access to an application or device.

    4 fields

  • Search User by Employee ID

    Find the JumpCloud user with an exact employee ID, for example one sent by your HR system.

    1 field

  • Lock User

    Lock a user so they cannot sign in to JumpCloud, their devices or connected applications until unlocked.

    1 field

  • Unlock User

    Unlock a user who was locked by an admin or by too many failed sign-in attempts.

    1 field

  • Reset User MFA

    Clear the multi-factor authentication enrollment of a user so they set it up again, for example after losing their phone.

    3 fields

  • Update User on System

    Set a user's administrator (sudo) rights on a device, binding the user to the device first if you choose.

    5 fields

  • Run Trigger Command

    Run the JumpCloud commands launched by a trigger name, and optionally wait for their results.

    5 fields

  • Custom API Call

    Call any JumpCloud API endpoint with this connection. Use a path such as /systemusers for the v1 API or /v2/usergroups for the v2 API.

    10 fields

Triggers

JumpCloud events your agent can watch

These start a run the moment something happens in JumpCloud, so work gets picked up on its own.

  • New Object

    Triggers when a new user, device, group or application appears in JumpCloud.

    1 field

Give your assistant JumpCloud

Connect JumpCloud once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

JumpCloud MCP, answered.

No. That is the point of it. One Activepieces server exposes JumpCloud alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect JumpCloud in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 16 tools, including Create Object, Update Object, Delete Object, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.