How do I ensure the tool slugs and schemas are current?

Always run RUBE_SEARCH_TOOLS before selecting and calling any tool; tool slugs and arguments come from current schemas.

What if the Mem connection is not ACTIVE?

Call RUBE_MANAGE_CONNECTIONS again, follow the provided auth link to activate, and re-check status before execution.

Do I need API keys to use mem-automation?

No API keys are required for the MCP endpoint; simply add the endpoint in the MCP server config and ensure RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS are available.

mem-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Mem Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mem

Prerequisites

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

Step 2: Check Connection

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

Overview

Mem Automation via Rube MCP enables executing Mem operations through Composio's Mem toolkit. It emphasizes always fetching current tool schemas with RUBE_SEARCH_TOOLS before running workflows to ensure valid tool slugs and inputs.

How This Skill Works

Connect to Rube MCP (no API keys needed) and verify Mem access with RUBE_SEARCH_TOOLS. Discover available Mem tools, confirm the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then execute a selected tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug and correctly structured arguments, including a memory payload.

When to Use It

Automate a Mem task and fetch current tool schemas first
Set up a new Mem workflow and verify an ACTIVE Mem connection
Run several Mem operations in a single session
Ensure exact field names and types match the discovered tool schemas
Perform bulk Mem operations via batch tools like RUBE_REMOTE_WORKBENCH when needed

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config and verify RUBE_SEARCH_TOOLS returns Mem tool schemas
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit mem and ensure the connection status is ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS, pick a tool slug, and execute it with RUBE_MULTI_EXECUTE_TOOL using a session_id and proper arguments

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to obtain current tool schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs for related workflows and generate new ones for new tasks

Example Use Cases

Discover available Mem operation tools with RUBE_SEARCH_TOOLS, select a slug, and execute it with RUBE_MULTI_EXECUTE_TOOL using the required arguments
Verify a Mem connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before initiating a Mem workflow
Execute a sequence of Mem tasks in one session by reusing a session_id and passing appropriate memory payloads
Perform a bulk Mem operation using RUBE_REMOTE_WORKBENCH and run_composio_tool for batch processing
Inspect the full tool schema with RUBE_GET_TOOL_SCHEMAS to confirm the exact input fields before execution

Frequently Asked Questions

Add this skill to your agents