recallai-automation

Recallai Automation Skills — Implementing Composio Integration via Rube MCP

Skill Overview

Recallai Automation is an automation skill implemented through Rube MCP and the Composio Recallai toolkit. It supports dynamic tool discovery, connection management, and batch execution. Recallai operations can be integrated without requiring an API key.

Applicable Scenarios

Projects that require dynamic tool schemas — When Recallai tool interfaces may be updated, use RUBE_SEARCH_TOOLS to fetch the latest schema in real time, avoiding call failures caused by hard-coded definitions.

MCP workflow integration — Integrate Recallai functionality into AI assistants built on the Model Context Protocol by using standard MCP interfaces for tool calls.

Batch Recallai operations — When you need to execute multiple Recallai tools at once, or when you need to reuse session state in an automation workflow.

Core Capabilities

Dynamic tool discovery — Query available Recallai tools and their input schemas in real time via RUBE_SEARCH_TOOLS. It returns a recommended execution plan and known issues, ensuring tool calls remain compatible with the current API version.

Connection status management — Use RUBE_MANAGE_CONNECTIONS to check and manage Recallai toolkit connection status. Supports automated activation flows and connection health checks.

Batch tool execution — Execute multiple tools within a single request using RUBE_MULTI_EXECUTE_TOOL. Supports session reuse and passing memory parameters, improving efficiency for batch operations.

Common Questions

How do I add a Rube MCP server in the configuration?

Add https://rube.app/mcp as the MCP server address in the client configuration file. No registration or API key is required. After adding it, you can verify the connection by using RUBE_SEARCH_TOOLS. It is recommended to call the tool after configuration to confirm that MCP communication is working properly.

Why must I call RUBE_SEARCH_TOOLS first?

Composio tool schemas change across versions. Hard-coding tool slugs or parameter fields may cause calls to fail. RUBE_SEARCH_TOOLS returns the current latest tool list, input schemas, and a recommended execution plan, along with reminders about known issues—ensuring your automation scripts stay compatible with the API.

How should session IDs be used correctly?

In the same workflow, reuse session_id to maintain state continuity. When starting a new workflow, use generate_id: true to create a new session. RUBE_MULTI_EXECUTE_TOOL requires a valid session_id; otherwise, it may not correctly associate connection state or execution context.