| FMRS | 66 / 100 · C | 77 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 13 / 20 | 16 / 20 |
|---|
| Maintenance | 16 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - Personal knowledge management that requires actual answers beyond search (synthesis + gap analysis)
- Teams wanting to build shared institutional memory (with OAuth scoping)
- AI agents needing persistent memory (automatic ingestion, enrichment, consolidation)
| - 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 | - Scenarios requiring real-time data streams (depends on scheduled syncs and crawling)
- Users without API keys or willing to configure an embedding provider (requires at least one)
- Users wanting a fully managed cloud service (requires self-hosting)
| - 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/write access to local filesystem (for brain repo and imports)
- Network access to external APIs (unlocks embedding providers, LLMs, ingestion webhooks)
- Environment variable access for API keys (e.g., OPENAI_API_KEY, etc.)
- Local database (PGLite or Postgres)
| - 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 | - Package confusion: the 'gbrain' package on npm is unrelated and may cause conflicts; install only from GitHub
- Data privacy: local data is secure, but remote deployments must secure OAuth tokens and API keys
- LLM costs: 'think' and synthesis features consume LLM API calls, incurring expenses
- Performance issues: large brain syncs may take time or stall (troubleshooting provided)
| - 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, Claude Code, Codex, Cursor, Windsurf, Perplexity, ChatGPT, Claude Cowork | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 10 | 26 |
|---|