sms-alert-automation

SMS Alert Automation - Automate SMS Reminders via Rube MCP

Skill Overview

SMS Alert Automation is a Claude skill that automates SMS reminder operations using Rube MCP and Composio's SMS Alert toolkit. It provides dynamic tool discovery, connection management, and batch execution capabilities.

Use Cases

SMS integration without API keys

- Simply add https://rube.app/mcp as the MCP server in the client configuration to start using SMS Alert features—no need to pre-apply for an API key or set up complex authentication.

Dynamic tool discovery and architecture adaptation

- The tool architecture may change. This skill uses RUBE_SEARCH_TOOLS in real time to fetch the current list of available tools, input schemas, and recommended execution plans, avoiding hard-coded, outdated tool parameters.

Batch SMS operations and session management

- Supports RUBE_MULTI_EXECUTE_TOOL to batch execute multiple SMS Alert operations. It reuses connection state via session IDs, suitable for scenarios requiring sending multiple SMS messages in sequence or running complex workflows.

Core Features

Tool discovery and architecture retrieval

- Uses RUBE_SEARCH_TOOLS to query tools related to specific SMS Alert tasks, returning available tool identifiers, input schemas, recommended execution plans, and known pitfalls—ensuring each call uses the latest architecture definitions.

Connection status management

- Uses RUBE_MANAGE_CONNECTIONS to check and manage the SMS Alert toolkit connection status. Before executing any workflow, it verifies that the connection is in ACTIVE state. If it’s not activated, it returns an authentication link to complete setup.

Tool execution and session reuse

- Executes discovered tools via RUBE_MULTI_EXECUTE_TOOL, supporting schema-compatible parameter passing, empty memory object handling, and session ID reuse. The same session can be reused within a single workflow, while a new workflow generates a new session.

FAQs

Does Rube MCP require an API key?

No. Just add https://rube.app/mcp as the MCP server endpoint in the client configuration—no API key or pre-configuration is required. After adding the endpoint, use RUBE_SEARCH_TOOLS to verify availability and get started.

How do I check whether the SMS Alert connection is available?

Call RUBE_MANAGE_CONNECTIONS and specify the toolkit as sms_alert to check the returned connection status. If the status is not ACTIVE, complete the setup using the authentication link returned. Only execute the workflow after the status becomes ACTIVE.

Why must I call RUBE_SEARCH_TOOLS first?

The SMS Alert tool architecture and the list of available tools may change. Hard-coding tool identifiers or parameters can cause calls to fail. RUBE_SEARCH_TOOLS returns the latest tool architecture, recommended execution plans, and known pitfalls to ensure your calls remain compatible.