Skip to main content
Glama
Cronometer MCP

Cronometer MCP

by ChrisJVanek

Related Servers

Alternatives to Cronometer MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Connects compatible AI assistants to a Cronometer account to review nutrition and diary data, search foods, log or remove meals, create custom foods and recipes, and retrieve fasting, biometric, and export history.
      3
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that provides access to Cronometer nutrition data, enabling users to pull food logs, macro and micronutrient summaries, and biometric data into Claude or Cursor. It supports daily nutrition tracking and raw CSV exports by interfacing with the Cronometer web protocol.
      27
      606 PyPI
      28
      MIT
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Unofficial, self-hosted MCP server that connects Claude or ChatGPT to your own FatSecret food diary. It drafts entries from a description, a plate photo or a nutrition label, saves them only after you confirm, and changes or removes entries the same way. It also reads a day or several weeks against your calorie and macro targets.
      2
      5
      64 PyPI
      6
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Connects Claude, ChatGPT, or Codex to a Yazio food diary so it can search the product catalogue, log foods, water and calories, delete entries, and read daily summaries, nutrient history and goals. Deploys as a Cloudflare Worker custom connector with OAuth, requiring no local runtime.
      3,097 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 65 tools

    Disambiguation2/5

    Several tools overlap significantly: remove_food_entry can delete foods, exercise, biometrics, or notes even though dedicated remove_note, remove_exercise, and remove_biometric tools exist; generic search/fetch duplicate search_foods/get_food_details; and create_recipe can update recipes while update_recipe also edits them. Nutrition reporting is split across get_food_log, get_daily_nutrition, analyze_day, get_nutrition_summary, nutrient_report, and get_nutrition_scores, whose boundaries are described but still easy to confuse.

    Naming Consistency4/5

    All names use snake_case and mostly follow verb_noun patterns. Minor inconsistencies exist in verb choice, such as remove versus delete, add versus create, and generic search/fetch names that are less descriptive than the rest.

    Tool Count1/5

    With 65 tools, the surface is far beyond a well-scoped set, even for a rich domain like Cronometer. The large count is compounded by overlapping removal, nutrition-reporting, and recipe-editing tools.

    Completeness4/5

    Coverage is broad: diary entries, custom foods, recipes, biometrics, exercise, fasting, nutrient and macro targets, repeated items, notes, exports, and account status are all represented. There are minor gaps and inconsistencies, such as contradictory note-deletion guidance and no explicit water or supplement logging surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues