Openf1 vs Strava MCP
A side-by-side look at the Openf1 and Strava MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Openf1 for sports work as a local process; choose Strava MCP for sports as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Openf1 when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_meetings, get_sessions, get_drivers.
Choose Strava MCP when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
get-athlete-profile, get-athlete-stats, get-activity-details.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Sports | Sports |
| Quality signal | 52/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 500 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 4 | 24 |
| Full listing | View Openf1 | View Strava MCP |
Tools & capabilities
Openf1 tools 4
get_meetingsList Formula 1 meetings (Grand Prix weekends). Live race data source. Filter by year and/or country. Returns meeting_key, official name, country, circuit, location, date.get_sessionsList F1 sessions (a Race, Qualifying, or Practice within a Grand Prix weekend). Use to find the session_key needed for drivers/laps. Filter by year, country, session_name ("Race","Qualifying","Practice 1"), or meeting_key.get_driversList F1 drivers entered in a session (live race data): number, full name, 3-letter acronym, team, team colour, country, headshot. session_key="latest" for the most recent / ongoing session.get_lapsLap times / telemetry for an F1 session: per-lap duration, sector times, speed-trap, pit-out flag. Live race data. session_key="latest" for the most recent / ongoing session. Optionally filter by driver_number or lap_number.
Strava MCP tools 24
get-athlete-profileFetches the profile information for the authenticated athlete, including their unique numeric ID needed for other tools like get-athlete-stats.get-athlete-statsFetches the activity statistics (recent, YTD, all-time) for a specific athlete using their ID. Requires the athleteId obtained from the get-athlete-profile tool.get-activity-detailsFetches detailed information about a specific activity using its ID.get-recent-activitiesFetches the most recent activities for the authenticated athlete.list-athlete-clubsLists the clubs the authenticated athlete is a member of.list-starred-segmentsLists the segments starred by the authenticated athlete.get-segmentFetches detailed information about a specific segment using its ID.explore-segmentsSearches for popular segments within a given geographical area.star-segmentStars or unstars a specific segment for the authenticated athlete.get-segment-effortFetches detailed information about a specific segment effort using its ID.list-segment-effortsLists the authenticated athlete's efforts on a specific segment, optionally filtering by date.list-athlete-routesLists the routes created by the authenticated athlete, with pagination.- +12 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Openf1
{
"mcpServers": {
"openf1": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-openf1"
]
}
}
}
Strava MCP
{
"mcpServers": {
"r-huijts-strava-mcp": {
"command": "npx",
"args": [
"-y",
"@r-huijts/strava-mcp-server"
]
}
}
}
Frequently asked questions
Openf1 is categorized under Sports and uses a local stdio subprocess. Strava MCP belongs to Sports and uses a local stdio subprocess. Pick Openf1 for sports work and Strava MCP for sports.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Openf1 has no declared pricing — check the project's own site. Strava MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add openf1 and r-huijts-strava-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Openf1 has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Strava MCP has 67/100 (Great) with 2 views, 0 installs and 500 GitHub stars.