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 VS Code Copilot 12 tools — connect in under 2 minutes

Name: Strava Training
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 12 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Strava Training and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "strava-training": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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.

GitHub Copilot Agent mode brings Strava Training data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Strava Training MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Strava Training

Ask Copilot: "Using Strava Training, help me...". 12 tools available

Why Use VS Code Copilot with the Strava Training MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Strava Training through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Strava Training + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Strava Training MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Strava Training MCP Tools for VS Code Copilot (12)

These 12 tools become available when you connect Strava Training to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

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

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Strava Training + VS Code Copilot FAQ

Common questions about integrating Strava Training MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.