JumpCloud connector for AI agents

Tools your IT agent reaches for on JumpCloud, scoped per user.

CALL ANY TOOL

98 tools for IT management in JumpCloud: users, user and device groups, devices, SSO applications, policies, commands, System Insights, and alerts, with suspend, lock, and MFA reset actions.

jumpcloud_activate_user

Activate user

Activate a staged JumpCloud user and send the activation email. Returns a confirmation string. Use activate_user for users in the STAGED state. Use update_user to move a suspended user back to ACTIVATED.

Parameters

Name

Type

Required

Description

string

Required

ObjectID of the user. Example: 5f3a1b2c4d5e6f7890123456. Example: 5f3a1b2c4d5e6f7890123456.

object

Optional

Email address the activation message is sent to. Defaults to the address on the user record. Example: jane.doe@example.com. Provide JSON.

jumpcloud_add_alert_note

Add alert note

jumpcloud_create_command

Create command

jumpcloud_delete_command

Delete command

jumpcloud_delete_system_group

Delete system group

jumpcloud_get_alert

Get alert

jumpcloud_get_application_template

Get application template

jumpcloud_get_ip_list

List get ip

jumpcloud_get_organization

Get organization

jumpcloud_get_policy_result

Get policy result

jumpcloud_get_role

Get role

jumpcloud_get_system_group

Get system group

jumpcloud_list_alerts

List alerts

jumpcloud_list_applications

List applications

jumpcloud_list_insights_apps

List insights apps

jumpcloud_list_insights_patches

List insights patches

jumpcloud_list_organizations

List organizations

jumpcloud_list_policy_results

List policy results

jumpcloud_list_radius_servers

List radius servers

jumpcloud_list_software_apps

List software apps

jumpcloud_list_system_group_memberships

List system group memberships

jumpcloud_list_system_users

List system users

jumpcloud_list_user_group_associations

List user group associations

jumpcloud_list_user_groups

List user groups

jumpcloud_manage_system_association

Manage system association

jumpcloud_manage_user_association

Manage user association

jumpcloud_reset_user_mfa

Reset user mfa

jumpcloud_search_systems

Search systems

jumpcloud_update_alert_status

Update alert status

jumpcloud_update_system_group

Update system group

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// JumpCloud tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["jumpcloud"], toolNames: [
    "jumpcloud_search_users",
    "jumpcloud_suspend_user",
    "jumpcloud_list_user_systems"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Suspend jordan@acme.com and list the devices they can access" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["jumpcloud"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Suspend jordan@acme.com and list the devices they can access" }],
  tools,
});

// Execute the tool call with the user's vaulted JumpCloud API key
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["jumpcloud"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Suspend jordan@acme.com and list the devices they can access" }],
  tools,
});

// Tool call runs with the user's vaulted JumpCloud API key
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["jumpcloud"] }, pageSize: 100,
});

const agent = new Agent({
  name: "it_agent",
  model: "gemini-2.5-pro",
  instruction: "JumpCloud tools scoped to this user",
  tools,
});

await agent.run("Suspend jordan@acme.com and list the devices they can access");

Try these prompts

Copy any prompt into your agent. Each maps directly to a JumpCloud tool. Click to copy, paste into your agent, done.

Users

Copy the prompt

Copied

Create a JumpCloud user for new hire Dana Kim and add her to the Engineering group.

Copy the prompt

Copied

Suspend the account for jordan@acme.com.

Copy the prompt

Copied

Reset MFA for sam@acme.com so they can re-enroll.

Devices

Copy the prompt

Copied

List devices that report disk encryption off.

Copy the prompt

Copied

Lock the laptop assigned to Alex Rivera.

Copy the prompt

Copied

Show the latest status of the Screen Lock policy on every device.

Access and alerts

Copy the prompt

Copied

Which SSO applications can maria@acme.com access?

Copy the prompt

Copied

List open alerts sorted by severity.

Copy the prompt

Copied

Acknowledge the failed logins alert and add a note.

SEE HOW AUTH WORKS

Each user connects their own JumpCloud API key once, and Scalekit sends it with every call. Keys stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

JumpCloud

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

JumpCloud

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

JumpCloud

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

JumpCloud

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other IT, security, and productivity connectors.

Engineering Teams

DevOps assistant agent

Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.

Engineering Teams

Slack triage

Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared JumpCloud API key looks fine in a demo. In production every user suspension and device lock looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

JumpCloud today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access JumpCloud as the user or through a shared key?

As the user. Each user connects their own JumpCloud API key once, and Scalekit sends it with every call. User changes and device commands the agent sends are attributed to that user in your audit trail, not a shared service account.

Where is the JumpCloud API key stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new API key. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in JumpCloud?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example the list and get tools without jumpcloud_delete_user, which permanently deletes a user, or jumpcloud_delete_system, which removes a device and uninstalls the agent from it. Scalekit also enforces scope checks before every API call.

What happens when a user revokes JumpCloud access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Which JumpCloud organizations can the agent reach?

The organizations the user's API key can access. jumpcloud_list_organizations returns them, and the user, device, group, and policy tools work within that scope.