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.

DimensionMCPHubUnified hub for centrally managing multiple MCP serversHevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS42 / 100 · D77 / 100 · B
Reliability7 / 2012 / 20
Security and permissions8 / 2016 / 20
Maintenance10 / 2016 / 20
Documentation9 / 2018 / 20
Setup experience8 / 2015 / 20
Best for
  • Development teams needing centralized management of multiple MCP servers
  • Organizations exposing various MCP servers to AI clients via a unified API
  • Production deployments requiring high availability and scalability
  • Solo developers wanting to quickly experiment with various MCP servers
  • 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 scenarios requiring only a single MCP server
  • Users with strict customization needs for a specific MCP server
  • Environments where running without authentication is unacceptable (high security requirements)
  • 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
  • Access to MCP server configuration files and local data directory
  • Ability to execute commands like npx and uvx to start MCP servers
  • Network access to communicate with MCP servers
  • Optional: PostgreSQL database connection for database mode
  • 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
  • MCP endpoints require authentication by default; unauthenticated access may expose servers
  • Hot-swappable configuration could lead to configuration errors causing service unavailability
  • Running many MCP servers may consume significant system resources
  • Admin password and API keys need careful management
  • 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, CursorClaude Desktop, Cursor, Codex, Antigravity
Tools026