instacart-automation
Automate Instacart tasks via Rube MCP (Composio). Always search tools first for current schemas.
Author
Category
Development ToolsInstall
Download and extract to your skills directory
Copy command and send to OpenClaw for auto-install:
Instacart Automation — Deliveries Automation via Rube MCP
Skills Overview
Instacart Automation is a Claude skill built on Rube MCP that lets you automatically manage your Instacart account, batch-process orders, and optimize delivery workflows—without needing an API key.
Use Cases
RUBE_MULTI_EXECUTE_TOOL, you can execute multiple actions at once, significantly improving efficiency.Core Features
RUBE_SEARCH_TOOLS to automatically fetch the latest Instacart tool schema and execution plans, eliminating the need to manually maintain a tool list. When the Instacart API updates, the skill automatically adapts to the latest available operations.RUBE_MANAGE_CONNECTIONS to easily establish and manage Instacart account connections. Supports connection status checks and reauthorization to ensure reliable workflow execution.RUBE_MULTI_EXECUTE_TOOL and a session reuse mechanism to execute multiple Instacart actions within a single call. It also preserves context within the workflow, enabling complex automation scenarios.FAQ
What is Rube MCP? Do I need an API key?
Rube MCP is a free MCP server provided by Composio. You only need to add https://rube.app/mcp as the server address in your Claude client configuration. No account registration or API key is required.
How do I get started with Instacart Automation?
First, confirm that Rube MCP is connected (call RUBE_SEARCH_TOOLS to verify). Then use RUBE_MANAGE_CONNECTIONS and specify the toolkit as instacart to create the connection. If the connection status is not ACTIVE, complete login by following the authorization link returned.
Will the tool schema change?
Yes. Instacart’s available operations and parameter structures may be updated. Therefore, before each workflow execution, you should call RUBE_SEARCH_TOOLS to get the latest tool schema instead of hard-coding tool names and parameters—this ensures compatibility.