M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionHass MCP ServerControl and query Home Assistant from Claude and other LLMs — a Model Context Protocol (MCP) server.Hevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS52 / 100 · D77 / 100 · B
Reliability7 / 2012 / 20
Security and permissions10 / 2016 / 20
Maintenance7 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Home Assistant users who want natural language control of their smart home
  • Developers who enjoy using AI assistants like Claude
  • Users who need quick troubleshooting of automations and entities
  • 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 who do not need AI control
  • Those who cannot manage long-lived tokens or network configuration
  • Those who need offline or fully local environments without exposing server ports (especially in HTTP mode)
  • 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
  • Requires a Home Assistant Long-Lived Access Token (HA_TOKEN)
  • Needs network access to the Home Assistant instance via HA_URL
  • In HTTP mode, opens a port that must be protected via proxy or VPN to prevent unauthorized access
  • 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
  • If HTTP mode is exposed to the public internet, anyone can control all smart devices (lights, locks, automations, restart HA)
  • Token leakage could lead to full control of Home Assistant
  • Wrong operations could cause device anomalies or unintended automations
  • 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, Cursor, Claude CodeClaude Desktop, Cursor, Codex, Antigravity
Tools1526