Skip to main content
Glama
rollecode

Cronometer MCP server

by rollecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Cronometer MCP server

No user-submitted related servers found.

    Related Servers

    • cronometer-api-mcp

      mhyounis19
      A
      license
      A
      quality
      B
      maintenance
      Enables nutrition tracking with Cronometer, including food logging, food search, diary management, and nutrition data retrieval via natural language.
      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.
      13 npm
      MIT

    • mfp-mcp

      Mason-Levyy
      A
      license
      Not graded
      quality
      B
      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.
      170 PyPI
      26
      MIT

    • Personal Cronometer MCP

      ekelly95
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients like Codex and Claude Code to securely read and manage a personal Cronometer account, including food logs, nutrient summaries with missing-data awareness, food search, biometrics, and export analysis.
      MIT

    • fatsecret-coach

      Shirlineyn
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables logging meals, tracking calories and macros, reviewing daily and range summaries, setting weight goals, searching foods and recipes, and getting meal suggestions from any Claude client, with optional multi-user household support. Includes a local food database for items missing from FatSecret and OAuth-based authentication to FatSecret profiles.
      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

    A4/5.0

    Scored across 41 tools

    Disambiguation4/5

    Tools are largely distinguishable by resource+action, and the descriptions explicitly clarify tricky pairs (get_food_log vs get_daily_nutrition vs get_nutrition_scores, add_custom_food vs create_recipe vs update_recipe). The main overlap is create_recipe doubling as an update path alongside update_recipe, and get_food_log carrying nutrition_summary that duplicates get_daily_nutrition, which could cause occasional misselection.

    Naming Consistency4/5

    Almost all tools follow a clean verb_noun snake_case pattern (get_food_log, add_food_entry, list_biometrics, edit_exercise). The only deviation is the remove_*/delete_* split, with delete_fast breaking from the otherwise consistent remove_* convention used for biometrics, exercises, and entries.

    Tool Count3/5

    41 tools is heavy and exceeds the comfortable range, though the domain (diary, foods, recipes, biometrics, fasting, targets, notes) is genuinely broad and most tools map to distinct operations. The per-entity CRUD clusters inflate the surface, making it borderline over-scoped.

    Completeness5/5

    Coverage is thorough: full CRUD on food entries, custom foods, recipes, biometrics, exercises, fasts, notes, and targets, plus day-level operations, paging, and discovery helpers. The only 'gaps' (no hard delete for foods/notes) are documented Cronometer limitations rather than surface omissions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources