Agenty Automation

What This Skill Does

This skill automates Agenty operations using Composio's Agenty toolkit through Rube MCP. It allows users to discover available tools, check connections, and execute tasks within the Agenty environment. It is designed for developers and automation engineers who need to integrate Agenty functionalities into their workflows.

When to Use

• Discover available Agenty tools.
• Check the status of an Agenty connection.
• Execute specific Agenty tasks.
• Automate web scraping tasks.
• Integrate Agenty with other systems.
• Troubleshoot Agenty connection issues.

Key Features

• Automates Agenty operations via Rube MCP.
• Uses Composio's Agenty toolkit.
• Discovers available tools using RUBE_SEARCH_TOOLS.
• Manages connections using RUBE_MANAGE_CONNECTIONS.
• Executes tools using RUBE_MULTI_EXECUTE_TOOL.
• Provides a structured workflow pattern.

Manual Installation

Agenty Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/agenty

Prerequisites

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

Step 2: Check Connection

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