What data streams are available for activities?

Available streams include: time, distance, latlng (GPS coordinates), altitude, velocity_smooth (speed), heartrate, cadence, watts (power), temp (temperature), moving (moving flag), and grade_smooth (incline %). Request specific streams with comma-separated types, e.g., "heartrate,watts,velocity_smooth". Not all streams are available for every activity — it depends on the recording device.

What are activity zones and how are they calculated?

Activity zones show the time spent in each heart rate zone (Z1-Z5) or power zone during an activity. Zones are based on the athlete's personal zone configuration (set in Strava settings). Zone analysis reveals training intensity — whether a workout was aerobic (Z1-Z2), threshold (Z3), or anaerobic (Z4-Z5). This data requires a heart rate monitor or power meter.

How do I find my athlete ID on Strava?

Your athlete ID is the numeric portion of your Strava profile URL. For example, from https://www.strava.com/athletes/12345678, your athlete ID is 12345678. You can also get it from the get_athlete tool in the Strava Planning or Strava Social MCP servers.

Strava Training MCP Server for LangChain 12 tools — connect in under 2 minutes

Name: Strava Training
Availability: InStock
Author: Vinkius

python.langchain.com/docs/integrations/tools/mcp

Built by Vinkius GDPR 12 Tools Framework

LangChain is the leading Python framework for composable LLM applications. Connect Strava Training through Vinkius and LangChain agents can call every tool natively. combine them with retrievers, memory, and output parsers for sophisticated AI pipelines.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

import asyncio
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain_openai import ChatOpenAI
from langgraph.prebuilt import create_react_agent

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with MultiServerMCPClient({
        "strava-training": {
            "transport": "streamable_http",
            "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
        }
    }) as client:
        tools = client.get_tools()
        agent = create_react_agent(
            ChatOpenAI(model="gpt-4o"),
            tools,
        )
        response = await agent.ainvoke({
            "messages": [{
                "role": "user",
                "content": "Using Strava Training, show me what tools are available.",
            }]
        })
        print(response["messages"][-1].content)

asyncio.run(main())

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Strava Training MCP Server

Connect Strava Training to any AI agent and unlock deep performance analysis from your Strava data — activity details, time-series streams, heart rate/power zones, segment efforts, lap splits, and lifetime athlete statistics.

LangChain's ecosystem of 500+ components combines seamlessly with Strava Training through native MCP adapters. Connect 12 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.

What you can do

Activity Details — Full metrics: distance, time, elevation, HR, power, speed, weather, gear
Activity Streams — Raw GPS, heart rate, power, cadence, altitude, speed, temperature, grade data
Activity Zones — Heart rate and power zone distribution for training intensity analysis
Activity Laps — Auto-split lap data with pace, distance, and elevation per split
Segment Efforts — Find, compare, and analyze all efforts on any segment with detailed metrics
Segment Streams — Elevation and grade profiles along segments for previewing difficulty
Segment Details — Distance, elevation, grade, effort count, and personal records
Athlete Statistics — Lifetime and recent totals for runs, rides, and all activities
Athlete Zones — Personal heart rate and power zone configurations
Gear Tracking — Equipment mileage, models, and primary gear assignments

The Strava Training MCP Server exposes 12 tools through the Vinkius. Connect it to LangChain in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Strava Training to LangChain via MCP

Follow these steps to integrate the Strava Training MCP Server with LangChain.

Install dependencies

Run pip install langchain langchain-mcp-adapters langgraph langchain-openai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Run the agent

Save the code and run python agent.py

Explore tools

The agent discovers 12 tools from Strava Training via MCP

Why Use LangChain with the Strava Training MCP Server

LangChain provides unique advantages when paired with Strava Training through the Model Context Protocol.

The largest ecosystem of integrations, chains, and agents. combine Strava Training MCP tools with 500+ LangChain components

Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step

LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging

Memory and conversation persistence let agents maintain context across Strava Training queries for multi-turn workflows

Strava Training + LangChain Use Cases

Practical scenarios where LangChain combined with the Strava Training MCP Server delivers measurable value.

RAG with live data: combine Strava Training tool results with vector store retrievals for answers grounded in both real-time and historical data

Autonomous research agents: LangChain agents query Strava Training, synthesize findings, and generate comprehensive research reports

