Bolt Iot Automation

What This Skill Does

This skill allows users to automate Bolt Iot operations using Composio's Bolt Iot toolkit through Rube MCP. It is designed for developers and engineers who need to integrate and manage Bolt Iot devices and services within their workflows. The skill ensures proper setup, connection management, and tool execution by leveraging Rube MCP.

When to Use

Automate device provisioningManage sensor data collectionControl IoT device settingsTrigger actions based on IoT eventsMonitor device status remotelyIntegrate IoT data with other systems

Key Features

Discovers available tools via RUBE_SEARCH_TOOLSManages connections using RUBE_MANAGE_CONNECTIONSExecutes tools with RUBE_MULTI_EXECUTE_TOOLProvides setup instructions for Rube MCPOffers a core workflow pattern for tool executionHighlights common pitfalls and solutions

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedBolt Iot Automation via Rube MCP

Automate Bolt Iot operations through Composio's Bolt Iot toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/bolt_iot

Prerequisites

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

Step 2: Check Connection

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

Automate Bolt Iot operations through Composio's Bolt Iot toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/bolt_iot