What is Rube MCP and why do I need it for Calendarhero automation?

Rube MCP is Composio's management plane that lets you discover tool schemas, manage connections, and execute tools for Calendarhero tasks without hardcoding slugs or schemas.

Do I need API keys to use this skill?

No. You only need to add the MCP endpoint (e.g., https://rube.app/mcp) as your MCP server; no API keys are required.

What if tool schemas change or I see a mismatch?

Always perform RUBE_SEARCH_TOOLS first to fetch current schemas, and ensure you use exactly the field names and types returned by the search results. Do not hardcode slugs or arguments.

calendarhero-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Calendarhero Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/calendarhero

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Calendarhero connection via RUBE_MANAGE_CONNECTIONS with toolkit calendarhero
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 calendarhero
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: "Calendarhero 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 Calendarhero task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["calendarhero"]
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 Calendarhero-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `calendarhero`
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/calendarhero-automation/SKILL.md

View on GitHub

Overview

This skill automates Calendarhero operations through Composio's Calendarhero toolkit via Rube MCP. It emphasizes discovering tool schemas first and ensuring an active Calendarhero connection before executing any workflows.

How This Skill Works

You first search for current tool schemas using RUBE_SEARCH_TOOLS, then verify an ACTIVE Calendarhero connection with RUBE_MANAGE_CONNECTIONS. Finally, execute discovered tools with RUBE_MULTI_EXECUTE_TOOL, always including the memory parameter and reusing a session ID for continuity.

When to Use It

When you need to automate a Calendarhero operation after discovering the latest tool schemas
When establishing or validating an active Calendarhero connection before workflows
When executing a discovered tool with the correct field names and types
When handling multi-step workflows that require a persistent session
When performing bulk or iterative operations and you must respect pagination and memory usage

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case = Calendarhero operations to discover tools
Step 2: RUBE_MANAGE_CONNECTIONS toolkits: ["calendarhero"] and confirm ACTIVE
Step 3: RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug and exact arguments

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool slugs and schemas
Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before execution
Use exact field names and types from the search results; avoid hardcoding
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow to maintain context

Example Use Cases

Discover a Calendarhero operation, connect, and run the tool with proper arguments
Validate ACTIVE connection status before triggering a calendar task automation
Execute a discovered Calendarhero tool with a complete, schema-compliant payload (including memory)
Handle paginated results from RUBE_SEARCH_TOOLS and continue fetching until complete
Reuse a single session ID across multiple Calendarhero-related steps in a workflow

Frequently Asked Questions

Add this skill to your agents