Bench Automation

What This Skill Does

• This skill automates Bench operations using Composio's Bench toolkit via Rube MCP.
• It enables users to interact with their Bench accounting data and services programmatically. This is ideal for automating financial reporting and analysis workflows.

When to Use

• Retrieve financial statements from Bench.
• Automate bookkeeping tasks. Get transaction data from Bench. Monitor key financial metrics. Generate custom financial reports. Integrate Bench data with other systems.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Bench connection. Dynamically fetches tool schemas to ensure compatibility. Provides a structured workflow for tool execution. Includes error handling and connection verification. Integrates with the Composio Bench toolkit.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedBench Automation via Rube MCP

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

• Toolkit docs: composio.
• dev/toolkits/bench.

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["bench"] 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