Bring Activity Tracking
to CrewAI
Learn how to connect Strava to CrewAI 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 CrewAI?
When paired with CrewAI, Strava becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Strava tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Strava in CrewAI
Strava and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Strava to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.