Cults Automation via Rube MCP

SkillSearch

Automate your tasks on Cults, the 3D model marketplace, through your AI. Once this skill is added, your AI can find out which Cults actions are available and run them for you, handling routine steps so you do not have to.

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add the skill and tell your AI what you want done on Cults. Start by asking it to show which Cults actions it has available, then let it run your task.

Then ask your AI: use the Cults Automation via Rube MCP skill

What your AI can do with it

  • Work with Cults, the 3D model marketplace, directly through your AI
  • Discover which Cults actions are available right now
  • Run Cults tasks on your behalf
  • Check the current details of an action before running it, so tasks use the right steps

What this skill tells your AI

The instructions your AI receives, as published by composio-community/awesome-codex-skills in composio-skills/cults-automation/SKILL.md and read by ahel’s review.

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

Toolkit docs: composio.dev/toolkits/cults

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["cults"]
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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Cults-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit cults
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

Signals

GitHub stars
17k
Forks
2k
Last commit
Jul 2026

Others that do the same job

Advanced
Item type
skill
Key
cults-automation
Source
github.com/composio-community/awesome-codex-skills