API Bible Automation

What This Skill Does

• This skill automates API Bible operations using Composio's API Bible toolkit through Rube MCP.
• It is designed for developers who need to integrate API Bible functionalities into their workflows.
• The skill ensures proper setup, tool discovery, and execution while adhering to schema compliance.

When to Use

• Automate API Bible tasks.
• Discover available API tools.
• Check API Bible connection status.
• Execute specific API Bible tools.
• Handle schema-compliant arguments.
• Integrate API Bible into workflows.

Key Features

• Uses Rube MCP for API Bible automation.
• Requires an active API Bible connection.
• Employs RUBE_SEARCH_TOOLS for tool discovery.
• Utilizes RUBE_MANAGE_CONNECTIONS for connection checks.
• Executes tools via RUBE_MULTI_EXECUTE_TOOL.
• Ensures schema compliance with API Bible.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedAPI Bible Automation via Rube MCP

Automate API Bible operations through Composio's API Bible toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/api_bible

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active API Bible connection via RUBE_MANAGE_CONNECTIONS with toolkit api_bible Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

• Get Rube MCP: Add https://rube.
• 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 api_bible 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 Bible 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 Bible task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["api_bible"] 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