Strava MCP vs Race Calendar F1

A side-by-side look at the Strava MCP and Race Calendar F1 MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Strava MCP logoStrava MCPSports · Local subprocess (stdio)A Model Context Protocol (MCP) server that connects to Strava API, providing tools to access Strava data through LLMs67GreatAuth: oauth 2.0
R
Race Calendar F1Sports
Anonymous read-only Formula 1 season schedule, standings, and race-weekend tools from Race Calendar.38FairAuth: not declared

Verdict: choose Strava MCP for sports work as a local process; choose Race Calendar F1 for sports. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Strava MCP logoChoose 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.
Explore Strava MCP

R
Choose Race Calendar F1 when

  • You need dedicated capabilities in the Sports domain.
Explore Race Calendar F1

Feature & specification comparison

Rows where the two servers differ are marked.

SpecStrava MCP logoStrava MCP
R
Race Calendar F1
CategorySportsSports
Quality signal67/100 · Great38/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthOAuth 2.0Not declared
PricingBYOK (pay the provider)Not declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars500—
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools24Not listed

Tools & capabilities

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

Race Calendar F1 tools

No tool names declared yet. Check the project README from 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.

Strava MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "r-huijts-strava-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@r-huijts/strava-mcp-server"
      ]
    }
  }
}

Race Calendar F1

No confirmed install command for Race Calendar F1 yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Strava MCP is categorized under Sports and uses a local stdio subprocess. Race Calendar F1 belongs to Sports and uses an install path we have not confirmed yet. Pick Strava MCP for sports work and Race Calendar F1 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. Race Calendar F1 has no confirmed install command yet — follow its own setup instructions.

Strava MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: oauth 2.0. Race Calendar F1 has no declared pricing — check the project's own site. 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 r-huijts-strava-mcp and race-calendar-f1 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Strava MCP has a quality signal of 67/100 (Great) with 2 views, 0 installs and 500 GitHub stars. Race Calendar F1 has 38/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.