| FMRS | 51 / 100 · D | 77 / 100 · B |
|---|
| Reliability | 7 / 20 | 12 / 20 |
|---|
| Security and permissions | 10 / 20 | 16 / 20 |
|---|
| Maintenance | 13 / 20 | 16 / 20 |
|---|
| Documentation | 11 / 20 | 18 / 20 |
|---|
| Setup experience | 10 / 20 | 15 / 20 |
|---|
| Best for | - Data teams with an OpenMetadata deployment
- AI assistants and agents that need governed data context
- Organizations performing discovery across semantics, lineage, quality, policies, and business terms
| - 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 without an OpenMetadata deployment
- Use cases that only require direct access to a raw database or files
- Browser automation, cloud storage, or general collaboration workflows
| - 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 | - Access to the target OpenMetadata deployment's /mcp endpoint is required
- Authentication is required through OAuth 2.0 with PKCE and the existing SSO provider, or through Basic Auth
- The available metadata and data-quality operations are controlled by OpenMetadata authentication, authorization, roles, and policies
| - 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 | - The connection may expose permission-controlled metadata, lineage, quality, policy, and memory content from the deployment
- Accounts with write permissions may update descriptions, tags, owners, and other metadata, or create glossary terms, lineage, and quality tests
- Semantic-search results or memories may contain internal organizational knowledge and should be governed accordingly
| - 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 |
|---|