home / skills / composiohq / awesome-claude-skills / memberspot-automation

memberspot-automation skill

safe

/memberspot-automation

This skill automates Memberspot tasks via Rube MCP and Composio toolkit, prioritizing live tool schemas and active connections for reliable workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill memberspot-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: memberspot-automation
description: "Automate Memberspot tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Memberspot Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/memberspot](https://composio.dev/toolkits/memberspot)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Memberspot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `memberspot`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `memberspot`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Memberspot 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 Memberspot task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["memberspot"]
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 Memberspot-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `memberspot` |
| 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](https://composio.dev)*

Overview

This skill automates Memberspot tasks by orchestrating Composio's Memberspot toolkit through Rube MCP. It provides a repeatable pattern for discovering tool schemas, verifying connections, and executing toolkit actions safely. The workflow emphasizes dynamic discovery and schema compliance to avoid runtime errors.

How this skill works

The skill queries RUBE_SEARCH_TOOLS to fetch current tool slugs, input schemas, and recommended execution plans. It checks and manages the Memberspot connection with RUBE_MANAGE_CONNECTIONS, then runs actions via RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH using schema-compliant arguments. Session IDs and memory bags are managed per workflow to ensure state and pagination handling.

When to use it

Automate user and subscription management in Memberspot
Run bulk operations or migrations against Memberspot data
Integrate Memberspot actions into larger agent workflows
Perform scheduled syncs or audits that require up-to-date tool schemas
Execute multi-step workflows that need composable toolkit actions

Best practices

Always call RUBE_SEARCH_TOOLS first to get current tool slugs and input schemas
Verify Memberspot connection status with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE
Use exact field names and types returned by the search; do not hardcode arguments
Include a memory object (even {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs within a workflow and generate new session IDs for new workflows
Watch for pagination tokens and iterate until complete

Example use cases

Create or update member records programmatically using discovered create/update tool schemas
Bulk-import course enrollments via RUBE_REMOTE_WORKBENCH and run_composio_tool() for batch processing
Automate subscription status checks and trigger follow-up actions when payments fail
Sync Memberspot user lists to an external CRM by paging through results and mapping fields
Run nightly audits to report inconsistencies using RUBE_GET_TOOL_SCHEMAS and multi-step execution

FAQ

Do I need API keys to use Rube MCP?

No API keys are required. Add https://rube.app/mcp as an MCP server in your client configuration to connect.

What if a tool slug or schema changes?

Always re-run RUBE_SEARCH_TOOLS before executing actions. The skill workflow depends on dynamic discovery to avoid breaking changes.

Can I run bulk jobs?

Yes. Use RUBE_REMOTE_WORKBENCH with run_composio_tool() for large or batched operations and handle pagination and memory accordingly.