| 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 | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 |
|---|
| Best for | - Developers and managers who want to consolidate multiple data sources into a searchable knowledge base.
- Teams that need to extract information from unstructured documents for LLM-powered applications.
- Users already using the Graphlit platform or interested in trying it.
| - 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 who only need simple web search or do not require data persistence.
- Users who need local storage or open-source solutions, as Graphlit is a hosted cloud platform.
- Users requiring fully offline or private deployment.
| - 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 | - Requires Graphlit Environment ID, Organization ID, and JWT secret for authentication.
- Optional: Data connector tokens such as Slack Bot Token, Discord Bot Token, Google OAuth credentials, etc., to access external services.
- MCP clients need to execute npx commands, requiring network access and a Node.js environment.
| - 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 | - Data security: Connectors access external services; ensure permissions are scoped minimally.
- Cost: Graphlit is a paid service; improper use may incur charges.
- Credential leakage: Environment variables contain sensitive info; guard them carefully, especially in shared configs.
- Third-party dependencies: The server is fetched via npx, introducing potential supply chain risks.
| - 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, Windsurf, Goose, Cline | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 59 | 26 |
|---|