Skip to main content
Glama
delize

MyFitnessPal MCP Server

by delize
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to MyFitnessPal MCP Server

No user-submitted related servers found.

    Related Servers

    • mfp-mcp

      Mason-Levyy
      A
      license
      Not graded
      quality
      A
      maintenance
      Connect MyFitnessPal to Claude or any MCP client. Log meals, search food database with macros, track trends, and export nutrition history against your real MyFitnessPal diary.
      137 PyPI
      13
      MIT

    • MyFitnessPal MCP

      thesaaspreneur
      A
      license
      A
      quality
      C
      maintenance
      Enables reading and writing MyFitnessPal data—including food diary entries, custom foods, saved meals, recipes, exercise, measurements, water, and nutrition goals—through 33 MCP tools using your existing browser session for authentication.
      33
      MIT

    • MyFitnessPal MCP

      a1dancole
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to access your MyFitnessPal diary—foods, portions, meal and daily nutrition totals, water, exercise, steps, and weight—through a custom connector on web, desktop, and mobile.
      14 npm
      MIT

    • fitness-mcp

      ikeike443
      A
      license
      Not graded
      quality
      B
      maintenance
      A personal remote MCP server that lets Claude read your Hevy workout data and MacroFactor nutrition data directly in conversation, with read-only tools for workouts, body measurements, macros, and weight trends.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: read/write pairs (get_water/set_water, get_goals/set_goals) are unambiguous, and diary CRUD operations are well-separated. The closest overlap is among the four food-list tools (search, recent, frequent, my_foods) and between create_food and add_food_to_diary, but descriptions clarify the source and intent of each.

    Naming Consistency5/5

    All 18 tools follow a uniform mfp_ prefix with snake_case verb_noun naming (get_, set_, add_, update_, delete_, search_, create_). The verb-noun pattern is predictable and consistent throughout, making tool selection straightforward for agents.

    Tool Count4/5

    18 tools is slightly above the ideal 3-15 range, but the domain is broad: diary entries, food database, measurements, goals, water, exercises, and reports each justify several tools. The count feels earned rather than bloated, though it leans heavy.

    Completeness4/5

    Core nutrition workflows are complete: diary entries have full CRUD, goals and water have read/write pairs, measurements have set/get, and the food database supports search, details, and creation. Notable gaps are the lack of exercise logging (get_exercises has no set/add counterpart) and no edit/delete tools for custom foods despite create_food implying they can be deleted.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources