Bonsai Automation
This skill enables users to automate Bonsai operations using Composio's Bonsai toolkit via Rube MCP. It is intended for developers and automation engineers who
Install
npx promptshop add bonsai-automationDetails
What This Skill Does
This skill enables users to automate Bonsai operations using Composio's Bonsai toolkit via Rube MCP. It is intended for developers and automation engineers who need to incorporate Bonsai's machine learning capabilities into their applications. The skill focuses on simplifying the setup, connection, and execution of Bonsai tools through Rube MCP.
When to Use
Automate model training workflowsDeploy trained Bonsai modelsMonitor model performanceIntegrate Bonsai with existing systemsOptimize control policiesAdapt to changing environments
Key Features
Discovers available tools via RUBE_SEARCH_TOOLSManages connections using RUBE_MANAGE_CONNECTIONSExecutes tools with RUBE_MULTI_EXECUTE_TOOLProvides setup instructions for Rube MCPOffers a core workflow pattern for tool executionHighlights common pitfalls and solutions
Bonsai Automation via Rube MCP
Automate Bonsai operations through Composio's Bonsai toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/bonsai
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Bonsai connection via RUBE_MANAGE_CONNECTIONS with toolkit bonsai 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 bonsai 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: "Bonsai 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 Bonsai task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["bonsai"] 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
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Bonsai-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit bonsai |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Automate Bonsai operations through Composio's Bonsai toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/bonsai