Borneo Automation via Rube MCP
SkillSearchThis skill lets your AI handle Borneo tasks for you. Give it a job and it finds the right tool for the work, then runs it. That means routine Borneo work gets done without you handling each step yourself.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding the skill, start by asking your AI to search the available tools so it knows what each one does right now. Then describe the Borneo task you want handled and let it pick and run the right tool.
Then ask your AI: use the Borneo Automation via Rube MCP skill
What your AI can do with it
- Find the right tool for each Borneo task
- Run Borneo tools to complete the work
- Search the available tools to see what is currently supported
- Check each tool's latest details before using it
- Match the job you describe to the tool that fits it
What this skill tells your AI
The instructions your AI receives, as published by composiohq/awesome-claude-skills in composio-skills/borneo-automation/SKILL.md and read by ahel’s review.
Automate Borneo operations through Composio's Borneo toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/borneo
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Borneo connection via
RUBE_MANAGE_CONNECTIONSwith toolkitborneo - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitborneo - 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: "Borneo 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 Borneo task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["borneo"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Borneo-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit borneo |
| 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 |
Powered by Composio
Signals
- GitHub stars
- 75k
- Forks
- 9k
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
borneo-automation- Source
- github.com/composiohq/awesome-claude-skills