hyperise-automation

Hyperise Automation - Rube MCP Agent Skills

Skill Overview

Hyperise Automation is an agent skill that automatically executes Hyperise tasks via Rube MCP (Composio). It supports tool discovery, connection management, and batch operations, enabling quick integration without the need for an API key.

Use Cases

Marketing automation workflows: Automatically generate and manage personalized marketing images, and process Hyperise campaigns in batches—ideal for marketing teams that need large-scale personalized content.

Fast developer integration: With Rube MCP, no API key configuration is required. You can use the Hyperise toolkit directly in Claude Code or other MCP clients for development.

Enterprise-grade batch operations: Use RUBE_REMOTE_WORKBENCH to run batch tasks, with support for pagination and session reuse—suitable for enterprise users handling large volumes of Hyperise data.

Core Features

Dynamic tool discovery: Use RUBE_SEARCH_TOOLS to retrieve the latest tool schema and execution plan in real time, ensuring the correct API structure is always used and preventing call failures caused by schema changes.

Connection status management: Use RUBE_MANAGE_CONNECTIONS to check and manage Hyperise connection status. Supports completing authentication via links, and ensures operations run only after the connection is active.

Batch task execution: Use RUBE_MULTI_EXECUTE_TOOL and RUBE_REMOTE_WORKBENCH to support multi-tool chaining and batch operations. Combine with memory parameters to implement complex workflows.

FAQs

How do I get started with Hyperise Automation?

First, add the Rube MCP server (https://rube.app/mcp) to your client configuration. After confirming that RUBE_SEARCH_TOOLS is available, call RUBE_MANAGE_CONNECTIONS and specify the toolkit as "hyperise". Complete authentication using the returned link to start using it.

Does the Hyperise skill require an API key?

No. Rube MCP provides a no-key integration method—you only need to add the MCP server endpoint. When connecting to Hyperise, authorization is completed via the authentication link returned by RUBE_MANAGE_CONNECTIONS, with no manual API credential management.

Why do I always need to call RUBE_SEARCH_TOOLS first?

Composio’s tool schemas are frequently updated. Hard-coding tool slugs and parameters often leads to call failures. RUBE_SEARCH_TOOLS returns the latest available tools, input schemas, and recommended execution plans, and also includes known pitfalls—ensuring your calls remain compatible with the current API.