Betsapi vs Hevy MCP Server
A side-by-side look at the Betsapi 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 Betsapi 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 Betsapi 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 want tools like
betsapi_inplay, betsapi_upcoming, betsapi_event_odds.
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 | 55/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | BYOK (pay the provider) |
| Required env vars | None listed | HEVY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 518 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 3 | 4 |
| Full listing | View Betsapi | View Hevy MCP Server |
Tools & capabilities
Betsapi tools 3
betsapi_inplayLive in-play sport matches happening right now, with running score and match clock. Pass a sport_id (${SPORT_IDS}). Example: betsapi_inplay({ sport_id: "1", _apiKey: "your-key" })betsapi_upcomingUpcoming (scheduled) sport events for a sport, optionally for a given day. Pass a sport_id (${SPORT_IDS}) and optionally day=YYYYMMDD. Example: betsapi_upcoming({ sport_id: "1", day: "20260704", _apiKey: "your-key" })betsapi_event_oddsBookmaker odds for a single event across markets (moneyline, spreads, totals). Odds are deeply nested by market, so the full structure is returned under `raw`. Get an event_id from betsapi_inplay or betsapi_upcoming first. Example: betsapi_event_odds({ event_id: "12345678", _apiKey: "your-key" })
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.
Betsapi
{
"mcpServers": {
"betsapi": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-betsapi"
]
}
}
}
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
Betsapi is categorized under Sports and uses a local stdio subprocess. Hevy MCP Server belongs to Sports and uses a local stdio subprocess. Pick Betsapi 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.
Betsapi is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 betsapi and hevy-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Betsapi has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Hevy MCP Server has 65/100 (Great) with 3 views, 0 installs and 518 GitHub stars.