Openf1 vs Hevy MCP Server
A side-by-side look at the Openf1 and Hevy MCP Server 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 Hevy MCP Server 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 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Sports | Sports |
| Quality signal | 52/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | HEVY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 520 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 4 | 4 |
| Full listing | View Openf1 | View Hevy MCP Server |
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.
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.
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"
]
}
}
}
Hevy MCP Server
{
"mcpServers": {
"hevy-mcp-server": {
"command": "npx",
"args": [
"-y",
"hevy-mcp"
],
"env": {
"HEVY_API_KEY": "YOUR_HEVY_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Openf1 is categorized under Sports and uses a local stdio subprocess. Hevy MCP Server belongs to Sports and uses a local stdio subprocess. Pick Openf1 for sports work and Hevy MCP Server 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. Hevy MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 hevy-mcp-server 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. Hevy MCP Server has 65/100 (Great) with 3 views, 0 installs and 520 GitHub stars.