JumpCloud (BYOK)

JumpCloud (BYOK) — connector documentation

• MCP endpoint: https://byok-jumpcloud.connectorbay.com/mcp
• REST API: POST https://byok-jumpcloud.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-jumpcloud.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own JumpCloud JumpCloud API key (US region, console.jumpcloud.com), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-jumpcloud.connectorbay.com/health · Tool schemas: https://byok-jumpcloud.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-jumpcloud · agent@connectorbay.com

What JumpCloud (BYOK) is for

JumpCloud (BYOK) lets an AI assistant read your own JumpCloud data through the JumpCloud API with a key you supply (JumpCloud API key (US region, console.jumpcloud.com)). Read-only: 11 tools (list_organizations, list_systems, get_system, list_users, list_commands, list_system_groups, list_user_groups, list_policies, list_alerts, list_directories, list_software_apps). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to console.jumpcloud.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by JumpCloud. JumpCloud and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which JumpCloud organization is my API key for?"
• "Which JumpCloud devices have not contacted the server recently?"
• "Show the details of JumpCloud device 5f3c0a1b2c3d4e5f6a7b8c9d"
• "Which JumpCloud users are suspended or locked?"
• "What commands are saved in JumpCloud?"
• "What device groups exist in JumpCloud?"

What it does

• list_organizations: List the JumpCloud organization the key belongs to with its id and display name.
• list_systems: List managed devices (systems) with name, hostname, OS, agent version, last contact, remote IP, serial number, disk encryption state and tags. Newest first with sort -created.
• get_system: Get one JumpCloud device by id: OS, agent version, last contact, IP, serial number, encryption and policy state.
• list_users: List JumpCloud users with username, name, email, department, job title, state, suspended and locked flags, MFA setup and creation date.
• list_commands: List saved JumpCloud commands with name, type, launch type, schedule and trigger (command bodies are not returned).
• list_system_groups: List JumpCloud device groups with name, description and whether membership is static or dynamic.
• list_user_groups: List JumpCloud user groups with name, description, membership method and pending membership suggestions.
• list_policies: List JumpCloud device policies with name and the policy template: display name, OS family, delivery type and state.
• list_alerts: List JumpCloud alerts with title, category, severity, status, source and first/last occurrence times.
• list_directories: List the directories connected to JumpCloud (Active Directory, Google Workspace, LDAP, Microsoft 365, Workday) with type and default domain.
• list_software_apps: List software applications configured for deployment in JumpCloud with name and creation and update times.

BYOK key

You bring your own JumpCloud JumpCloud API key (US region, console.jumpcloud.com) (https://console.jumpcloud.com/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to console.jumpcloud.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://docs.jumpcloud.com/api/1.0/index.html (the API this connector calls, with a BYOK key)

Live from the JumpCloud API (console.jumpcloud.com) with a BYOK key; documentation: https://docs.jumpcloud.com/api/1.0/index.html. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by JumpCloud. JumpCloud and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your JumpCloud account.

Built for: Worldwide. Languages: English.

JumpCloud (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What JumpCloud (BYOK) is. JumpCloud (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own JumpCloud data: Read your JumpCloud devices, users, user and device groups, policies, commands, directories, software apps and alerts with your own API key (US region). You bring your own JumpCloud JumpCloud API key (US region, console.jumpcloud.com); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one JumpCloud call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to console.jumpcloud.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If JumpCloud rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What JumpCloud receives. The request we make on your behalf, including the key and the arguments, under JumpCloud's own terms and privacy policy. JumpCloud acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer JumpCloud gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your JumpCloud data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. JumpCloud (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at JumpCloud at any time to end all access.

Children. JumpCloud (BYOK) is a general-audience service operated by the adult using the assistant, under JumpCloud's own age rules.

Changes. We will post changes here with a new effective date.

JumpCloud (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the JumpCloud (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. JumpCloud (BYOK) provides: Read your JumpCloud devices, users, user and device groups, policies, commands, directories, software apps and alerts with your own API key (US region). It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own JumpCloud credentials and only access data you are allowed to access. JumpCloud's terms apply to your use of JumpCloud; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by JumpCloud. JumpCloud and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data JumpCloud returns, lightly trimmed; it may be incomplete, delayed or changed by JumpCloud. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your JumpCloud account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent JumpCloud's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; JumpCloud may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your JumpCloud key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action JumpCloud takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-jumpcloud

JumpCloud (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-jumpcloud.connectorbay.com/mcp
• REST API: https://byok-jumpcloud.connectorbay.com/openapi.json
• Live status: https://byok-jumpcloud.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. JumpCloud (BYOK) never asks for them.