Skip to main content
Glama
cphoskins

cronometer-mcp

by cphoskins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to cronometer-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      48 npm
      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.
      -

    • foodvisor-mcp

      cldt-fr
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server integrating Foodvisor nutrition API for food search, meal logging, daily summaries, and progress tracking via LLM agents like Claude.
      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

    A3.6/5.0

    Scored across 27 tools

    Disambiguation4/5

    The tools are largely organized into clear subdomains: food logging, nutrition summaries, macro targets, fasting, biometrics, repeated items, and diary management. A few boundaries could still trip up an agent, such as cancel_active_fast vs. delete_fast and creating vs. applying macro templates, but the descriptions and complementary parameters make most selections clear.

    Naming Consistency4/5

    Tool names consistently follow a verb_noun style with snake_case throughout, which makes the set predictable. The main inconsistency is vocabulary: get_ vs. list_, remove_ vs. delete_ vs. cancel_, and create_macro_template vs. add_food_entry, but these are minor style deviations rather than pattern-breaking names.

    Tool Count2/5

    27 top-level tools is above the 25+ threshold and will burden an agent during tool selection, even though most tools individually earn their place. The set covers many Cronometer subdomains, but it would be more usable split into smaller servers or with some related operations consolidated.

    Completeness3/5

    The server covers food logging, nutrition retrieval, macro targets, fasting stats, biometrics, repeated items, and diary operations with read/create/delete paths for most entities. However, there are notable lifecycle gaps: no start_fast operation, no update/edit path for food entries or repeated items, and no direct exercise or note logging outside raw CSV exports.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources