Skip to main content
Glama
rwestergren

io.github.rwestergren/cronometer-api-mcp

by rwestergren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to io.github.rwestergren/cronometer-api-mcp

No user-submitted related servers found.

    Related Servers

    • cronometer-mcp

      cphoskins
      A
      license
      A
      quality
      B
      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
      431 PyPI
      22
      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

    • nutrition-mcp

      RootMePLS
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for personal nutrition tracking, enabling users to log meals with calories and macros, water intake, body weight, set goals, and import food diaries from other apps through natural language.
      114 npm
      MIT

    • Nutrition MCP

      edp8489
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables calorie and macronutrient tracking by letting users search foods, build recipes, compute macros, and log meals through an MCP server, with all nutrition calculations performed server-side.
      -
    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.4/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource. Similar nutrition query tools (get_food_log, get_daily_nutrition, get_nutrition_scores) have clear differentiators: diary entries with per-food details, daily totals, and category scores respectively. Recipe creation tools are separated by input type (free text vs. food IDs).

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (e.g., get_food_log, add_food_entry, update_custom_food, list_biometrics). Verbs like get/add/remove/update/delete/search/copy/mark are used predictably across resource types.

    Tool Count4/5

    At 19 tools, the set is slightly larger than the ideal 3-15 range but each tool addresses a distinct capability (diary, food database, custom foods, recipes, biometrics, fasting, targets). The count is justified by the breadth of Cronometer's feature set without becoming unwieldy.

    Completeness4/5

    The tool surface covers core workflows: food logging, diary management, custom food CRUD, recipe creation, nutrition analysis, biometrics, and fasting. Minor gaps exist (e.g., no direct diary entry editing, no exercise logging tool), but agents can work around these via remove/add or by using existing tools.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources