Skip to main content
Glama
mfp-mcp-vercel

mfp-mcp-vercel

by michadasis

Related Servers

Alternatives to mfp-mcp-vercel

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude to manage MyFitnessPal food diaries, nutrition goals, exercises, body measurements, and water intake via a remote MCP server using session cookie authentication.
      19
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      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.
      9 npm
      MIT
    • A
      license
      A
      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.
      18
      620 PyPI
      31
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables Claude and other remote MCP clients to query your own read-only Garmin Connect data — recovery trends, sleep, HRV, Body Battery, stress, heart rate, and activities — through Garmin's official Personal API, with OAuth sign-in that works from the mobile apps as well as desktop. Deploys on Cloudflare Workers' free tier with no password sharing or scraping.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude to access selected read-only Garmin activity and step data plus MyFitnessPal diary data through one self-hosted authenticated endpoint.
      MIT

    TDQS

    A3.9/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools map to a distinct resource+action, making selection straightforward. The main risk is the cluster of food-collection readers (mfp_get_recent_foods, mfp_get_frequent_foods, mfp_get_my_foods) which share an identical input shape and are easy to confuse, though descriptions clarify the difference.

    Naming Consistency5/5

    Every tool follows a strict mfp_verb_noun pattern (get_diary, set_goals, add_food_to_diary, delete_food_entry, etc.), including the mfp_ prefix throughout. Verb choice is consistent (get/set/add/create/update/delete/search) and predictable.

    Tool Count4/5

    18 tools is on the high side but justified by a broad personal-tracking domain spanning diary, food database, measurements, goals, water, exercises, and reports. Each tool maps to a real operation, though the food-collection trio could be collapsed to reduce surface slightly.

    Completeness4/5

    Diary CRUD (get/add/update/delete) is fully covered and goals, water, and measurements have read+write pairs. Notable gaps remain: exercises are read-only (no logging tool) and there is no delete/update tool for created custom foods, despite mfp_create_food mentioning they 'can later delete'.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data