What is RUBE MCP and why search tools first?

RUBE MCP is Composio's managed control plane for tool integration. Searching tools first ensures you always use current tool schemas and slugs.

How do I check the connection status?

Use RUBE_MANAGE_CONNECTIONS with the pdf4me toolkit and confirm the status is ACTIVE before executing any tools. If not active, follow the provided auth link.

What should memory contain in multi tool calls?

Memory must be a JSON object and is required for RUBE_MULTI_EXECUTE_TOOL even if empty, e.g., memory: {}.

pdf4me-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Pdf4me Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/pdf4me

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Pdf4me operations through Composio's Pdf4me toolkit using the Rube MCP. It emphasizes discovering tool schemas first and ensuring an active connection before running workflows.

How This Skill Works

The workflow relies on three calls: RUBE_SEARCH_TOOLS to discover available Pdf4me tool schemas, RUBE_MANAGE_CONNECTIONS to ensure the pdf4me toolkit connection is ACTIVE, and RUBE_MULTI_EXECUTE_TOOL to run a chosen tool with a memory payload and a session id.

When to Use It

You need to automate a specific Pdf4me task using a tool slug discovered at runtime.
Tool schemas change often, so always fetch current schemas before coding or executing.
Setting up a new Pdf4me connection or reusing an existing session for continued workflows.
Validating connection status before executing tools to avoid failed runs.
Performing batch or bulk Pdf4me operations using multi tool execution within a session.

Quick Start

Step 1: Add the rube MCP endpoint https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit pdf4me to ensure an ACTIVE connection.
Step 3: Use RUBE_SEARCH_TOOLS to identify TOOL_SLUG_FROM_SEARCH, then run RUBE_MULTI_EXECUTE_TOOL with the discovered slug, memory, and a session_id.

Best Practices

Always run RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.
Use exact field names and types from the search results; avoid hardcoding.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and refresh for new tasks as needed.

Example Use Cases

Compress a PDF using the discovered tool slug from RUBE_SEARCH_TOOLS.
Merge multiple PDFs by discovering the merge tool slug and executing with memory payload.
Extract text from a PDF by calling the appropriate tool slug from search results.
Process a batch of PDFs in a single session using RUBE_MULTI_EXECUTE_TOOL with memory and session_id.
Establish a new pdf4me connection, verify ACTIVE, then run a workflow across tools.

Frequently Asked Questions

Add this skill to your agents