PromptShop

Openrouter Automation

This skill automates Openrouter operations using the Composio Openrouter toolkit through Rube MCP. It enables users to programmatically manage and optimize A.

Install

npx promptshop add openrouter-automation

Details

What This Skill Does

This skill automates Openrouter operations using the Composio Openrouter toolkit through Rube MCP. It enables users to programmatically manage and optimize AI model routing. It is designed for developers and automation engineers.

When to Use

  • Route requests to optimal AI models.
  • Manage AI model configurations.
  • Automate model selection.
  • Monitor model performance.
  • Integrate AI routing into applications.
  • Optimize AI inference costs.

Key Features

  • Connects to Openrouter via Rube MCP.
  • Discovers available tools dynamically.
  • Manages Openrouter connections.
  • Executes Openrouter tools with schema validation.
  • Provides a structured workflow pattern.
  • Offers guidance on avoiding common pitfalls.

Manual Installation

Openrouter Automation via Rube MCP

Automate Openrouter operations through Composio's Openrouter toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/openrouter

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Openrouter connection via RUBE_MANAGE_CONNECTIONS with toolkit openrouter 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 openrouter 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: "Openrouter 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 Openrouter task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Openrouter-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit openrouter
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Openrouter Automation via Rube MCP

Automate Openrouter operations through Composio's Openrouter toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/openrouter

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Openrouter task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Openrouter-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit openrouter
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef