Rocketlane Automation
This skill automates Rocketlane operations using Composio's Rocketlane toolkit through Rube MCP. It's designed for users who want to streamline project
Install
npx promptshop add rocketlane-automationDetails
What This Skill Does
This skill automates Rocketlane operations using Composio's Rocketlane toolkit through Rube MCP. It's designed for users who want to streamline project management and customer onboarding tasks within Rocketlane. The skill requires an active Rocketlane connection and utilizes Rube MCP for tool discovery and execution.
When to Use
- Automate project creation.
- Manage project tasks.
- Track project progress.
- Onboard new customers.
- Automate customer communication.
- Generate project reports.
Key Features
Automates Rocketlane tasks via Rube MCP.Uses Composio's Rocketlane toolkit. Discovers available tools using RUBE_SEARCH_TOOLS.Manages connections with RUBE_MANAGE_CONNECTIONS.Executes tools with RUBE_MULTI_EXECUTE_TOOL.Provides setup instructions and known pitfalls.
Rocketlane Automation via Rube MCP
Automate Rocketlane operations through Composio's Rocketlane toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/rocketlane
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Rocketlane connection via RUBE_MANAGE_CONNECTIONS with toolkit rocketlane 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 rocketlane 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: "Rocketlane 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 Rocketlane task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["rocketlane"] 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 Rocketlane-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit rocketlane |
| 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 Rocketlane operations through Composio's Rocketlane toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/rocketlane