Bring Activity Tracking
to Claude Desktop
Learn how to connect Strava to Claude Desktop and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Strava MCP Server?
Connect your Strava account to any AI agent to automate your athletic performance tracking and activity orchestration. Strava provides a premier platform for athletes to track their progress, and this integration allows you to retrieve activity metadata, monitor athlete statistics, and explore routes through natural conversation.
What you can do
- Activity & Workout Orchestration — List all your athletic activities and retrieve detailed metadata, including distance, heart rate, and elevation programmatically.
- Athlete Performance Monitoring — Access and monitor your athlete statistics and profile metadata to track your progress over time directly from the AI interface.
- Route & Segment Intelligence — List available routes and starred segments to ensure your training paths are always synchronized via natural language.
- Club & Social Insight — Access and monitor the clubs you belong to to maintain a clear overview of your athletic community engagement.
- Data Management — Create and update activities programmatically to ensure your training log is always current and accurate using simple AI commands.
How it works
1. Subscribe to this server
2. Enter your Strava Access Token (OAuth2) from your developer settings
3. Start managing your athletic data from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Athletes & Fitness Enthusiasts — quickly retrieve recent workout details and monitor performance stats without switching apps.
- Coaches & Trainers — automate the retrieval of athlete activity logs and monitor training progress via natural conversation.
- Data Analysts — streamline the retrieval of workout metadata and monitor segment performance directly within the chat.
Built-in capabilities (12)
Add manual workout
Get activity info
Get your info
Check totals
Get route info
Get segment info
List your activities
List joined clubs
List your routes
List favorite segments
Update workout info
Verify API key
Why Claude Desktop?
Claude Desktop is the definitive way to connect Strava to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Strava in Claude Desktop
Strava and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Strava to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Strava in Claude Desktop
The Strava 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. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
Strava for Claude Desktop
Every tool call from Claude Desktop to the Strava MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Strava Access Token?
Log in to Strava Developers, create an API application, and you will find your Access Token in the settings. Note that you may need to use the OAuth flow to generate a long-lived or refreshed token.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
