Skip to main content
Glama
cabird

loseit-mcp

by cabird
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOSEIT_EMAILNoLose It! account email
LOSEIT_TOKENNoA `liauth` JWT, used instead of email/password
LOSEIT_PASSWORDNoLose It! account password
LOSEIT_POLICY_HASHNoGWT policy hash, if Lose It ships a new build
LOSEIT_STRONG_NAMENoGWT permutation, if Lose It ships a new build
LOSEIT_HOURS_FROM_GMTNoUTC offset in whole hours; auto-detected

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_foodA

Search the Lose It! food database. Returns candidate foods with a food_id to pass to log_food or describe_food.

describe_foodA

Get full nutrition detail and serving information for one food, identified by the food_id returned from search_food.

get_diaryA

Read the food diary for a day: every logged entry with calories and macros, plus the day's totals. Each entry carries an entry_id for delete_entry.

log_foodB

Log a food to a meal in the diary. Specify the portion EITHER as serving_amount + serving_unit (e.g. 120 and 'g') OR as servings (a multiplier of the food's default serving). Set dry_run to preview.

log_custom_foodA

Log a food by its exact nutrition values, without needing a match in the food database. Use this for restaurant meals, homemade dishes, or anything where you know the calories and macros but search_food has no good match. Values are per serving.

delete_entryA

Delete a diary entry. Get the entry_id from get_diary for the same day. A recoverable copy is written to local trash before deleting.

log_weightA

Record a weigh-in for a day. The unit follows the account's display setting (lb or kg).

whoamiA

Show which Lose It! account this server is authenticated as.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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