What is Leverly Automation via Rube MCP?

A workflow pattern to automate Leverly operations using Rube MCP's tool discovery and execution APIs.

What prerequisites are required?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available, a Leverly connection active with toolkit levery, and you should always search tools first before running workflows.

Why should I always search for tools first?

Tool schemas can change; never hardcode tool slugs or arguments. Calling RUBE_SEARCH_TOOLS returns current slugs, schemas, and known pitfalls to guide execution.

leverly-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Leverly Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/leverly

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Leverly operations through Composio's Leverly toolkit via Rube MCP. Always search for current tool schemas before running workflows to ensure up-to-date slugs and arguments.

How This Skill Works

Connect Rube MCP to Leverly and discover tools with RUBE_SEARCH_TOOLS. Check the Leverly connection with RUBE_MANAGE_CONNECTIONS and then execute discovered tools via RUBE_MULTI_EXECUTE_TOOL, including the memory field and a session_id. Always fetch current schemas before execution to avoid hardcoded slugs.

When to Use It

Automate repetitive Leverly workflows to save time and reduce errors.
Set up new Leverly tasks by discovering current tool schemas instead of hardcoding slugs.
Validate that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Run batch Leverly operations via RUBE_MULTI_EXECUTE_TOOL with a stored session.
Debug Leverly automation by reusing session IDs and checking for pagination in tool discovery.

Quick Start

Step 1: Run RUBE_SEARCH_TOOLS with use_case: "Leverly operations" to discover available tools.
Step 2: Run RUBE_MANAGE_CONNECTIONS for toolkit "leverly" and confirm ACTIVE.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory (even if empty) and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow; generate new ones for new workflows.
Watch for pagination; continue fetching until complete.

Example Use Cases

Automate a Leverly data pull by discovering the required tool, confirming an ACTIVE connection, and running with a memory payload.
Set up a new Leverly integration by connecting via RUBE_MANAGE_CONNECTIONS, then run an initial discovery and execute a tool.
Batch multiple Leverly tasks using RUBE_MULTI_EXECUTE_TOOL and RUBE_REMOTE_WORKBENCH run_composio_tool.
Maintain up-to-date schemas by re-running RUBE_SEARCH_TOOLS before each workflow.
Reuse session IDs within a single workflow to speed up sequential Leverly operations.

Frequently Asked Questions

Add this skill to your agents