API Labz Automation via Rube MCP
SkillSearchOnce added, your AI can handle tasks in API Labz on your behalf by finding and running the operations API Labz makes available. It checks the current details of each operation before using it, so tasks run against up-to-date information. This works through the tools you already have connected.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding it, make sure your connected tools are set up and tell your AI which API Labz task you want done. It will first look up the available operations, then run the ones needed.
Then ask your AI: use the API Labz Automation via Rube MCP skill
What your AI can do with it
- Look up the operations available in API Labz
- Run API Labz operations for you
- Automate everyday API Labz tasks end to end
- Check the latest details of each operation before acting on it
What this skill tells your AI
The instructions your AI receives, as published by composio-community/awesome-codex-skills in composio-skills/api-labz-automation/SKILL.md and read by ahel’s review.
Automate API Labz operations through Composio's API Labz toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/api_labz
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active API Labz connection via
RUBE_MANAGE_CONNECTIONSwith toolkitapi_labz - 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 toolkitapi_labz - 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: "API Labz 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 API Labz task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["api_labz"]
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 API Labz-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit api_labz |
| 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
- 16k
- Forks
- 2k
- Last commit
- Jul 2026
Others that do the same job
Advanced
- Catalog kind
- skill
- Gateway key
api-labz-automation- Source
- github.com/composio-community/awesome-codex-skills