Skip to main content
Glama
abhaymettu

bodylog

by abhaymettu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to bodylog

No user-submitted related servers found.

    Related Servers

    • gym

      SklyerX
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables logging workouts, sets, routines, food, water, and macros through natural-language chat in any MCP client, with OAuth-based secure access and timezone-aware daily tracking.
      ISC

    • fitness-mcp

      wbratz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables conversational logging and retrieval of workouts, sets, weigh-ins, meals, goals, plans, and progress photos through MCP-capable AI clients, with authenticated per-user storage and export/query capabilities.
      ISC

    • Health & Fitness Coach MCP

      Dinesh-Satram
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive AI-powered fitness tracking application that enables AI tools to interact intelligently with user fitness data, providing personalized workout plans, nutrition tracking, and progress analysis through natural language.
      15
      MIT

    • daizee-mcp

      fazilnazkolambil
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables voice assistants to keep a persistent health memory across conversations, so allergies and temporary notes like a sore knee are remembered, expire on their own, and are checked against meals and daily calorie/macro goals as they are logged. Provides meal logging with allergy and diet warnings, memory recall and two-step forgetting, and daily weigh-ins that are never spoken aloud.
      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.6/5.0

    Scored across 15 tools

    Disambiguation4/5

    Tools are mostly distinct by domain: food vs. workout logging, and card generation vs. raw data. A few pairs (food_card/session_card, lookup_food/log_food, prs/exercise_history) could be confused, but their descriptions clarify the boundaries well.

    Naming Consistency3/5

    All names are snake_case and readable, but the pattern is mixed: some are verb-first (log_food, end_session, edit_food) while others are noun-first (food_card, session_card, weekly_volume, prs). This is a readable mixed convention rather than a consistent one.

    Tool Count5/5

    Fifteen tools is at the upper end of the typical range, but the server covers two distinct domains—food logging and workout logging—and each tool has a clear, non-redundant purpose. The count feels appropriate for the stated scope.

    Completeness4/5

    The surface covers food logging, editing, searching, goals, summaries, and cards, plus workout logging, workout cards, history, PRs, volume, streaks, and chat import. The main gap is that workout set editing is limited to the most recent set, with no way to edit or delete arbitrary past workout entries.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources