← ClaudeAtlas

segment-automationlisted

Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.
aiskillstore/marketplace · ★ 334 · AI & Automation · score 83
Install: claude install-skill aiskillstore/marketplace
# Segment Automation via Rube MCP Automate Segment customer data platform operations through Composio's Segment toolkit via Rube MCP. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Segment connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `segment` - 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. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `segment` 3. If connection is not ACTIVE, follow the returned auth link to complete Segment authentication 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. Track Events **When to use**: User wants to send event data to Segment for downstream destinations **Tool sequence**: 1. `SEGMENT_TRACK` - Send a single track event [Required] **Key parameters**: - `userId`: User identifier (required if no `anonymousId`) - `anonymousId`: Anonymous identifier (required if no `userId`) - `event`: Event name (e.g., 'Order Completed', 'Button Clicked') - `properties`: Object with event-specific properties - `timestamp`: ISO 8601 timestamp (optional; defaults to server time) - `context`: Object with contextual metadata (IP, user agent, etc.) **Pitfalls**: - At least one of `userId` or `anonymousId` is require