2,500+ MCP servers ready to use
Vinkius

Strava Planning MCP Server for OpenAI Agents SDK 14 tools — connect in under 2 minutes

Built by Vinkius GDPR 14 Tools SDK

The OpenAI Agents SDK enables production-grade agent workflows in Python. Connect Strava Planning through Vinkius and your agents gain typed, auto-discovered tools with built-in guardrails. no manual schema definitions required.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from agents import Agent, Runner
from agents.mcp import MCPServerStreamableHttp

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with MCPServerStreamableHttp(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ) as mcp_server:

        agent = Agent(
            name="Strava Planning Assistant",
            instructions=(
                "You help users interact with Strava Planning. "
                "You have access to 14 tools."
            ),
            mcp_servers=[mcp_server],
        )

        result = await Runner.run(
            agent, "List all available tools from Strava Planning"
        )
        print(result.final_output)

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.

The OpenAI Agents SDK auto-discovers all 14 tools from Strava Planning through native MCP integration. Build agents with built-in guardrails, tracing, and handoff patterns. chain multiple agents where one queries Strava Planning, another analyzes results, and a third generates reports, all orchestrated through Vinkius.

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 OpenAI Agents SDK 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 OpenAI Agents SDK via MCP

Follow these steps to integrate the Strava Planning MCP Server with OpenAI Agents SDK.

01

Install the SDK

Run pip install openai-agents in your Python environment

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

03

Run the script

Save the code above and run it: python agent.py

04

Explore tools

The agent will automatically discover 14 tools from Strava Planning

Why Use OpenAI Agents SDK with the Strava Planning MCP Server

OpenAI Agents SDK provides unique advantages when paired with Strava Planning through the Model Context Protocol.

01

Native MCP integration via `MCPServerSse`, pass the URL and the SDK auto-discovers all tools with full type safety

02

Built-in guardrails, tracing, and handoff patterns let you build production-grade agents without reinventing safety infrastructure

03

Lightweight and composable: chain multiple agents and MCP servers in a single pipeline with minimal boilerplate

04

First-party OpenAI support ensures optimal compatibility with GPT models for tool calling and structured output

Strava Planning + OpenAI Agents SDK Use Cases

Practical scenarios where OpenAI Agents SDK combined with the Strava Planning MCP Server delivers measurable value.

01

Automated workflows: build agents that query Strava Planning, process the data, and trigger follow-up actions autonomously

02

Multi-agent orchestration: create specialist agents. one queries Strava Planning, another analyzes results, a third generates reports

03

Data enrichment pipelines: stream data through Strava Planning tools and transform it with OpenAI models in a single async loop

04

Customer support bots: agents query Strava Planning to resolve tickets, look up records, and update statuses without human intervention

Strava Planning MCP Tools for OpenAI Agents SDK (14)

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

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

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

01

MCPServerStreamableHttp not found

Ensure you have the latest version: pip install --upgrade openai-agents
02

Agent not calling tools

Make sure your prompt explicitly references the task the tools can help with.

Strava Planning + OpenAI Agents SDK FAQ

Common questions about integrating Strava Planning MCP Server with OpenAI Agents SDK.

01

How does the OpenAI Agents SDK connect to MCP?

Use MCPServerSse(url=...) to create a server connection. The SDK auto-discovers all tools and makes them available to your agent with full type information.
02

Can I use multiple MCP servers in one agent?

Yes. Pass a list of MCPServerSse instances to the agent constructor. The agent can use tools from all connected servers within a single run.
03

Does the SDK support streaming responses?

Yes. The SDK supports SSE and Streamable HTTP transports, both of which work natively with Vinkius.

Connect Strava Planning to OpenAI Agents SDK

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