| FMRS | 66 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 11 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 12 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 13 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - macOS users with OmniFocus who want to drive their task database in natural language
- OmniFocus users who need an AI assistant to bulk-organize and reorganize tasks
- Users comfortable granting macOS automation access and troubleshooting AppleEvent timeouts
| - 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 | - Windows or Linux users, since the server depends on OmniFocus on macOS
- Users whose environment cannot grant macOS automation permissions
- Users expecting official Omni Group support, as this is a third-party open-source project
| - 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 macOS Automation (AppleEvents) access to control OmniFocus
- Reads and writes the local OmniFocus database through osascript
- The shared daemon listens on a 0700-permission Unix domain socket under ~/.omnifocus-mcp/; access is enforced by the filesystem, with no network port and no token
| - 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 | - Once automation access is granted, the server can read and modify the local OmniFocus database, including removing tasks and projects; removals may warrant care.
- Editing or removing completed past occurrences of repeating items cascades through the live repeat chain and is refused by default unless explicitly allowed.
- If the shared daemon crashes or is killed, attached clients can be affected; newer versions reconnect and replay the initialize handshake.
- Right after an upgrade two daemons may briefly coexist, with clients attached to the old one receiving an in-band upgrade notice in tool results.
- Too many concurrent osascript calls can cause AppleEvent timeouts.
| - 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, Claude Code | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 12 | 26 | 11 |
|---|