Skip to main content
Glama
cabird

loseit-mcp

by cabird
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to loseit-mcp

No user-submitted related servers found.

    Related Servers

    • loseit

      the-mace
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that reads local SQLite database populated by a Playwright scraper to provide daily summary, food log, weight history, and water log from LoseIt.
      MIT

    • Macro Engine

      rockitdev
      A
      license
      Not graded
      quality
      C
      maintenance
      Tracks macros and logs meals via plain language by exposing a local USDA food database as an MCP server.
      MIT

    • fatsecret-mcp

      ikeike443
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for FatSecret that enables searching foods/recipes and managing personal food diary, weight, and exercise logs via natural language.
      51 npm
      MIT

    • fatsecret-mcp-server

      Yurzs
      A
      license
      A
      quality
      D
      maintenance
      MCP server for managing food diary, nutrition tracking, meal planning, and weight logging via the FatSecret Platform API.
      15
      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

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: diary reading, food searching, nutrition detailing, two types of food logging, entry deletion, weight logging, and account info. No overlap that would confuse an agent.

    Naming Consistency4/5

    Tools mostly follow a verb_noun pattern (get_diary, search_food, log_food, delete_entry, log_weight). The exception is 'whoami', which is a standard command but doesn't fit the verb_noun convention, causing minor inconsistency.

    Tool Count5/5

    With 8 tools, the server is well-scoped for a food and weight tracking service. Each tool earns its place, covering diary, food database, logging, weight, and account queries.

    Completeness4/5

    Core workflows are covered: diary reading, food search and description, logging (both database and custom), deletion, weight logging, and account info. Missing update/edit functionality for diary entries, but agents can delete and re-log as a workaround.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources