2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 14 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Strava Planning as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="strava_planning_agent",
            tools=tools,
            system_message=(
                "You help users with Strava Planning. "
                "14 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())
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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Strava Planning tools. Connect 14 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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

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

01

Install AutoGen

Run pip install "autogen-ext[mcp]"

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

04

Explore tools

The workbench discovers 14 tools from Strava Planning automatically

Why Use AutoGen with the Strava Planning MCP Server

AutoGen provides unique advantages when paired with Strava Planning through the Model Context Protocol.

01

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Strava Planning tools to solve complex tasks

02

Role-based architecture lets you assign Strava Planning tool access to specific agents. a data analyst queries while a reviewer validates

03

Human-in-the-loop support: agents can pause for human approval before executing sensitive Strava Planning tool calls

04

Code execution sandbox: AutoGen agents can write and run code that processes Strava Planning tool responses in an isolated environment

Strava Planning + AutoGen Use Cases

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

01

Collaborative analysis: one agent queries Strava Planning while another validates results and a third generates the final report

02

Automated review pipelines: a researcher agent fetches data from Strava Planning, a critic agent evaluates quality, and a writer produces the output

03

Interactive planning: agents negotiate task allocation using Strava Planning data to make informed decisions about resource distribution

04

Code generation with live data: an AutoGen coder agent writes scripts that process Strava Planning responses in a sandboxed execution environment

Strava Planning MCP Tools for AutoGen (14)

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

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

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

01

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Strava Planning + AutoGen FAQ

Common questions about integrating Strava Planning MCP Server with AutoGen.

01

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Strava Planning tools during their conversation turns.
02

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
03

Does AutoGen support human approval for tool calls?

Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.

Connect Strava Planning to AutoGen

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