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.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
2 tools
How to connect
How to connect JumpCloud to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect JumpCloud once
-
Open Connections, choose Add connection, and pick JumpCloud.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
Google Workspace
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
JumpCloud MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect JumpCloud to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with JumpCloud through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
IT
Find every suspended or inactive account
Ask for the JumpCloud system users who are suspended or have not been activated, and get the list back without opening the admin console.
-
People
Catch a profile up after a role change
When someone moves teams, update their JumpCloud title, department and manager in one ask instead of clicking through each field.
-
Security
Review who still has an active account
Pull the full list of JumpCloud system users before an access review and spot accounts that should have been closed.
-
Helpdesk
Fix a mistyped name or email
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.
-
Operations
Pull a headcount by department
List JumpCloud system users grouped by department or location when a manager asks how many people sit in each office.
-
Finance
Count users before a license renewal
JumpCloud bills per user, so list the active system users ahead of renewal and check the number against what you are being charged.
Try asking
- “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”
Compare
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
JumpCloud tools for your AI agents
2 tools are ready to call through Elaichi's MCP endpoint the moment you connect JumpCloud, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting JumpCloud gets you
6 screens from the product, each doing one job for your JumpCloud account.
The agent
Ask about JumpCloud users in plain language.
Three starter prompts, answers pulled from live JumpCloud system user records.
- system users
- user accounts
- directory users
- user attributes
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint, every client, no shared API key.
Claude, ChatGPT and Cursor reach JumpCloud through one governed org endpoint, no SDK.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
2 JumpCloud tools, ready without writing code.
List system users and update them by ID, with no connector code to build.
- Update a JumpCloud systemuser by ID
- List all JumpCloud system users
ElaichiToolsToolboxes
Every team gets its own JumpCloud toolbox.
IT, People and Security each work from a toolbox scoped to them.
- IT
- People
- Security
- Helpdesk
ElaichiToolboxesShared connections
Teammates use JumpCloud without seeing a credential.
One person connects the API key, then shares it with teams and members.
- IT Admins
- People Ops
- Security
- Helpdesk
ElaichiConnectionsAudit log
Every JumpCloud change is logged with a name.
When, who, what happened, type and resource, in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the work, a person approves.
Fetch JumpCloud system users, group them, draft a digest, approve it, post back.
JumpCloud digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch system users
JumpCloud
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
JumpCloud
Queued
Collections and dashboards
JumpCloud user numbers, computed, no model involved.
Four metrics, 14 days of users created, and a team breakdown, refreshed on schedule.
JumpCloud health
Refreshed 4 minutes ago · every 15 minutes · from the system users collection
System users
1,284 ↓ 12%
User accounts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
System users created
Last 14 days
By team
Share of activity
IT Admins 34%
People Ops 27%
Security 21%
Helpdesk 18%
Related connectors
More from the catalog
FAQ
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 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.
Put JumpCloud in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.