Hyperise Automation

What This Skill Does

This skill automates Hyperise operations using Composio's Hyperise toolkit via Rube MCP. It enables users to programmatically interact with Hyperise features, streamlining workflows and integrations. This is beneficial for those seeking to automate repetitive tasks or connect Hyperise with other systems.

When to Use

Automate image personalizationCreate dynamic website contentIntegrate Hyperise with marketing automation platformsPersonalize email campaigns with dynamic imagesAutomate A/B testing of personalized contentGenerate personalized landing pages

Key Features

Uses Rube MCP for tool discovery and executionRequires an active Hyperise connectionDiscovers available tools and schemas dynamicallyProvides a core workflow pattern for tool executionEmphasizes the importance of schema complianceManages connections via RUBE_MANAGE_CONNECTIONS

Manual Installation

Hyperise Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/hyperise

Prerequisites

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

Step 2: Check Connection

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