M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionGarmin MCP ServerMCP server for accessing Garmin data, with 110+ tools covering fitness, health, and training analytics.Hevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS72 / 100 · B77 / 100 · B
Reliability11 / 2012 / 20
Security and permissions14 / 2016 / 20
Maintenance16 / 2016 / 20
Documentation17 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Garmin users wanting to centralize fitness data in AI assistants
  • Runners or cyclists needing automated workout generation and scheduling
  • Analytical users who prefer natural language queries for health trends
  • Developers and hobbyists integrating Garmin data into custom toolchains
  • Hevy PRO users who want AI assistants to directly access their workout data
  • People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
  • Anyone needing summaries and insights from their training data
Not for
  • Non-Garmin users or those without a Garmin account
  • Applications requiring real-time GPS tracking or instant data push
  • Users who want to bypass authentication (requires Garmin account and OAuth tokens)
  • Destructive operations like deleting activities (not implemented for safety)
  • Users without a Hevy PRO subscription (API key required)
  • Users who want to use the server without an API key
  • Those needing delete workflows (Hevy API does not expose delete endpoints)
Required permissions
  • Read and edit Garmin Connect data (activities, health metrics, workouts, etc.)
  • Download activity files to local directory
  • Create and schedule workout plans
  • Access user's health metrics and body composition data
  • Requires HEVY_API_KEY environment variable for Hevy API authentication
  • Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
  • Read operations can fetch workouts, routines, folders, templates, history, and user info
Risks and side effects
  • Stores OAuth tokens which expire after ~6 months, requiring re-authentication
  • HTTP transport has no authentication; if exposed on public network, place behind a reverse proxy
  • Some destructive operations (e.g., delete activity) are intentionally not implemented to avoid accidents
  • Many tools may increase LLM context overhead, but can be filtered via environment variables
  • API key can be misused if leaked; do not expose in URLs, logs, or screenshots
  • Create operations may produce duplicates on retry; update operations replace existing records
  • The server sends data to the Hevy API and may send telemetry to external services unless disabled
Supported clientsClaude Desktop, Codex, OpenCodeClaude Desktop, Cursor, Codex, Antigravity
Tools026