Garmin Connect Workouts MCP vs Hevy MCP Server

In-depth architectural comparison of the Garmin Connect Workouts MCP and Hevy MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Garmin Connect Workouts MCP when:

• You need dedicated capabilities in the Sports domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: create_garmin_workout, list_garmin_workouts, get_garmin_workout.

Explore Garmin Connect Workouts MCP Details

Choose Hevy MCP Server when:

• You need dedicated capabilities in the Sports domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Free / Open Source).
• You have access to required keys: HEVY_API_KEY.
• Primary tools included: user-profile, workout-count, exercise-templates.

Feature & Specification Comparison

Specification	Garmin Connect Workouts MCP Sports	Hevy MCP Server Sports
Summary	Turn plain language into real workouts on your Garmin watch: pace, HR, power, intervals, swim sets.	MCP server for managing workouts, routines, and exercise data through the Hevy API
Category & Scope	Sports	Sports

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "garmin-connect-workouts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "garmin-connect-workouts-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "hevy-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "hevy-mcp"
      ],
      "env": {
        "HEVY_API_KEY": "YOUR_HEVY_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons