Bring Activity Tracking
to LlamaIndex
Learn how to connect Strava to LlamaIndex 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 LlamaIndex?
LlamaIndex agents combine Strava tool responses with indexed documents for comprehensive, grounded answers. Connect 12 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Strava tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Strava tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Strava, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Strava tools were called, what data was returned, and how it influenced the final answer
Strava in LlamaIndex
Strava and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Strava to LlamaIndex 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 LlamaIndex
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 LlamaIndex 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 LlamaIndex
Every tool call from LlamaIndex 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 LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Strava tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp