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 dataBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS51 / 100 · D75 / 100 · B
Reliability9 / 2010 / 20
Security and permissions8 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience10 / 2014 / 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
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
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 needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
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 internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
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
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude DesktopClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools2011