Multi-tool orchestration: chain Strava Training tools with web scrapers, databases, and calculators in a single agent run

Production monitoring: use LangSmith to trace every Strava Training tool call, measure latency, and optimize your agent's performance

Strava Training MCP Tools for LangChain (12)

These 12 tools become available when you connect Strava Training to LangChain via MCP:

get_activity

The activityId is the numeric ID from Strava activity URLs (e.g., strava.com/activities/12345678 → 12345678). Use this for deep analysis of any workout, ride, or run. Get detailed information about a specific Strava activity

get_activity_laps

Each lap includes distance, moving time, average speed, elevation gain, and pace. GPS devices and Strava auto-split activities into laps (typically ~1km or ~1mi). Use this to analyze pace consistency, identify fast/slow sections, and compare splits within a single activity. Get lap/split data for a Strava activity

get_activity_streams

The "types" parameter is comma-separated stream types: "time", "distance", "latlng", "altitude", "velocity_smooth", "heartrate", "cadence", "watts", "temp", "moving", "grade_smooth". Example: "heartrate,watts,velocity_smooth" for HR, power, and speed data. Each stream returns an array of values with corresponding timestamps. Use this for detailed performance analysis, visualization, or export. Get raw time-series data streams from a Strava activity (GPS, heart rate, power, cadence, altitude, speed, etc)

get_activity_zones

Requires activity ID. This data helps understand training intensity and whether the workout targeted the correct zones. Only available for activities with heart rate or power data. Summit/subscription feature. Get heart rate and power zone distribution for a Strava activity

get_athlete_stats

Use the athlete's Strava numeric ID. Returns recent_run_totals, recent_ride_totals, all_run_totals, all_ride_totals. Great for performance overview and progress tracking. Get consolidated activity statistics for any Strava athlete

get_athlete_zones

Requires profile:read_all scope. Use this to understand training zones for zone-based analysis of activities and efforts. Get the authenticated athlete's custom heart rate and power zones

get_gear

The gear ID is found in activity data or athlete profile. Use this to track equipment mileage, plan maintenance, or analyze performance with specific gear. Get details about a piece of equipment (bike, shoes) tracked in Strava

get_segment

The segment ID is found in Strava segment URLs. Use this to discover segment characteristics before attempting it or to compare segments. Get details of a Strava segment including distance, elevation, grade, and leaderboards

get_segment_effort

Includes elapsed time, distance, average speed, heart rate, power, start date, and activity reference. The effort ID is found in segment effort listings or activity details. Use this to analyze specific KOM/QOM attempts and compare efforts on the same segment. Get details of a specific segment effort (KOM/QOM/PR attempt)

get_segment_effort_streams

Same format as activity streams but limited to the segment portion. The "types" parameter is comma-separated: "time", "distance", "latlng", "altitude", "velocity_smooth", "heartrate", "cadence", "watts". Use this for granular analysis of segment performance. Get time-series data streams for a specific segment effort

get_segment_streams

Useful for previewing a segment's difficulty profile before attempting it. The "types" parameter accepts "distance", "altitude", "grade_smooth". Use this to understand elevation changes and steepness patterns along a segment. Get time-series data streams for a Strava segment (elevation profile, grade, etc)

list_segment_efforts

Filter by athlete_id (required), optionally segment_id to get efforts on a specific segment, and date range with start_date_local and end_date_local (ISO 8601 format). Use this to find PRs, analyze progress on segments over time, or compare multiple efforts on the same segment. List all segment efforts for an athlete, optionally filtered by segment and date range

Example Prompts for Strava Training in LangChain

Ready-to-use prompts you can give your LangChain agent to start working with Strava Training immediately.

"Show my athlete statistics."

"Get activity streams for activity 12345678 with heart rate, power, and speed."

"Show my segment efforts on segment 22978."

Troubleshooting Strava Training MCP Server with LangChain

Common issues when connecting Strava Training to LangChain through the Vinkius, and how to resolve them.

MultiServerMCPClient not found

Install: pip install langchain-mcp-adapters

Strava Training + LangChain FAQ

Common questions about integrating Strava Training MCP Server with LangChain.

How does LangChain connect to MCP servers?

Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.

Which LangChain agent types work with MCP?

All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.