Strava Automation

What This Skill Does

This skill automates interactions with the Strava API using Composio's toolkit and Rube MCP. It's designed for developers and fitness enthusiasts who want to programmatically access and manage Strava data. The skill simplifies tool discovery, connection management, and workflow execution.

When to Use

• Retrieve activity data for fitness analysis.
• Automate uploading activities to Strava.
• Monitor personal fitness progress.
• Integrate Strava data into custom dashboards.
• Create automated fitness challenges.
• Sync Strava data with other fitness platforms.

Key Features

• Discovers available Strava tools via Rube MCP.
• Manages Strava connections through Rube MCP.
• Executes Strava tools with schema validation.
• Provides a structured workflow for tool execution.
• Handles authentication and connection status checks.
• Offers error handling and schema compliance guidance.

Manual Installation

Strava Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/strava

Prerequisites

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

Step 2: Check Connection

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

Strava Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/strava

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Strava task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

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