What is mem0-automation?

Automate Mem0 operations via Rube MCP using the Mem0 toolkit.

What are the prerequisites?

Rube MCP connected (RUBE_SEARCH_TOOLS available) and an active Mem0 connection via RUBE_MANAGE_CONNECTIONS with toolkit 'mem0'.

Why always search tools first?

Tool schemas change over time; fetching current schemas prevents hardcoding slugs or arguments and ensures compatibility.

mem0-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Mem0 Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mem0

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Mem0 operations through Composio's Mem0 toolkit using Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before executing workflows to avoid hardcoding. Following the setup and workflow pattern ensures reliable, schema-aware automation.

How This Skill Works

Connect to Rube MCP and verify Mem0 toolkit access, then fetch up-to-date tool schemas with RUBE_SEARCH_TOOLS. Use RUBE_MANAGE_CONNECTIONS to ensure an ACTIVE Mem0 session, and finally run tools with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and the discovered tool slug and arguments.

When to Use It

Starting a Mem0 automation workflow for a new task to ensure correct tool selection
When tool schemas change or new Mem0 tools are added, to avoid broken integrations
Before executing any Mem0 workflow, to confirm an ACTIVE Mem0 connection
When reusing related Mem0 tasks within the same session for efficiency
For bulk or parallel Mem0 operations using bulk tooling like RUBE_REMOTE_WORKBENCH

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Run RUBE_SEARCH_TOOLS to confirm available Mem0 tool schemas
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkit 'mem0' and then RUBE_MULTI_EXECUTE_TOOL for execution

Best Practices

Always search first with RUBE_SEARCH_TOOLS to get current tool schemas
Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before executing tools
Use exact field names and types from the search results; avoid hardcoding slugs
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new ones only for new workflows

Example Use Cases

Discover available Mem0 tools with RUBE_SEARCH_TOOLS for a Mem0 task like data retrieval
Establish a Mem0 connection using RUBE_MANAGE_CONNECTIONS and verify ACTIVE
Execute a discovered MEM0 tool via RUBE_MULTI_EXECUTE_TOOL with proper arguments
Perform bulk Mem0 operations via RUBE_REMOTE_WORKBENCH using run_composio_tool()
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs

Frequently Asked Questions

Add this skill to your agents