2,500+ MCP servers ready to use
Vinkius

Strava Planning MCP Server for Cursor 14 tools — connect in under 2 minutes

Built by Vinkius GDPR 14 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

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.

Cursor's Agent mode turns Strava Planning into an in-editor superpower. Ask Cursor to generate code using live data from Strava Planning and it fetches, processes, and writes. all in a single agentic loop. 14 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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 Cursor 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 Cursor via MCP

Follow these steps to integrate the Strava Planning MCP Server with Cursor.

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

03

Save the file

Cursor will automatically detect the new MCP server

04

Start using Strava Planning

Open Agent mode in chat and ask: "Using Strava Planning, help me...". 14 tools available

Why Use Cursor with the Strava Planning MCP Server

Cursor AI Code Editor provides unique advantages when paired with Strava Planning through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Strava Planning + Cursor Use Cases

Practical scenarios where Cursor combined with the Strava Planning MCP Server delivers measurable value.

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Strava Planning MCP Tools for Cursor (14)

These 14 tools become available when you connect Strava Planning to Cursor 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 Cursor

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

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

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Strava Planning + Cursor FAQ

Common questions about integrating Strava Planning MCP Server with Cursor.

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Connect Strava Planning to Cursor

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