| FMRS | 63 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 11 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 15 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Home Assistant users who want AI-assisted configuration and maintenance
- Users who need automation debugging, history queries, and system-management capabilities
- Users running Home Assistant OS, Supervised, Container, or Core
| - 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 who only need voice-style control of devices already exposed to Assist
- People who do not use Home Assistant
- Users requiring the server to be an official Home Assistant product
| - 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 Home Assistant APIs and entity, service, and configuration capabilities
- Control, configuration changes, deletion, restart, and backup operations may require substantial privileges
- File and YAML tools require the custom component and beta feature flags
- Read-only mode, per-tool controls, and tool security policies can be enabled
| - 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 | - Write, delete, restart, restore, and YAML-editing operations can change or disrupt the smart-home configuration
- File and YAML tools are disabled by default; when enabled, restrict allowed paths and retain backups
- stdio has known connection issues; the custom component or HTTP methods are recommended for real setups
- Multiple installation entries for the same client can cause connection hangs
| - 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.ai, ChatGPT, Claude Code, Gemini CLI, Open WebUI, VSCode, Cursor | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 87 | 26 | 11 |
|---|