| FMRS | 46 / 100 · D | 77 / 100 · B |
|---|
| Reliability | 4 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 12 / 20 | 16 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 |
|---|
| Setup experience | 9 / 20 | 15 / 20 |
|---|
| Best for | - Users who need Claude Code, OpenClaw, Cursor, or Windsurf to access content across multiple platforms
- Individuals and developers seeking free or open-source upstream tools for web research
- Agent workflows that need centralized installation, diagnostics, and backend routing
| - 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 | - Tasks requiring graphical browser interaction, form submission, or automated login
- Deployments requiring a standalone MCP server or a documented MCP transport
- Environments that do not allow shell command execution by the agent
- Use cases requiring every platform to work without login state or cookies
| - 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 | - The agent must execute shell commands, including pip install, system dependency installation, and upstream CLI calls
- Some channels require local browser login state, cookies, or tokens
- Credentials are stored locally in ~/.agent-reach/config.yaml; the README states the file mode is 600
| - 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 | - Cookie- or login-state-based access to Twitter/X, Xiaohongshu, Reddit, and similar platforms may trigger detection, restrictions, or account bans
- The default installation may install Node.js, gh CLI, mcporter, and other system infrastructure, and modify agent skills and MCP configuration
- Platform anti-crawling changes or upstream tool changes may break individual channels
- Server deployments may require a proxy; the README estimates roughly $1 per month
| - 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 clients | Claude Code, OpenClaw, Cursor, Windsurf | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 0 | 26 |
|---|