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.

DimensionMyFitnessPal MCP ServerLet AI assistants read and write your MyFitnessPal diary and health dataHevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS51 / 100 · D77 / 100 · B
Reliability9 / 2012 / 20
Security and permissions8 / 2016 / 20
Maintenance10 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • Individuals who want to view and organize MyFitnessPal food, exercise and weight records in natural language
  • macOS Claude Desktop users who are comfortable authenticating with browser cookies
  • People automating entries (e.g. inferring fasts from a sleep window plus first-meal timestamp) or correcting logs programmatically
  • Technical users who accept a scraping-based approach and know the interface can break
  • 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
  • Production use requiring official support or a stable public API
  • Users unwilling to keep session cookies or account credentials on their machine
  • Environments on Python 3.13+ or where lxml cannot be built
  • MCP clients other than Claude Desktop (only a Claude Desktop config example is documented)
  • Anyone who needs to read fasting history — MFP exposes no read endpoint for it
  • 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 and modify your MyFitnessPal account data (diary, goals, measurements, water, fasting)
  • Write to ~/.mfp_mcp/cookies.json (mode 0600; equivalent to a password with full account access)
  • On macOS, read each browser's '<Browser> Safe Storage' keychain entry to decrypt its cookie database
  • Read browser cookies (Chromium-based or Firefox) or credentials from the MFP_USERNAME / MFP_PASSWORD environment variables
  • Optionally read MFP_SECRET_KEY from the environment or OS keychain to decrypt credentials
  • 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
  • The server can modify your diary, goals, measurements and water — mistaken calls change real data
  • Session cookies grant full account access and are stored locally in ~/.mfp_mcp/cookies.json; leaking that file is leaking the account
  • Storing plain credentials in the client config puts your MyFitnessPal password in plaintext on disk, readable by anything running as your user
  • Reads and writes depend on MFP's undocumented interfaces, which can change without notice (the author notes it already happened once)
  • Scraping and internal API use may conflict with MyFitnessPal's terms of service
  • If MFP_SECRET_KEY is stored alongside the encrypted values in the same config file, the encryption provides little protection
  • 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 DesktopClaude Desktop, Cursor, Codex, Antigravity
Tools2026