What is Rube MCP and how do I enable it?

Add https://rube.app/mcp as an MCP server in your client configuration; no API keys required. Then verify RUBE_SEARCH_TOOLS responds to confirm connectivity.

Why must I always search tools first?

Tool schemas change over time. Searching prevents hardcoding tool slugs and ensures you use the current required input fields and execution plans.

What should I include in memory when executing tools?

Include a memory object in RUBE_MULTI_EXECUTE_TOOL to maintain state across calls. If there is no memory data, pass an empty object {}.

desktime-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/desktime-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Desktime Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/desktime

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Desktime connection via RUBE_MANAGE_CONNECTIONS with toolkit desktime
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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit desktime
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: "Desktime 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 Desktime task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["desktime"]
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 Desktime-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `desktime`
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/desktime-automation/SKILL.mdView on GitHub

Overview

Automate Desktime operations through Composio's Desktime toolkit via Rube MCP. The skill emphasizes discovering current tool schemas, establishing an active Desktime connection, and executing tools in safe, memory-aware workflows. It helps teams stay up-to-date with changing tool schemas and avoids hardcoding slugs or arguments.

How This Skill Works

The workflow starts by verifying RUBE_SEARCH_TOOLS to fetch available Desktime tool slugs and input schemas, then checks the Desktime connection with RUBE_MANAGE_CONNECTIONS. Once ACTIVE, it executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug, proper arguments, and a memory payload, ensuring session continuity and schema compliance.

When to Use It

When you need to automate routine Desktime tasks through Composio's Desktime toolkit via Rube MCP
When setting up a new Desktime workflow and you must query current tool schemas before scripting
When validating an ACTIVE Desktime connection before running any tool
When performing multiple Desktime actions in one workflow using RUBE_MULTI_EXECUTE_TOOL
When discovering tools with RUBE_SEARCH_TOOLS to avoid hardcoding slugs and to handle pagination

Quick Start

Step 1: Ensure RUBE_SEARCH_TOOLS is reachable and returns Desktime tool slugs and schemas
Step 2: Connect to Desktime with RUBE_MANAGE_CONNECTIONS using toolkit 'desktime' and confirm ACTIVE
Step 3: Run a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a valid session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before attempting any tool execution to get current schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to running tools
Use exact field names and types from search results; avoid hardcoding slugs or arguments
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session IDs within a workflow and create new sessions only for new workflows

Example Use Cases

Discover available Desktime tool slugs and schemas with RUBE_SEARCH_TOOLS for Desktime operations
Establish a Desktime connection using RUBE_MANAGE_CONNECTIONS with toolkit: desktime
Execute a discovered tool via RUBE_MULTI_EXECUTE_TOOL with memory and the correct session_id
Perform bulk Desktime actions using RUBE_REMOTE_WORKBENCH and run_composio_tool()
Fetch full tool schemas using RUBE_GET_TOOL_SCHEMAS for tools that include schemaRef

Frequently Asked Questions

Add this skill to your agents