Algolia Automation

What This Skill Does

• This skill automates Algolia operations using Composio's Algolia toolkit via Rube MCP.
• It's tailored for developers and engineers who need to programmatically manage and interact with Algolia search services.
• The skill emphasizes dynamic tool discovery and connection management for efficient and reliable search automation.

When to Use

• Automate index updates in Algolia.
• Manage Algolia search configurations.
• Integrate Algolia into e-commerce platforms.
• Optimize search relevance programmatically.
• Schedule index backups.
• Monitor search performance metrics.

Key Features

• Uses Rube MCP for tool access.
• Dynamically discovers available tools via RUBE_SEARCH_TOOLS.
• Manages connections using RUBE_MANAGE_CONNECTIONS.
• Executes tools with RUBE_MULTI_EXECUTE_TOOL.
• Requires active Algolia connection.
• Ensures schema compliance for tool arguments.

Manual Installation

Manual installation View Full Skill Content The complete markdown content that gets installed Algolia Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/algolia

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Algolia connection via RUBE_MANAGE_CONNECTIONS with toolkit algolia 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 algolia 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: "Algolia 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

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["algolia"] 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: {}

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