# JumpCloud MCP connector The JumpCloud connector lets Claude, ChatGPT, Cursor and the Elaichi Agent list your JumpCloud system users and update their details, with each person signed in as themselves and every change recorded in an audit log. Source: https://elaichi.ai/connectors/jumpcloud/ ## Facts | | | | --- | --- | | Application | JumpCloud | | Category | SSO | | AI tools | 2 | | Authentication | Connects with an API key | | Bring your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once JumpCloud is connected - List every JumpCloud system user in the Finance department - Update Priya Shah's job title to Senior Analyst - Show me all suspended system users in JumpCloud ## Connect JumpCloud in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick JumpCloud. 2. Optionally set Share with, then press Connect. 3. Paste a JumpCloud API key. One person generates a token in JumpCloud and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which JumpCloud tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## JumpCloud MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## JumpCloud MCP connector for ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## JumpCloud MCP connector for Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect JumpCloud to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Every scope the client asks for starts ticked except "Delete data and remove access", which you tick yourself. Calling a JumpCloud tool needs "Run your connected tools". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with JumpCloud through Elaichi ### Find every suspended or inactive account IT. Ask for the JumpCloud system users who are suspended or have not been activated, and get the list back without opening the admin console. ### Catch a profile up after a role change People. When someone moves teams, update their JumpCloud title, department and manager in one ask instead of clicking through each field. ### Review who still has an active account Security. Pull the full list of JumpCloud system users before an access review and spot accounts that should have been closed. ### Fix a mistyped name or email Helpdesk. A ticket says a display name is wrong, so you ask the agent to correct that user in JumpCloud and reply to the ticket in the same minute. ### Pull a headcount by department Operations. List JumpCloud system users grouped by department or location when a manager asks how many people sit in each office. ### Count users before a license renewal Finance. JumpCloud bills per user, so list the active system users ahead of renewal and check the number against what you are being charged. ## Elaichi vs Zapier MCP vs Composio for JumpCloud All three can connect JumpCloud to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay. | What to check | Elaichi | Zapier MCP | Composio | | --- | --- | --- | --- | | Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. | | Control over JumpCloud tools | Allow or restrict single JumpCloud tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. | | Record of calls | One audit entry per JumpCloud call. | A History tab of tool calls. | A log of every tool call. | | Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. | | Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. | Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026. Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/). ## Frequently asked questions ### How do I connect JumpCloud to Claude? Connect JumpCloud in Elaichi by pasting a JumpCloud API key, which you copy from your JumpCloud admin profile. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. ### Does JumpCloud work with ChatGPT and Cursor as well as Claude? Yes. Once JumpCloud is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, the Elaichi Agent and any other MCP client. You connect JumpCloud once and every client picks it up. ### What can an AI agent actually do with my JumpCloud data? With JumpCloud connected, an agent can list your system users, filter them by things like department, location or account state, and update a user's details such as title, department or display name. Short concrete asks work best, for example "list suspended JumpCloud users" rather than a long paragraph. It cannot do anything in JumpCloud that this connector does not cover. ### Does connecting JumpCloud give the AI full admin rights? No. Everything the agent does in JumpCloud runs inside the access of the person who signed in, so it can only see and change what that person already could. Elaichi can narrow that access further with restrictions, and it never widens it. ### Can my team share one JumpCloud connection? Yes. One admin connects JumpCloud with an API key, shares the connection with a team, and nobody else ever handles the key. Each person still signs in to Elaichi as themselves, so the audit log names who listed or updated a JumpCloud user. ### Can I stop an agent from changing users in JumpCloud? Yes. Restrictions in Elaichi work per action, so you can allow listing JumpCloud system users while blocking updates. A restricted action is left out of the AI client's tool list entirely and cannot be called, whatever the prompt says. ### What happens to a JumpCloud connection when someone leaves? Offboarding that person in Elaichi ends their access to JumpCloud through every client at once. A shared JumpCloud connection keeps working for everyone else on the team. If you want it gone completely, disconnecting JumpCloud once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client. ### Does the JumpCloud MCP connector work with Gemini, Codex, Claude Code or other MCP clients? Yes. JumpCloud is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs. ### Is Elaichi an alternative to Zapier MCP for JumpCloud? Yes. Both let Claude, ChatGPT or Cursor use JumpCloud. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every JumpCloud call. ### How is Elaichi different from Composio for JumpCloud? Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to JumpCloud: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call. ## All 2 JumpCloud tools Every tool below is callable through https://api.elaichi.ai/mcp once JumpCloud is connected, subject to the toolbox it is in and the restrictions on the caller. - **Update a JumpCloud systemuser by ID** (Update). Update a system user in JumpCloud. Requires user id. Accepts only the fields email, firstname, lastname and displayname. Returns the updated user with fields including _id, email, firstname, lastname, displayname, organization and created. - **List all JumpCloud system users** (List). List the users bound to a system (device) in JumpCloud, directly or indirectly, by traversing the JumpCloud graph. Requires system_id. Returns one graph object per user with id, type, paths and compiledAttributes.