JumpCloud

listing.by

Manage JumpCloud users, devices, groups and other directory resources from your AI assistant.

state.auth.long (state.auth.title)Streamable HTTP

listing.connect

listing.explain.oauth

https://mcp.jumpcloud.com/v1

listing.note.oauth

listing.share.h

listing.share.p

mcp.tc/i/jumpcloud

listing.about

Connects an assistant to a JumpCloud organization through the JumpCloud API, so it can work with identity and device resources such as users, devices, groups and other directory objects. JumpCloud is a platform for identity, access and device management.

Runs as a hosted streamable HTTP endpoint at https://mcp.jumpcloud.com/v1. Users sign in with OAuth, and the requested scopes include openid, profile, email, api and organization. No local install is needed. The tool list is not published, so available actions depend on the signed-in account.

listing.can

  • Manage JumpCloud users and groups
  • Work with devices in your JumpCloud organization
  • Access directory resources through the JumpCloud API
  • Sign in with OAuth scoped to your organization

listing.tools

listing.notools.oauth

listing.prompts

  • List the users in my JumpCloud organization.

  • Which devices are in the Engineering group in JumpCloud?

  • Add a new user to the Sales group in JumpCloud.

  • Show the groups that a specific user belongs to.

listing.setup.h

listing.setup.oauth

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http jumpcloud https://mcp.jumpcloud.com/v1
  1. Start Claude Code, type /mcp, pick jumpcloud and choose Authenticate. A browser window opens for the JumpCloud sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Settings → Connectors and click Add custom connector.
  2. Name it JumpCloud and paste this URL:
https://mcp.jumpcloud.com/v1
  1. Click Add, then Connect, and sign in when JumpCloud asks.

Claude Desktop's JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://mcp.jumpcloud.com/v1 and click Add.
  2. Click Connect and sign in when JumpCloud asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, open Settings → Security and login and turn on Developer mode.
  2. Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
  3. Paste https://mcp.jumpcloud.com/v1 as the server URL and choose OAuth. ChatGPT sends you to JumpCloud to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "jumpcloud": {
      "url": "https://mcp.jumpcloud.com/v1"
    }
  }
}

Cursor shows Needs login next to the server. Click it to sign in.

VS Code

Or from a terminal:

code --add-mcp '{"name":"jumpcloud","type":"http","url":"https://mcp.jumpcloud.com/v1"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "jumpcloud": {
      "type": "http",
      "url": "https://mcp.jumpcloud.com/v1"
    }
  }
}

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "jumpcloud": {
      "serverUrl": "https://mcp.jumpcloud.com/v1"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add jumpcloud --url https://mcp.jumpcloud.com/v1
codex mcp login jumpcloud

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.jumpcloud]
url = "https://mcp.jumpcloud.com/v1"

Gemini CLI

gemini mcp add --transport http jumpcloud https://mcp.jumpcloud.com/v1

Then, inside Gemini CLI, run /mcp auth jumpcloud to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI's settings file.

{
  "mcpServers": {
    "jumpcloud": {
      "type": "http",
      "url": "https://mcp.jumpcloud.com/v1"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp.jumpcloud.com/v1.

listing.faq

Can I paste mcp.tc/i/jumpcloud into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mcp.jumpcloud.com/v1, so your client talks to JumpCloud directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does JumpCloud need an API key or a sign-in?

Yes, you need a JumpCloud account. The first time your client connects, it opens JumpCloud's sign-in page. The token goes straight to the server's own URL, never through mcp.tc.

Is JumpCloud a remote or a local server?

Remote. JumpCloud hosts it at https://mcp.jumpcloud.com/v1, and it speaks Streamable HTTP. There's nothing to install.

What can JumpCloud do?

You can manage JumpCloud users and groups, work with devices in your JumpCloud organization and access directory resources through the JumpCloud API.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc's robot read JumpCloud's own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![JumpCloud on mcp.tc](https://mcp.tc/i/jumpcloud/badge.svg)](https://mcp.tc/i/jumpcloud)
HTML
<a href="https://mcp.tc/i/jumpcloud"><img src="https://mcp.tc/i/jumpcloud/badge.svg" alt="JumpCloud on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/jumpcloud.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/jumpcloud" title="JumpCloud on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json

https://mcp.tc/i/jumpcloud.json

listing.em.fields

listing.disclaimer_checked