What is Rube MCP in this context?

Rube MCP is Composio's Multi-Cloud Protocol for connecting and orchestrating external toolkits, here used to automate Process Street tasks.

Do I always need to search for tools first?

Yes. The toolkit emphasizes calling RUBE_SEARCH_TOOLS to fetch current tool schemas and avoid hardcoding slugs or arguments.

How can I verify a connection is ready?

Call RUBE_MANAGE_CONNECTIONS with the 'process_street' toolkit and ensure the status is ACTIVE before running workflows.

process-street-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

Process Street Automation via Rube MCP

Automate Process Street operations through Composio's Process Street toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/process_street

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["process_street"]
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 Process Street-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `process_street`
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/process-street-automation/SKILL.md

View on GitHub

Overview

This skill automates Process Street operations through Composio's Rube MCP toolkit. It requires an active Rube MCP connection and a configured Process Street toolkit, and emphasizes discovering current tool schemas before execution.

How This Skill Works

The workflow starts by querying RUBE_SEARCH_TOOLS to fetch available Process Street tools and their input schemas. It then uses RUBE_MANAGE_CONNECTIONS to ensure the process_street toolkit is ACTIVE, and finally executes tools with RUBE_MULTI_EXECUTE_TOOL, supplying memory and the discovered arguments.

When to Use It

When automating a recurring Process Street workflow
When you need the latest tool schemas before execution
When establishing or validating a new Process Street connection
When performing bulk actions across multiple Process Street tasks
When auditing tool activity and reusing session IDs in a run

Quick Start

Step 1: Add Rube MCP endpoint (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS
Step 2: Manage connection with toolkit 'process_street' and ensure ACTIVE
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug and proper arguments, including memory and 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 every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow; generate new ones for separate runs

Example Use Cases

Auto-create a Process Street checklist when a form is submitted
Update Process Street task fields when a CRM event occurs
Bulk-create several Process Street tasks for a project using discovered tool slugs
Run a scheduled Process Street workflow with a reused session for consistency
Run a diagnostic sequence to verify tool schemas and ACTIVE connections

Frequently Asked Questions

Add this skill to your agents