Skip to main content
Glama
ansonyuu

MyFitnessPal MCP Server

by ansonyuu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
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

      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

    • Dieta.ai

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables nutrition tracking via AI, allowing users to read food logs with macros, goals, and profile, log meals by text or photo, and access diary, subscription, diabetes, and wearable/glucose data.
      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.8/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools are clearly distinct: search_food and get_food_details relate to the food database, while get_diary and get_nutrition_summary relate to daily records. There is minor overlap between get_diary and get_nutrition_summary since both expose calorie/macro totals, but their descriptions clarify the different levels of detail.

    Naming Consistency5/5

    Tool names follow a consistent snake_case verb_noun pattern: get_diary, get_goals, search_food, add_food, quick_add_calories. The naming style is uniform and predictable across all seven tools.

    Tool Count5/5

    Seven tools is a well-scoped size for a nutrition diary server. Each tool covers a meaningful part of the workflow—viewing data, searching foods, and logging entries—without unnecessary redundancy.

    Completeness3/5

    The server covers core read and add workflows: viewing diary data, searching foods, getting details, and adding entries. However, it lacks update and delete operations for diary entries, which is a notable gap when correcting mistakes or modifying logged food.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources