Musette MCP vs Hevy MCP Server
A side-by-side look at the Musette MCP 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 Musette MCP for sports work over a hosted endpoint; 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 Musette MCP when
- You need dedicated capabilities in the Sports domain.
- You prefer a remote HTTP/SSE transport.
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 | 36/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | 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 | Not listed | 4 |
| Full listing | View Musette MCP | View Hevy MCP Server |
Tools & capabilities
Musette MCP tools
No tool names declared yet. Check the project README from the listing page.
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.
Musette MCP
{
"mcpServers": {
"musette-mcp": {
"url": "https://www.musette.cc/mcp"
}
}
}
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
Musette MCP is categorized under Sports and uses a remote HTTP/SSE transport. Hevy MCP Server belongs to Sports and uses a local stdio subprocess. Pick Musette MCP 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.
Musette MCP 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 musette-mcp and hevy-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Musette MCP has a quality signal of 36/100 (Fair) 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.