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.

DimensionUniFi Access MCPManage UniFi Access through MCP.Hevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS61 / 100 · C77 / 100 · B
Reliability9 / 2012 / 20
Security and permissions14 / 2016 / 20
Maintenance13 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Home-automation or small-organization administrators using UniFi Access.
  • Users who need AI-assisted access to a local UniFi Access controller.
  • Deployments able to maintain a local UniFi administrator or service account.
  • 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 only have a Ubiquiti SSO cloud account and cannot provide a local controller account.
  • Users needing Network or Protect functionality; those are separate servers in the repository.
  • Environments where AI workflows must not access door, credential, or visitor data.
  • 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 the UniFi controller IP address or hostname.
  • Requires a local UniFi administrator or service-account username and password.
  • The account should have permissions for the required access-management operations.
  • A UniFi API key may be used optionally; the source labels it experimental.
  • 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
  • Door, credential, and visitor operations can affect real physical access.
  • Controller credentials and API keys are sensitive and must be protected.
  • UNIFI_VERIFY_SSL defaults to false, which can reduce TLS certificate-validation protection.
  • Incorrect permissions or requests may cause unintended access-configuration changes.
  • 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, Codex, OpenClawClaude Desktop, Cursor, Codex, Antigravity
Tools026