playbooks

home / skills / composiohq / awesome-claude-skills / jumpcloud-automation

jumpcloud-automation skill

/jumpcloud-automation

This skill automates Jumpcloud operations via Rube MCP, discovering tools first to ensure up-to-date schemas and reliable execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill jumpcloud-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.9 KB
---
name: jumpcloud-automation
description: "Automate Jumpcloud tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Jumpcloud Automation via Rube MCP

Automate Jumpcloud operations through Composio's Jumpcloud toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/jumpcloud](https://composio.dev/toolkits/jumpcloud)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Jumpcloud connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jumpcloud`
- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas

## Setup

**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jumpcloud`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Jumpcloud operations", known_fields: ""}]
session: {generate_id: true}
```

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

## Core Workflow Pattern

### Step 1: Discover Available Tools

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Jumpcloud task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["jumpcloud"]
session_id: "your_session_id"
```

### Step 3: Execute Tools

```
RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
```

## Known Pitfalls

- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS`
- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools
- **Schema compliance**: Use exact field names and types from the search results
- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`)
- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows
- **Pagination**: Check responses for pagination tokens and continue fetching until complete

## Quick Reference

| Operation | Approach |
|-----------|----------|
| Find tools | `RUBE_SEARCH_TOOLS` with Jumpcloud-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `jumpcloud` |
| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs |
| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` |
| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` |

---
*Powered by [Composio](https://composio.dev)*

Overview

This skill automates JumpCloud tasks through Composio's JumpCloud toolkit using the Rube MCP orchestration layer. It provides a reliable pattern for discovering current tool schemas, managing connections, and executing single or bulk operations. The skill enforces runtime checks to avoid schema drift and connection failures.

How this skill works

First, it queries RUBE_SEARCH_TOOLS to discover available tool slugs and exact input schemas for the requested JumpCloud use case. Next, it verifies or initiates an active JumpCloud connection via RUBE_MANAGE_CONNECTIONS. Finally, it runs operations with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH, always supplying session IDs and a memory object to ensure consistent execution and pagination handling.

When to use it

  • Automating user, device, or policy changes in JumpCloud at scale
  • Building reproducible workflows that must adapt to changing tool schemas
  • Running bulk operations or multi-step orchestration across JumpCloud APIs
  • Integrating JumpCloud tasks into broader automation pipelines via Rube MCP
  • When you need safe execution with connection and schema validation before running actions

Best practices

  • Always call RUBE_SEARCH_TOOLS first to get live tool slugs and exact input schemas
  • Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the jumpcloud toolkit before executing tools
  • Include an explicit memory object (even empty) in RUBE_MULTI_EXECUTE_TOOL calls
  • Reuse session IDs for related steps and generate new sessions for separate workflows
  • Respect pagination tokens in responses and iterate until all pages are retrieved
  • Avoid hardcoding tool slugs or argument shapes—derive them from search results

Example use cases

  • Provision or deprovision groups of users by discovering the user-management tool and executing it with schema-compliant arguments
  • Rotate device policies across an organization using bulk runs via RUBE_REMOTE_WORKBENCH and run_composio_tool()
  • Query device inventory with paginated responses and aggregate results while reusing a session ID
  • Automate MFA or SSO connection checks by verifying the JumpCloud toolkit connection status before running tests
  • Create a scheduled workflow that refreshes configuration by fetching current tool schemas at each run

FAQ

What must I do before executing any JumpCloud tool?

Always run RUBE_SEARCH_TOOLS to get the current tool schemas and confirm the jumpcloud connection is ACTIVE via RUBE_MANAGE_CONNECTIONS.

Can I hardcode tool slugs or input fields?

No. Tool schemas can change. Always use RUBE_SEARCH_TOOLS results to obtain tool slugs and exact field names and types.