mcpbeat

API Bible Automation

composiohq/api-bible-automation

Automate API Bible tasks via Rube MCP (Composio). Always search tools first for current schemas.

This is a copy. The original lives at christophacham/api-bible-automation.

738 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
71684
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill api-bible-automation

MCP servers it needs

declared by the author in the skill header

Not in the registry: rube

The skill names a server we cannot find in the official MCP registry. It may be private, renamed, or never published — either way, the skill will not work until you have it.

The instruction itself

10 sections, as written by the author

API 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.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 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

| Operation | Approach |

|-----------|----------|

| Find tools | RUBE_SEARCH_TOOLS with API Bible-specific use case |

| Connect | RUBE_MANAGE_CONNECTIONS with toolkit api_bible |

| 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*

How to use it

Copy the folder

Take composiohq/api-bible-automation from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.