← All integrations

JumpCloud MCP server

48 operations0 webhooks

Manage JumpCloud directory resources — system users, systems, groups, policies, commands and organizations — through the official API 1.0/2.0 with x-api-key auth.

Try JumpCloud with your agent

Connect JumpCloud, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in JumpCloud on my account, then run one read-only example and show me the result.

Runs once, when you ask

JumpCloud tools and triggers

Tools are what your agent can do in JumpCloud through Corsair's MCP server. Triggers are the JumpCloud events a routine can start from.

Users

  • CreateDestructive

    Create a JumpCloud system user; unless state is STAGED, JumpCloud emails the user a welcome or activation link

    users.create

  • DeleteDestructive

    Delete a JumpCloud system user

    users.delete

  • Enforce MfaDestructive

    Update a system user's MFA requirement; an unenrolled user is locked out of MFA-protected resources once any exclusion ends

    users.enforceMfa

  • Expire PasswordDestructive

    Expire a system user's password so they must reset it at next login

    users.expirePassword

  • GetRead-only

    Get a JumpCloud system user by ID

    users.get

  • ListRead-only

    List JumpCloud system users with limit/skip pagination

    users.list

  • List Ssh KeysRead-only

    List SSH keys of a system user

    users.listSshKeys

  • Reset MfaDestructive

    Reset a system user's MFA (TOTP key) and start a new enrollment period

    users.resetMfa

  • Set PasswordDestructive

    Force-set a system user's password, replacing the current one

    users.setPassword

  • Sync MfaWrite

    Sync system user MFA

    users.syncMfa

  • UnlockWrite

    Unlock a locked system user

    users.unlock

  • UpdateDestructive

    Update a JumpCloud system user; setting state to ACTIVATED on a staged user emails them an activation link

    users.update

Connect JumpCloud to Claude, ChatGPT or Cursor

  1. 1

    Connect JumpCloud in Corsair

    Add your JumpCloud API key once in Corsair. Corsair stores the credential encrypted and makes the JumpCloud API calls for your agent, so it never goes into a prompt or a config file. Connect JumpCloud

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs JumpCloud. On a ChatGPT personal plan, connect JumpCloud here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, JumpCloud's read and write operations run right away and its 12 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/jumpcloud, add the JumpCloud plugin, and connect with an API key. Then call methods like corsair.jumpcloud.api.applications.get() from your app. Corsair keeps each tenant isolated.

Yes. JumpCloud requires an API key from your JumpCloud account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit JumpCloud, GitHub, Notion, Stripe, and the rest. Trigger JumpCloud from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for manage JumpCloud directory resources — system users, systems, groups, policies, commands and organizations — through the official API 1.0/2.0 with x-api-key auth. Common builds include sync jobs, admin tooling, and agents that call JumpCloud APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per JumpCloud API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/jumpcloud in the open repo. When JumpCloud ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your JumpCloud data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store JumpCloud data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put JumpCloud on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 12 destructive JumpCloud operations. You can change a link's mode at hub.corsair.dev/me.