memberstack-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/memberstack-automation --openclawMemberstack Automation via Rube MCP
Automate Memberstack operations through Composio's Memberstack toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/memberstack
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Memberstack connection via
RUBE_MANAGE_CONNECTIONSwith toolkitmemberstack - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitmemberstack - 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: "Memberstack 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 Memberstack task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["memberstack"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Memberstack-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit memberstack |
| 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/memberstack-automation/SKILL.mdView on GitHub Overview
Automate Memberstack operations via Composio's Memberstack toolkit through Rube MCP. It relies on discovering up-to-date tool schemas before every workflow and requires an active Rube MCP connection with the Memberstack toolkit. This keeps complex routines reproducible and reduces manual errors by driving workflows through discovered tool slugs and schemas.
How This Skill Works
Use RUBE_SEARCH_TOOLS to discover available Memberstack tools and their input schemas. Verify your connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and exact arguments from the schema, while including an empty or populated memory object and a session_id to maintain workflow state.
When to Use It
- You need to perform a specific Memberstack operation but want to ensure you’re using the current tool schemas first (via RUBE_SEARCH_TOOLS).
- You must confirm the Memberstack connection is ACTIVE before running any workflow.
- You want to execute a tool with precise, schema-driven arguments and a memory payload as required by RUBE_MULTI_EXECUTE_TOOL.
- You intend to reuse a session ID across a workflow to maintain continuity between steps.
- You’re handling large results or multiple operations and need to paginate or batch tool executions.
Quick Start
- Step 1: Ensure Rube MCP is connected and call RUBE_SEARCH_TOOLS to fetch current Memberstack tool schemas.
- Step 2: Verify the Memberstack connection is ACTIVE with RUBE_MANAGE_CONNECTIONS.
- Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug, exact arguments, memory, and a session_id.
Best Practices
- Always search first: Tool schemas change, so fetch current slugs and field names with RUBE_SEARCH_TOOLS.
- Check connection: Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
- Schema compliance: Use exact field names and types from the search results without guessing.
- Memory usage: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty {}.
- Session management: Reuse session IDs within a workflow and generate new ones for separate runs.
Example Use Cases
- Create or update a Memberstack member when a new signup event occurs, using a discovered tool slug and schema-driven arguments.
- Sync Memberstack profile fields (e.g., name, email, tags) with changes from an external CRM system.
- Adjust a member's plan or status in Memberstack after a checkout or upgrade in your payment system.
- Deactivate or remove a Memberstack member based on an external termination status within an automated workflow.
- Batch-update multiple members using a bulk operation via RUBE_REMOTE_WORKBENCH and run_composio_tool with discovered tool slugs.
