Algodocs Automation via Rube MCP

Prerequisites

• Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
• Active Algodocs connection via RUBE_MANAGE_CONNECTIONS with toolkit algodocs
• Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
2. Call RUBE_MANAGE_CONNECTIONS with toolkit algodocs
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

RUBE_SEARCH_TOOLS
queries: [{use_case: "Algodocs operations", known_fields: ""}]
session: {generate_id: true}

Core Workflow Pattern

Step 1: Discover Available Tools

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

Step 2: Check Connection

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