Bubble Automation
This skill automates operations within the Bubble platform using Composio's toolkit via Rube MCP. It is intended for developers and users who want to...
Install
npx promptshop add bubble-automationDetails
What This Skill Does
This skill automates operations within the Bubble platform using Composio's toolkit via Rube MCP. It is intended for developers and users who want to programmatically interact with their Bubble applications. The skill focuses on discovering available tools and managing connections before executing workflows.
When to Use
- Automate user creation.
- Update database records.
- Trigger workflows.
- Retrieve data from Bubble.
- Manage application settings.
- Create new app elements.
Key Features
- Discovers available tools via RUBE_SEARCH_TOOLS.
- Manages Bubble connections using RUBE_MANAGE_CONNECTIONS.
- Executes tools with RUBE_MULTI_EXECUTE_TOOL.
- Provides setup instructions for Rube MCP.
- Offers a core workflow pattern for tool execution.
- Highlights common pitfalls and how to avoid them.
Manual Installation
Automate Bubble operations through Composio's Bubble toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/bubble
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available).
- Active Bubble connection via RUBE_MANAGE_CONNECTIONS with toolkit bubble.
- 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 bubble 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: "Bubble 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 Bubble task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["bubble"] 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 Bubble-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit bubble |
| 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 Bubble operations through Composio's Bubble toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/bubble
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available).
- Active Bubble connection via RUBE_MANAGE_CONNECTIONS with toolkit bubble.
- 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 bubble 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: "Bubble 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 Bubble task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["bubble"] 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 Bubble-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit bubble |
| 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 |