bonsai-automation
Automate Bonsai tasks via Rube MCP (Composio). Always search tools first for current schemas.
Bonsai Automation Skills - Implemented Through Rube MCP
Skill Overview
Bonsai Automation is a Bonsai task automation skill implemented via a Rube MCP server. It uses Composio’s Bonsai toolkit, allowing you to connect to and execute Bonsai operations without needing an API key.
Use Cases
-
Automating Bonsai Workflows: Scenarios that require batch or periodic execution of Bonsai tasks, such as data synchronization and bulk updates—repetitive operations.
-
Dynamic Tool Discovery and Execution: When Bonsai tool modes might change, use RUBE_SEARCH_TOOLS to fetch the latest tool definitions in real time, ensuring that execution parameters are correct.
-
Simplified Connection Management: Suitable for developers who don’t want to handle complex API authentication. Simply add the Rube MCP endpoint to start using Bonsai functionality.
Core Features
-
Tool Discovery Mode: Use RUBE_SEARCH_TOOLS to first discover available tools. Retrieve the current tool mode, recommended execution plans, and known pitfalls to avoid hardcoding outdated tool definitions.
-
Connection State Management: Use RUBE_MANAGE_CONNECTIONS to check and manage Bonsai connection status, ensuring that the connection is in ACTIVE state before running a workflow.
-
Batch Execution of Multiple Tools: Use RUBE_MULTI_EXECUTE_TOOL to execute multiple tools within a single session. Supports in-memory parameters and session reuse, enabling complex automation workflows.
Frequently Asked Questions
What Configuration Does Rube MCP Require?
Just add https://rube.app/mcp as an MCP server. No API key is needed. After adding it, verify the connection by confirming that RUBE_SEARCH_TOOLS responds normally.
How Do I Establish a Bonsai Connection?
- First call RUBE_MANAGE_CONNECTIONS and specify the toolkit as
"bonsai". - If the connection is not activated, complete the setup using the authentication link returned.
- Once the status shows ACTIVE, you can start executing workflows.
Why Call RUBE_SEARCH_TOOLS First?
Tool modes change over time. Hardcoding tool definitions can lead to execution failures. RUBE_SEARCH_TOOLS returns the latest tool mode, input mode, and known pitfalls, ensuring that subsequent executions are correct.