| FMRS | 62 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 14 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 11 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Individual learners already using Anki and AnkiConnect.
- Users who want AI-guided review, explanations, and dynamic card creation.
- Users connecting local Anki to Claude Desktop, Cursor, Cline, or Zed.
| - 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
| - Scenarios needing clean, structured web context fed to an AI assistant
- Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
|
|---|
| Not for | - Users without the Anki desktop application or AnkiConnect.
- Organizations requiring official Anki support or an official integration.
- Remote users seeking only review workflows; GUI tools are intended for editing and creation, not review sessions.
| - 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)
| - Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
- Sites that explicitly disallow automated access (robots.txt)
|
|---|
| Required permissions | - Requires access to the configured AnkiConnect URL, which defaults to local http://localhost:8765.
- Write operations can create, modify, move, and delete Anki content; deletion tools require explicit confirmation.
- Media imports may read specified file paths or URLs, subject to media security settings.
- If AnkiWeb sync is enabled, the Anki application synchronizes directly with AnkiWeb.
| - 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
| - Requires a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
- firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
|
|---|
| Risks and side effects | - The project is explicitly in beta, and APIs and features may change.
- Deleting notes permanently removes associated cards; clearing tags, deleting media, and removing fields can also cause data loss.
- updateNoteFields may silently fail while the note is being viewed in Anki's browser.
- ngrok mode is unauthenticated, so anyone with the URL may reach Anki; the managed Tunnel requires login authentication.
- Remote HTTP exposure requires correct ALLOWED_HOSTS configuration; misconfiguration can cause rejected requests or broader exposure.
| - 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
| - Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
- firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
|
|---|
| Supported clients | Claude Desktop, Cursor IDE, Cline, Zed Editor | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 48 | 26 | 11 |
|---|