Skip to main content
Glama
firaskudsy

cronometer-api-mcp

by firaskudsy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to 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
      24
      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

    • YAZIO MCP Server

      yazio-community
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server over the YAZIO food diary that lets a model read what you've eaten today, log meals, build recipes from tracked products, track water, weight and exercise, and query nutrition summaries, goals and profiles.
      2
      MIT

    • MacroMCP

      lukew0824
      F
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server for natural-language calorie/macro and weight tracking, designed to connect to Claude.ai as a custom connector.
      -
    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.3/5.0

    Scored across 13 tools

    Disambiguation4/5

    Tools have distinct primary purposes, but get_food_log, get_daily_nutrition, and get_nutrition_scores provide overlapping nutrition data at different granularities. Descriptions help differentiate, but an agent might still be confused about which to use for a specific need.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., get_macro_targets, search_foods, add_food_entry). The naming is predictable and clear.

    Tool Count5/5

    With 13 tools, the surface is well-scoped for a nutrition tracking API. Each tool serves a clear function without unnecessary duplication, covering targets, logging, food management, and fasting.

    Completeness4/5

    Core CRUD operations are covered (search, add, remove, custom food creation). Day management (copy, mark complete) and multiple read endpoints exist. Missing is an update/editing capability for diary entries, but removal and re-addition can compensate.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources