Beaconstac Automation

What This Skill Does

This skill automates Beaconstac operations using the Composio Beaconstac toolkit via Rube MCP. It's designed for users who need to programmatically manage Beaconstac, emphasizing proper setup and workflow. The skill focuses on tool discovery and connection management for reliable automation.

When to Use

• Automate beacon deployment and management.
• Trigger actions based on beacon proximity.
• Schedule routine Beaconstac tasks.
• Integrate Beaconstac data with other systems.
• Manage user access to beacons.

Key Features

• Uses Rube MCP for Beaconstac automation.
• Requires an active Beaconstac connection.
• Employs RUBE_SEARCH_TOOLS for tool discovery.
• Provides a core workflow pattern for execution.
• Highlights known pitfalls for robust automation.

Beaconstac Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/beaconstac

Prerequisites

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

Step 2: Check Connection

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

Beaconstac Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/beaconstac

Quick Reference