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.

DimensionHevy MCP ServerManage workouts, routines, and exercise data through the Hevy APIBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS66 / 100 · C75 / 100 · B
Reliability9 / 2010 / 20
Security and permissions14 / 2016 / 20
Maintenance12 / 2018 / 20
Documentation17 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Hevy PRO users
  • Fitness enthusiasts who want AI-assisted training analysis and planning
  • Developers who want to integrate Hevy data into MCP clients like Claude Desktop, Codex, Cursor
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users without Hevy PRO subscription
  • Users who need deletion capabilities (Hevy API does not expose delete endpoints)
  • Users looking for official support (this is community-maintained, not affiliated with Hevy)
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • Requires Hevy API key (`HEVY_API_KEY`)
  • Can read and write Hevy data (workouts, routines, exercise templates, body measurements, etc.)
  • Hosted endpoint validates the API key with Hevy on each request and forwards it as `api-key` header
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • API key leakage risk: never put key in source control, URLs, logs, or screenshots.
  • Mutation risk: create operations may produce duplicates on retry; update operations replace existing records.
  • Privacy: local package enables telemetry by default (can be disabled), sending errors and metrics to external services.
  • Dependency on third-party service: hosted endpoint relies on Cloudflare Worker, availability may vary.
  • Tool confirmation: mutation tools may require client confirmation, but support varies by client.
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude Desktop, Codex, Cursor, AntigravityClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools2611