2,500+ MCP servers ready to use
Vinkius

Strava Planning MCP Server for VS Code Copilot 14 tools — connect in under 2 minutes

Built by Vinkius GDPR 14 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.

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 Planning and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "strava-planning": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Strava Planning
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 Planning MCP Server

Connect Strava Planning to any AI agent and manage your training logistics — route creation, GPX/TCX export, manual activity logging, gear tracking, segment favoriting, and profile management.

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

What you can do

  • Route Management — List, view, and analyze all your saved routes with distance, elevation, and descriptions
  • Route Streams — Get GPS coordinates, elevation profiles, and distance data for any route
  • Route Export — Export routes to GPX and TCX formats for GPS devices (Garmin, Wahoo, etc.)
  • Manual Activity Creation — Log activities not recorded by Strava (gym, yoga, cross-training) with full details
  • Activity Updates — Edit activity names, descriptions, assign gear, mark commutes or indoor sessions
  • File Uploads — Upload FIT, TCX, or GPX files for processing by Strava with status tracking
  • Segment Management — Star (favorite) or unstar segments for quick training access
  • Athlete Profile — View and update your profile information including weight for accurate power-to-weight ratios
  • Athlete Zones — Review your heart rate and power zone configurations
  • Gear Details — Track equipment mileage, models, and primary gear assignments

The Strava Planning MCP Server exposes 14 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 Planning to VS Code Copilot via MCP

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

01

Create MCP config

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

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

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

04

Start using Strava Planning

Ask Copilot: "Using Strava Planning, help me...". 14 tools available

Why Use VS Code Copilot with the Strava Planning MCP Server

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

01

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

02

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

03

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

04

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

Strava Planning + VS Code Copilot Use Cases

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

01

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

02

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

03

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

04

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

Strava Planning MCP Tools for VS Code Copilot (14)

These 14 tools become available when you connect Strava Planning to VS Code Copilot via MCP:

01

create_activity

Required: name (activity name), type (activity type like "Run", "Ride", "Swim", "Walk", "Hike"), startDate (ISO 8601 format), elapsedTime (seconds). Optional: description, distance (meters). Use this to log activities recorded outside of Strava (gym workouts, yoga, cross-training, etc.). Activity types must match Strava's valid types list. Create a manual activity in Strava

02

export_route_gpx

GPX files can be downloaded and loaded onto GPS devices (Garmin, Wahoo, etc.) for navigation. The routeId is from Strava route URLs. Use this to export routes to your GPS device for guided training. Get the GPX export URL for a Strava route

03

export_route_tcx

TCX files include route data with additional training metadata. Compatible with Garmin Training Center and other fitness platforms. Use this to export routes with training metadata. Get the TCX export URL for a Strava route

04

get_athlete

Use this to review personal profile details, check equipment assignments, or verify account settings. Get the authenticated athlete's profile information

05

get_athlete_zones

Required for zone-based training analysis. Use this to review training zones, ensure zones are correctly set, or use zone data for activity analysis. Get the athlete's custom heart rate and power zones

06

get_gear

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

07

get_route

The routeId is found in Strava route URLs. Use this to review route characteristics before training or to plan similar routes. Get detailed information about a specific Strava route

08

get_route_streams

The "types" parameter is comma-separated: "latlng", "altitude", "distance". Use this to preview a route's elevation profile, understand the terrain, or export GPS data for navigation. Get elevation and GPS data streams for a Strava route

09

get_upload_status

Status values: "Your activity is ready" (success), "Your activity is still processing" (wait and retry), or error messages. The uploadId is returned by upload_activity. Poll this endpoint every 5-10 seconds after upload until ready. Check the status of a Strava activity upload

10

list_routes

Each route includes: name, distance, elevation gain, type (ride/run), description, and whether it's private. Use this to review saved routes, plan upcoming workouts, or export route data for GPS devices. List all routes created by the authenticated athlete

11

star_segment

Set starred=true to favorite, starred=false to unfavorite. The segmentId is from Strava segment URLs. Use this to manage your favorite segments for quick access and training focus. Star (favorite) or unstar a Strava segment

12

update_activity

The activityId is the numeric ID. Updatable fields: name, description, sport_type, gear_id (to assign equipment), commute (mark as commute: "true"/"false"), trainer (mark as indoor: "true"/"false"). Use this to correct activity details, assign gear, or add descriptions after the fact. Update an existing Strava activity

13

update_athlete

Currently only "weight" (in kg) is supported by the API. Accurate weight is important for power-to-weight ratio calculations and performance analysis. Use this when your weight changes to keep performance metrics accurate. Update the authenticated athlete's profile information

14

upload_activity

Supported data_type: "fit", "fit.gz", "tcx", "tcx.gz", "gpx", "gpx.gz". Returns an upload ID to check status with get_upload_status. Note: Actual file upload requires multipart/form-data with the file content. This endpoint initiates the process. Check upload status periodically — processing takes 10-60 seconds. Upload an activity file (FIT, TCX, GPX) to Strava for processing

Example Prompts for Strava Planning in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Strava Planning immediately.

01

"List all my saved routes."

02

"Export route 12345 to GPX format."

03

"Create a manual activity for today's gym session."

Troubleshooting Strava Planning MCP Server with VS Code Copilot

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

01

MCP tools not available

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

Strava Planning + VS Code Copilot FAQ

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

01

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.
02

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.
03

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.
04

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.

Connect Strava Planning to VS Code Copilot

Get your token, paste the configuration, and start using 14 tools in under 2 minutes. No API key management needed.