Rube MCP is a Composio-integrated MCP that discovers Passcreator tools and manages connections for automated workflows.

Why must tools be discovered first?

Tool schemas change over time; discovery returns current slugs, input fields, execution plans, and pitfalls to avoid breakage.

What if the connection is not ACTIVE?

Follow the returned auth link to complete setup, then re-check until the connection status shows ACTIVE before running workflows.

passcreator-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Passcreator Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/passcreator

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

Automate Passcreator operations through Composio's Passcreator toolkit via Rube MCP. Always search tools first to fetch current schemas and keep workflows compatible.

How This Skill Works

The skill uses RUBE_SEARCH_TOOLS to discover available Passcreator tools, then establishes a connection with RUBE_MANAGE_CONNECTIONS for the Passcreator toolkit, and finally executes tools with RUBE_MULTI_EXECUTE_TOOL, passing the discovered schema fields and a memory object. This ensures you always run the correct tool slugs and input schemas, with a per-call memory payload and a valid session_id.

When to Use It

Onboarding new users by auto-generating Passcreator passes from a sign-up feed.
Scheduling recurring Passcreator tasks (e.g., passes refresh or updates) that must run with current tool schemas.
Validating tool schemas and updating workflows after a schema change.
Diagnosing failures by re-discovering tools and re-running with fresh slugs.
Executing bulk Passcreator operations in a batch using discovered tools.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds and connect to toolkit passcreator with RUBE_MANAGE_CONNECTIONS.
Step 3: Discover tools and run a sample tool with RUBE_MULTI_EXECUTE_TOOL, ensuring memory and session_id are provided.

Best Practices

Always search first: fetch current tool schemas before any run to avoid stale slugs or fields.
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: include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Session reuse: reuse session IDs within a workflow to improve reliability.

Example Use Cases

Auto-create Passcreator passes for all new sign-ups in a campaign.
Apply a schema change across multiple Passcreator tools and re-run workflows.
Run a nightly batch of Passcreator tasks with a single session for efficiency.
Switch to updated tool slugs after a discovery pass to stay in sync with schemas.
Bulk-update pass metadata for a partner event using discovered tool inputs.

Frequently Asked Questions

Add this skill to your agents