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
      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
      468 PyPI
      24
      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.
      37 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

    Disambiguation4/5

    Most tools target distinct resources/actions (search vs details, list vs get for biometrics, history vs stats for fasting, custom-food CRUD). The main overlaps are add_recipe vs import_recipe and the trio get_food_log/get_daily_nutrition/get_nutrition_scores, but their descriptions clearly delineate entries-vs-totals-vs-grades so an agent can still pick correctly.

    Naming Consistency5/5

    Nearly every tool follows a clean snake_case verb_noun pattern (add_custom_food, get_food_log, remove_food_entry, search_foods, list_biometrics). Even exceptions like copy_day and mark_day_complete read as verb_noun and fit the convention smoothly.

    Tool Count4/5

    19 tools is on the heavier side for the 16-25 band, but the server legitimately spans several sub-domains (food logging, custom foods, recipes, diary management, nutrition analysis, biometrics, fasting, targets). Each tool maps to a real operation, so the count is justified rather than padded.

    Completeness4/5

    Food logging, custom-food CRUD, recipe creation, diary management, nutrition reads, biometrics reads, and fasting reads are all covered. Gaps exist on the write side — no way to set/update macro targets, add biometric measurements, or start/stop a fast — but core logging and reporting workflows are intact.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources