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.

DimensionOpenConnectorConnect once. Use everywhere.Hevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS52 / 100 · D77 / 100 · B
Reliability8 / 2012 / 20
Security and permissions10 / 2016 / 20
Maintenance10 / 2016 / 20
Documentation13 / 2018 / 20
Setup experience11 / 2015 / 20
Best for
  • Agent products that need access to many SaaS, developer, data, or communication services
  • Teams that need inspectable Action request and response contracts
  • Developers and teams that want control over credentials and runtime deployment
  • 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
  • Simple integrations that need only one service and no connector gateway
  • Users who require a documented list of specific MCP tool identifiers or client integrations
  • Users who do not want to manage credentials, deployment, or runtime configuration
  • 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
  • API keys, OAuth clients, and provider-specific scopes may need to be configured
  • The runtime may require connections, runtime tokens, and Action allow or block policies
  • Required permissions depend on the connected provider and executed Action
  • 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
  • Connected third-party accounts may let an agent access or modify user data
  • Incorrect scopes, Action policies, or runtime-token settings may broaden access
  • Credentials, transit files, and run logs must be protected in the deployment environment; logs support redaction but still require review
  • Third-party provider APIs, permissions, and availability can affect execution results
  • 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, Cursor, Codex, Antigravity
Tools026