jumpcloud.com
JumpCloud provides a cloud directory and identity platform for managing users, devices, access, and related IT operations across organizations. It also offers audit and event visibility through Directory Insights and supports managed service provider multi-tenant workflows.
JumpCloud exposes three documented HTTP API surfaces on jumpcloud.com subdomains: the core JumpCloud REST APIs v1 and v2, plus the Directory Insights REST API; all require authentication, primarily via an admin API key, with limited system-context HTTP-signature auth also documented for subsets of the core APIs. I could not confirm a public GraphQL API, MCP connect endpoint, or first-party CLI endpoint on jumpcloud.com.
- JumpCloud API v1discovered
- Directory Insights API v1discovered
- JumpCloud API v2discovered
Sign in to the JumpCloud Admin Console, open the user menu in the top-right, then go to API Settings to copy your API key. You can rotate it there with Generate New API Key / reset actions if needed. The docs say this key is tied to the currently logged-in administrator account.
On an enrolled Linux system, read the local JumpCloud agent configuration at /opt/jc/jcagent.conf to obtain the system key used for System Context Authorization. The docs describe generating HTTP Signatures from that local key; JumpCloud links an example signing script. This is only available from eligible enrolled systems, not from the admin console.
conventions · 1/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✓https://jumpcloud.com/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing