Membervault Automation

What This Skill Does

This skill automates Membervault operations using Composio's Membervault toolkit via Rube MCP. It allows users to manage and interact with Membervault data and functionalities through automated workflows. This is ideal for users who want to streamline their Membervault tasks and integrate them with other systems.

When to Use

• Create new users in Membervault
• Update existing user profilesEnroll users in specific courses
• Generate reports on user activity
• Manage product access
• Automate content delivery

Key Features

• Automates Membervault tasks via Rube MCP
• Uses Composio's Membervault toolkit
• Requires an active Membervault connection
• Discovers available tools using RUBE_SEARCH_TOOLS
• Checks connection status with RUBE_MANAGE_CONNECTIONS
• Executes tools using RUBE_MULTI_EXECUTE_TOOL

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedMembervault 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

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