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.

DimensionAccess MCP ServerManage internal access through MCP.Hevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS63 / 100 · C77 / 100 · B
Reliability9 / 2012 / 20
Security and permissions15 / 2016 / 20
Maintenance11 / 2016 / 20
Documentation16 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Organizations that need centralized visibility into Okta-related internal access.
  • Teams that want MCP clients to assist with permission discovery and pending request submission.
  • Operators able to configure Cloudflare Access or OIDC for an Access deployment.
  • 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
  • Workflows requiring MCP to approve or reject requests.
  • Workflows requiring direct MCP mutation of groups, roles, or apps.
  • Users without an Access deployment, Okta data, or a supported authentication setup.
  • 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
  • Access to the Okta API is required; development setup calls for Group Admin and Application Admin roles plus group-management permissions.
  • Production deployments require Cloudflare Access or OIDC authentication.
  • MCP tools require read_all or create_requests scopes, while Access authorization rules still apply to each operation.
  • 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
  • A misconfigured Okta API token may grant excessive group or application administration privileges.
  • Tokens without an explicit scope receive read_all and create_requests by default; operators can configure read-only or fail-closed behavior.
  • Enabling MCP allows authenticated clients to read access data and submit pending requests.
  • Incorrect proxy Host or OIDC callback configuration can create redirect-URI risks; the source recommends ALLOWED_HOSTS and OIDC_OVERWRITE_REDIRECT_URI.
  • 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 Code, Claude.ai, Cursor, Zed, Self-hosted modelsClaude Desktop, Cursor, Codex, Antigravity
Tools326