What is required to start?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available, and an active Apiverve connection via RUBE_MANAGE_CONNECTIONS.

Why is tool discovery required?

Tool schemas change frequently. Discovering tools ensures you use current slugs and input schemas, avoiding hardcoding errors.

How do I execute a tool?

Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, correct arguments per the schema, a memory object, and a session_id.

apiverve-automation

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

Files (1)

SKILL.md

2.9 KB

Apiverve Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/apiverve

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Apiverve operations through Composio's Apiverve toolkit via Rube MCP. It emphasizes discovering current tool schemas before execution to ensure you’re using up-to-date inputs and avoid breaking changes.

How This Skill Works

Connect Rube MCP to Apiverve and call RUBE_SEARCH_TOOLS to fetch the latest tool slugs and input schemas. Validate the toolkit connection with RUBE_MANAGE_CONNECTIONS and execute selected tools using RUBE_MULTI_EXECUTE_TOOL, always including a memory object and reusing a session_id for continuity.

When to Use It

Automate recurring Apiverve tasks without hardcoding tool slugs; ensure schemas stay current.
Verify the Rube MCP-APIVERVE connection is ACTIVE before running workflows.
Discover available tools first to tailor the workflow to current capabilities.
Run multi-tool workflows that require memory and a persistent session.
Handle changes in tool schemas by re-fetching tool schemas before execution.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["apiverve"] and ensure the status is ACTIVE.
Step 3: Discover a tool with RUBE_SEARCH_TOOLS, then execute it with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id.

Best Practices

Always run RUBE_SEARCH_TOOLS before selecting tools.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before execution.
Use exact field names and types from the tool schemas.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and paginate tool searches as needed.

Example Use Cases

Automate a weekly Apiverve data pull and push results to a dashboard.
Execute a sequence of Apiverve operations after establishing an active connection.
Bulk-run multiple tools via RUBE_MULTI_EXECUTE_TOOL and store outputs.
Handle paginated tool listings by repeatedly calling RUBE_SEARCH_TOOLS until complete.
Adapt an automation to schema changes by re-fetching tool schemas before execution.

Frequently Asked Questions

Add this skill to your agents