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

Rube MCP is the cross-tool platform used to discover current Timely tool schemas, manage connections, and execute tools in a standardized workflow. It ensures your automation stays aligned with the latest Timely capabilities.

Do I need API keys to use Timely automation via Rube MCP?

No API keys are required. You add the MCP endpoint (https://rube.app/mcp) and rely on the built-in authentication flow when needed to activate the Timely toolkit.

What should I include in the memory parameter and why is it required?

The memory parameter must be included in every RUBE_MULTI_EXECUTE_TOOL call, even if empty, to provide session-scoped state and support continuity across tool executions.

timely-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Timely Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/timely

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Timely operations through Composio's Timely toolkit via Rube MCP. It emphasizes discovering current tool schemas first and verifying an active connection before running workflows to adapt to schema changes and ensure reliable automation.

How This Skill Works

You first query RUBE_SEARCH_TOOLS to pull up-to-date Timely tool slugs and input schemas. Then you verify the connection with RUBE_MANAGE_CONNECTIONS (authenticating if necessary) and finally execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id for continuity.

When to Use It

When you need to automate recurring Timely operations while staying aligned to the latest tool schemas.
When onboarding a new Timely task and you want to discover available tools first.
When establishing or revalidating a Timely connection before execution.
When building a multi-tool Timely workflow that reuses a session.
When you need to fetch all available Timely tools and handle pagination.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds.
Step 2: Run RUBE_MANAGE_CONNECTIONS for the timely toolkit and authenticate if needed, then confirm ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, pick a tool_slug from the results, and execute via RUBE_MULTI_EXECUTE_TOOL with memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls (empty object allowed).
Reuse session IDs for related workflows and paginate through results if needed.

Example Use Cases

Automate weekly Timely time-entry updates by discovering the current tools and executing the corresponding tool slug.
Onboard a new Timely task by discovering available tools first and then running the appropriate tool with the provided arguments.
Connect Timely through Rube MCP and validate ACTIVE status before performing any actions.
Execute multiple Timely actions in one session by reusing a session_id and memory payload.
Fetch all Timely tool options with pagination handling to avoid missing tools.

Frequently Asked Questions

Add this skill to your agents