← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionHome Assistant MCPTalk to your house. Your AI assistant connected to Home Assistant via MCP. 50+ tools, three transports, one bunx command.Hevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS58 / 100 · C77 / 100 · B
Reliability8 / 2012 / 20
Security and permissions14 / 2016 / 20
Maintenance12 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • Users wanting deep AI integration with smart home
  • Privacy-conscious users needing local voice control
  • Developers looking for multiple deployment options (STDIO, HTTP, Docker)
  • Enthusiasts exploring AI-driven automation
  • 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 a Home Assistant instance
  • Enterprises requiring official vendor support (community-maintained)
  • Users extremely averse to any remote hosting (though local voice processing available)
  • Users needing only basic functionality (other simpler MCP servers may be more appropriate)
  • 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 Home Assistant entity states (lights, climate, media, etc.)
  • Control device states (on/off, brightness, temperature, etc.)
  • Access history data, logs, and configuration
  • Execute automations, scenes, and notifications
  • Manage dashboards and to-do lists
  • 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
  • Token leak: long-lived access token could be abused for unauthorized control.
  • Configuration errors may result in unintended actions (e.g., turning off critical safety devices).
  • HTTP/WS transport requires JWT auth, but misconfiguration could expose the service.
  • Voice features may introduce additional security risks (e.g., microphone access).
  • 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 clientsClaude Desktop, CursorClaude Desktop, Cursor, Codex, Antigravity
Tools8226