What is Rube MCP and how does it relate to Amcards automation?

Rube MCP is the MCP server used to search for current tool schemas and manage connections for the Amcards toolkit, enabling dynamic, schema-driven automation.

Do I need API keys to use amcards-automation?

No. The setup uses a MCP endpoint (https://rube.app/mcp) and toolkit connections; no API keys are required.

What are common pitfalls when using this skill?

- Always search first: tool schemas change, avoid hardcoding slugs or arguments.\n- Check connection: ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.\n- Schema compliance: use exact field names and types from search results.\n- Memory parameter: include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).\n- Session reuse: reuse session IDs within a workflow; generate new ones for new workflows.\n- Pagination: handle pagination tokens and fetch until complete.

amcards-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Amcards Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/amcards

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Amcards operations through Composio's Amcards toolkit using Rube MCP. The skill emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running any workflows to avoid hardcoding slugs or arguments.

How This Skill Works

Connect to Rube MCP and the Amcards toolkit, then discover available tools and their input schemas. Validate the connection status is ACTIVE, then execute tools using RUBE_MULTI_EXECUTE_TOOL with a memory payload and a session_id.

When to Use It

Starting a new Amcards workflow and you need the current tool schemas (to avoid hardcoding tool slugs and arguments).
Verifying that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running any tools.
Discovering available Amcards tool slugs and their input schemas for a task via RUBE_SEARCH_TOOLS.
Performing bulk operations using tools like RUBE_REMOTE_WORKBENCH or run_composio_tool.
Handling tool schema changes or pagination by fetching updates with RUBE_SEARCH_TOOLS and RUBE_GET_TOOL_SCHEMAS.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["amcards"] and complete any auth to reach ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then run a chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
Use exact field names and types from the search results (no hardcoding).
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse session IDs within a workflow; generate new ones for separate workflows and watch for pagination.

Example Use Cases

Discover tools for an Amcards operation using RUBE_SEARCH_TOOLS with use_case: 'Amcards operations', then connect and execute a chosen tool.
Connect to the Amcards toolkit via RUBE_MANAGE_CONNECTIONS with toolkits: ["amcards"], ensuring status is ACTIVE.
Execute a discovered tool slug by passing the required arguments and memory through RUBE_MULTI_EXECUTE_TOOL.
Bulk run multiple Amcards actions by using RUBE_REMOTE_WORKBENCH or run_composio_tool with a prepared tool list.
Inspect full tool schemas with RUBE_GET_TOOL_SCHEMAS to understand schemaRef-backed inputs before execution.

Frequently Asked Questions

Add this skill to your agents