| FMRS | 55 / 100 · C | 77 / 100 · B |
|---|
| Reliability | 6 / 20 | 12 / 20 |
|---|
| Security and permissions | 11 / 20 | 16 / 20 |
|---|
| Maintenance | 9 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - Users who use Anki for spaced repetition and want to leverage AI to automate study workflows
- Advanced users who need to manage cards, notes, and tags in bulk
- Developers who want to integrate Anki data into AI workflows
| - 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 | - Casual users who don't need AI interaction and only want basic Anki features
- Users uncomfortable with technical configuration who want plug-and-play
- Users needing official support or enterprise-grade security guarantees
| - 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 modify Anki collection data (cards, notes, decks, tags)
- Perform sync operations, communicating with AnkiWeb
- Access and modify media files (import, delete)
- Perform UI operations in Anki interface (e.g., open dialogs, browse)
| - 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 | - Exposing via tunnel may increase unauthorized access risk, but built-in DNS-rebinding protection and optional API key mitigate it
- Destructive tools (like field deletion) are hidden by default, but users can enable them, potentially causing data loss
- Media file import has path traversal and SSRF risks, which are built-in validated, but loose configuration could lead to security issues
- Automatic sync may unexpectedly overwrite or modify collection; regular backups recommended
| - 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, OpenCode | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 41 | 26 |
|---|