Do I always need to search tools first?

Yes. Tool schemas change; always call RUBE_SEARCH_TOOLS to get current slugs and input fields before execution.

How do I verify the Membervault connection is ready?

Use RUBE_MANAGE_CONNECTIONS with toolkit 'membervault' and ensure the status is ACTIVE before running any workflows.

What must I include in RUBE_MULTI_EXECUTE_TOOL calls?

Include memory (even if empty) and a valid session_id, and use the exact tool_slug and arguments from the latest tool schemas.

membervault-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Membervault Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/membervault

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["membervault"]
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 Membervault-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `membervault`
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/membervault-automation/SKILL.md

View on GitHub

Overview

Automate Membervault operations through Composio's Rube MCP toolkit. This skill emphasizes discovering current tool schemas before execution, validating active connections, and executing prepared workflows to manage Membervault tasks.

How This Skill Works

Rube MCP automation starts by discovering available Membervault tools with RUBE_SEARCH_TOOLS to fetch current schemas. It then validates an ACTIVE connection with RUBE_MANAGE_CONNECTIONS and runs the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments, session_id, and a memory object.

When to Use It

Automating common Membervault operations such as user provisioning or bulk updates.
When tool schemas change and you need to pull the latest tool slugs and fields with RUBE_SEARCH_TOOLS.
Before executing any workflow to ensure the Membervault connection is ACTIVE.
When chaining multiple tools in a single workflow that requires a shared session_id.
When handling large result sets that require pagination tokens during tool discovery.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds and establish a MEMBERVAULT connection with RUBE_MANAGE_CONNECTIONS.
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, memory, and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to get up-to-date tool slugs and schemas.
Verify the Membervault connection is ACTIVE with RUBE_MANAGE_CONNECTIONS before any tool execution.
Use exact field names and types from the search results; avoid hardcoding.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if it's empty.
Reuse session IDs within a workflow and handle pagination tokens when large results are returned.

Example Use Cases

Provision a new member by discovering its provisioning tool and executing with the required arguments.
Bulk update member access levels by discovering and running a bulk-edit tool.
Re-establish an inactive Membervault connection by following the auth flow and retrying the workflow.
Chain multiple tools (e.g., search, validate, and execute) in one workflow using a shared session_id for a member's lifecycle.
Paginate through a large list of members or tools by continuing requests using pagination tokens until complete.

Frequently Asked Questions

Add this skill to your agents