jumpcloud-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/jumpcloud-automation --openclawJumpcloud Automation via Rube MCP
Automate Jumpcloud operations through Composio's Jumpcloud toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/jumpcloud
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Jumpcloud connection via
RUBE_MANAGE_CONNECTIONSwith toolkitjumpcloud - Always call
RUBE_SEARCH_TOOLSfirst 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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitjumpcloud - If connection is not ACTIVE, follow the returned auth link to complete setup
- 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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/jumpcloud-automation/SKILL.mdView on GitHub Overview
Automate Jumpcloud operations through Composio's Jumpcloud toolkit via Rube MCP. This skill orchestrates discovery, connection management, and execution of Jumpcloud tasks by querying current tool schemas first to avoid broken integrations. It emphasizes establishing an ACTIVE Jumpcloud connection and executing discovered tool slugs within a structured workflow.
How This Skill Works
The workflow starts by discovering available Jumpcloud tools using RUBE_SEARCH_TOOLS to fetch current input schemas. It then verifies or establishes an ACTIVE connection to Jumpcloud with RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL, ensuring proper memory is passed and a session_id is reused when appropriate.
When to Use It
- When you need to perform a Jumpcloud operation and must first discover current tool schemas with RUBE_SEARCH_TOOLS to avoid outdated slugs.
- When setting up or validating an ACTIVE Jumpcloud connection before running any workflows.
- When you want to execute a discovered tool slug with proper arguments and session management using RUBE_MULTI_EXECUTE_TOOL.
- When coordinating multiple Jumpcloud tasks in a single flow (e.g., create user, assign groups, and set attributes) with a shared session.
- When you must avoid hardcoding tool slugs and arguments by always checking schemas and following the known tool discovery process.
Quick Start
- Step 1: Get Rube MCP running and verify availability with RUBE_SEARCH_TOOLS.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'jumpcloud' and ensure the status is ACTIVE.
- Step 3: Discover tools using RUBE_SEARCH_TOOLS, then execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and slugs.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
- Use exact field names and types from the search results; avoid hardcoding.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty (memory: {}).
- Reuse session IDs within a workflow and create new ones only for new workflows; watch for pagination in responses.
Example Use Cases
- Discover Jumpcloud operations with RUBE_SEARCH_TOOLS and execute a single tool slug returned from the results using RUBE_MULTI_EXECUTE_TOOL.
- Establish and verify an ACTIVE Jumpcloud connection via RUBE_MANAGE_CONNECTIONS before running a workflow that provisions a user.
- Run a multi-step Jumpcloud workflow in one session (e.g., create user, assign to groups, and set attributes) by reusing session_id across RUBE_MULTI_EXECUTE_TOOL calls.
- Use RUBE_REMOTE_WORKBENCH to execute multiple Composio Jumpcloud tools in bulk for batch operations.
- Retrieve the full tool schemas with RUBE_GET_TOOL_SCHEMAS to confirm input fields before integrating into a custom workflow.
