JumpCloud for AI agents
JumpCloud is a cloud directory platform for identity, access, and device management across an organization. Security teams fold it into their existing checks rather than relying on it alone. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in JumpCloud.
Provision a new system
Register a new device system in the directory as part of onboarding a new laptop.
Review a role before removal
Review a role's permissions, read-only, before recommending it for deletion.
Delete a role with confirmation
Delete an access role only after an admin confirms no users still depend on it.
2 JumpCloud actions, graded by risk.
Every JumpCloud action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
0Look things up. Allowed by default.
- No read actions.
write
1Create and change things. Allow, or ask the user first.
- jumpcloud.create_systemCreate System
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- jumpcloud.delete_roleDelete Role
JumpCloud in three steps.
- 01Your users connect JumpCloudThey add their JumpCloud api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create System” can wait for the user, and “delete Role” can be denied outright.
- 03Any agent can actYour agent calls JumpCloud through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('jumpcloud', { read: 'allow', write: 'ask', // create_system destructive: 'deny', // delete_role }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How JumpCloud connects.
Users add their JumpCloud api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same JumpCloud connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use JumpCloud from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore security and identity apps.
JumpCloud and Arc0, answered.
Can I use JumpCloud with Claude, ChatGPT or Cursor?
Yes. Connect JumpCloud to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the JumpCloud actions you allow.
How do users connect JumpCloud?
Users add their JumpCloud api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which JumpCloud actions can my agent take?
2 in total: 0 read, 1 write and 1 destructive, such as “create System”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in JumpCloud?
Yes. Actions like “delete Role” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call JumpCloud too?
Yes. The same JumpCloud connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug JumpCloud into your agent.
Your users connect JumpCloud once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan