Hevy MCP Server vs Race Calendar F1

A side-by-side look at the Hevy MCP Server 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.

Hevy MCP Server logoHevy MCP ServerSports · Local subprocess (stdio)MCP server for managing workouts, routines, and exercise data through the Hevy API65GreatAuth: api key required
R
Race Calendar F1Sports
Anonymous read-only Formula 1 season schedule, standings, and race-weekend tools from Race Calendar.38FairAuth: not declared

Verdict: choose Hevy MCP Server 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?

Hevy MCP Server logoChoose Hevy MCP Server when

  • You need dedicated capabilities in the Sports domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: HEVY_API_KEY.
  • You want tools like user-profile, workout-count, exercise-templates.
Explore Hevy MCP Server

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.

SpecHevy MCP Server logoHevy MCP Server
R
Race Calendar F1
CategorySportsSports
Quality signal65/100 · Great38/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthAPI key requiredNot declared
PricingBYOK (pay the provider)Not declared
Required env varsHEVY_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars520—
Directory activity 3 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools4Not listed

Tools & capabilities

Hevy MCP Server tools 4

  • user-profileAuthenticated Hevy user profile.
  • workout-countTotal number of workouts in the account.
  • exercise-templatesFull formatted exercise template catalog.
  • routine-foldersFull formatted list of Hevy routine folders.

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.

Hevy MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "hevy-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "hevy-mcp"
      ],
      "env": {
        "HEVY_API_KEY": "YOUR_HEVY_API_KEY_HERE"
      }
    }
  }
}

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

Hevy MCP Server 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 Hevy MCP Server 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.

Hevy MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 hevy-mcp-server and race-calendar-f1 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Hevy MCP Server has a quality signal of 65/100 (Great) with 3 views, 0 installs and 520 GitHub stars. Race Calendar F1 has 38/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.