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.
      16 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
      D
      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.9/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target a distinct resource+action, and descriptions clarify granularity (get_daily_nutrition = macro totals, get_micronutrients = micros, get_food_log = individual entries). However, these three nutrition-report tools plus export_raw_csv (daily_summary) overlap enough that an agent could reasonably pick the wrong one for 'get my nutrition data'.

    Naming Consistency5/5

    Every tool follows a predictable snake_case verb_noun pattern (get_/set_/add_/remove_/delete_/list_/search_/create_/cancel_/sync_/copy_). Consistent across all 27 tools with no convention mixing.

    Tool Count3/5

    27 tools is on the heavy side and sits at the borderline where separate subdomains (food logging, macros/templates, fasting, biometrics, repeat items, sync/export) each pull in their own tools. Defensible for a feature-rich domain but feels somewhat bloated.

    Completeness4/5

    Food entries, biometrics, macros/templates, fasting, repeat items, day copy/complete, sync and export are well covered. Minor gaps: no way to start a fast (only delete/cancel exist) and no update operations for food entries or biometrics, only add/remove.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources