| FMRS | 44 / 100 · D | 77 / 100 · B |
|---|
| Reliability | 3 / 20 | 12 / 20 |
|---|
| Security and permissions | 10 / 20 | 16 / 20 |
|---|
| Maintenance | 10 / 20 | 16 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 |
|---|
| Setup experience | 8 / 20 | 15 / 20 |
|---|
| Best for | - Users who want the control loop and state kept on their device
- Users with llama.cpp, Ollama, LM Studio, or another OpenAI-compatible model backend
- Developers needing browser, filesystem, document, and task automation
- Technical users willing to review approvals, traces, and network egress
| - 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 | - Users looking for a standalone MCP server that can be installed directly into an MCP client
- Production integrations requiring stable APIs, because the project is still a developer preview
- Environments that cannot allow agent access to browsers, files, shells, or networks
- Systems without Node.js, Chromium, git, or an accessible model backend
| - 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 write access to the local state directory and SQLite databases
- Permission to run approved shell commands and perform some process operations
- Access to the configured Chromium browser, browser profile, and websites
- Network access to configured llama-server, cloud models, search providers, or HTTP endpoints
- Permissions required by external MCP servers whose tools are invoked
- Optional macOS Accessibility, Screen Recording, Automation, or Reminders permissions
| - 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 | - Browser navigation, HTTP tools, cloud models, search providers, MCP, Telegram, update checks, and analytics can create network egress
- Shell commands and skills inherit the agent process environment and may access `.env` secrets
- Traces and `.env` under the state directory should be treated as sensitive; the project says redaction and environment filtering are not complete isolation
- Filesystem writes, patches, archive extraction, process termination, HTTP requests, and untrusted MCP tools are policy-gated, but approval errors can still cause harm
- The project is a developer preview, so commands, configuration, and behavior may change
| - 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 Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 0 | 26 |
|---|