Skip to main content
Glama
fitdays-mcp-server

fitdays-mcp-server

by brad28820

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FITDAYS_EMAILYesYour FitDays account email address.
FITDAYS_REGIONNoFitDays API region. Defaults to us; other values are supported by fitdays-api.us
FITDAYS_PASSWORDYesYour FitDays account password.

Instructions

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

This MCP provides access to FitDays smart-scale data.

Use this MCP when the user asks about body weight, body fat, fat mass, body composition, smart-scale measurements, or health data related to weight and body composition.

For daily weigh-in checks, prefer calling get_todays_weigh_ins to fetch all of today's measurements and full details in a single call.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_todays_weigh_insA

Fetch all body-composition / weight measurements for a single calendar day (defaults to today in America/Chicago or FITDAYS_TIMEZONE) in one call. Returns date, timezone, count, has_weigh_in (boolean), latest (the most recent weigh-in for that day with full ext_data, or null if none), and weigh_ins (all weigh-ins for that day ordered newest first). By default forces a fresh sync (refresh: true) and excludes deleted records (include_deleted: false) while including full ext_data (include_ext_data: true). ext_data contains the measured person's context and FitDays reference values for interpreting the weight metrics. Treat these as informational rather than authoritative, and adjust them to the person's actual situation. Context fields describe the person and measurement state, including age, height, sex (female or male), and onlyMeasureWeight (whether the record contains weight only). Range and standard fields provide reference targets: Min and Max define the reference range, while Standard is the recommended value. They include body-fat mass, body-fat percentage, BMI, basal metabolic rate, bone mass, muscle mass, skeletal muscle mass, protein mass, water mass, and weight fields. Control fields indicate the suggested adjustment toward the corresponding Standard value, including bfmControl (body-fat mass), ffmControl (fat-free mass), and weightControl (weight). Fat-free-mass reference fields provide the recommended fat-free mass, including ffmStandard. Index fields provide skeletal-muscle indexing, including smi (skeletal muscle index). Classification fields describe body-composition status, including bodyScore, bodyType, and obesityDegree. Target fields describe target body-composition values, including targetWeight, targetBodyfatMass, and targetSMMMass; unavailable target-mass values are null. Device fields identify the source device, including deviceModelExt, deviceNameExt, and deviceSoftwareVer.

list_usersA

List the sub-users (people) registered under the FitDays account. Each user has a unique and stable suid, used by other tools to query data for that user. Returns a list where each entry contains nickname, sex (male or female, biological sex), birthday, height_cm, target_weight_kg (user-set target weight), suid, and uid (account uid).

list_devicesA

List the devices bound to the FitDays account. Returns device_id (FitDays device identifier), name, model, mac (MAC address), and firmware_ver (firmware version) for each device.

get_weight_historyA

Return body-composition / weight measurements, optionally filtered by sub-user (suid) and time window. Data is fetched lazily when no valid cache exists and stored in a global cache shared by all tools for 5 minutes; subsequent queries use that cached snapshot until it expires. Use refresh_sync if you are within the 5-minute cache window and fresher data is required. Returns a list ordered newest first. Each measurement contains weight_kg, weight_lb, bmi, bfr_pct (body fat percentage), rom_pct (muscle percentage), rosm_pct (skeletal muscle percentage), vwc_pct (body water percentage), pp_pct (protein percentage), sfr_pct (subcutaneous fat percentage), uvi (visceral fat index), bm_kg (bone mass), bmr_kcal (basal metabolic rate), bodyage (body age), measured_at (ISO 8601 timestamp), measured_time (Unix-seconds timestamp), data_id, suid, uid, and is_deleted. Set include_ext_data: true to also return ext_data for each record. ext_data contains the measured person's context and FitDays reference values for interpreting the weight metrics. Treat these as informational rather than authoritative, and adjust them to the person's actual situation. Context fields describe the person and measurement state, including age, height, sex (female or male), and onlyMeasureWeight (whether the record contains weight only). Range and standard fields provide reference targets: Min and Max define the reference range, while Standard is the recommended value. They include body-fat mass, body-fat percentage, BMI, basal metabolic rate, bone mass, muscle mass, skeletal muscle mass, protein mass, water mass, and weight fields. Control fields indicate the suggested adjustment toward the corresponding Standard value, including bfmControl (body-fat mass), ffmControl (fat-free mass), and weightControl (weight). Fat-free-mass reference fields provide the recommended fat-free mass, including ffmStandard. Index fields provide skeletal-muscle indexing, including smi (skeletal muscle index). Classification fields describe body-composition status, including bodyScore, bodyType, and obesityDegree. Target fields describe target body-composition values, including targetWeight, targetBodyfatMass, and targetSMMMass; unavailable target-mass values are null. Device fields identify the source device, including deviceModelExt, deviceNameExt, and deviceSoftwareVer. By default includes tombstoned records (is_deleted: 1); set include_deleted: false to hide them.

get_latest_weightA

Return the most recent body-composition / weight measurement in the current global cache, optionally for a single sub-user (suid). Data is fetched lazily when no valid cache exists and stored in a global cache shared by all tools for 5 minutes; subsequent queries use that cached snapshot until it expires. Use refresh_sync if you are within the 5-minute cache window and fresher data is required. Returns exactly one measurement containing weight_kg, weight_lb, bmi, bfr_pct (body fat percentage), rom_pct (muscle percentage), rosm_pct (skeletal muscle percentage), vwc_pct (body water percentage), pp_pct (protein percentage), sfr_pct (subcutaneous fat percentage), uvi (visceral fat index), bm_kg (bone mass), bmr_kcal (basal metabolic rate), bodyage (body age), measured_at (ISO 8601 timestamp), measured_time (Unix-seconds timestamp), data_id, suid, uid, is_deleted, and ext_data, or null if no matching measurement exists. ext_data contains the measured person's context and FitDays reference values for interpreting the weight metrics. Treat these as informational rather than authoritative, and adjust them to the person's actual situation. Context fields describe the person and measurement state, including age, height, sex (female or male), and onlyMeasureWeight (whether the record contains weight only). Range and standard fields provide reference targets: Min and Max define the reference range, while Standard is the recommended value. They include body-fat mass, body-fat percentage, BMI, basal metabolic rate, bone mass, muscle mass, skeletal muscle mass, protein mass, water mass, and weight fields. Control fields indicate the suggested adjustment toward the corresponding Standard value, including bfmControl (body-fat mass), ffmControl (fat-free mass), and weightControl (weight). Fat-free-mass reference fields provide the recommended fat-free mass, including ffmStandard. Index fields provide skeletal-muscle indexing, including smi (skeletal muscle index). Classification fields describe body-composition status, including bodyScore, bodyType, and obesityDegree. Target fields describe target body-composition values, including targetWeight, targetBodyfatMass, and targetSMMMass; unavailable target-mass values are null. Device fields identify the source device, including deviceModelExt, deviceNameExt, and deviceSoftwareVer. By default ignores tombstoned records (is_deleted: 1).

refresh_syncA

Force-refresh the global FitDays cache shared by all tools. FitDays data is loaded lazily: the first tool call that needs synchronized account data fetches a fresh snapshot and stores it in the global cache for 5 minutes. Returns synchronized record counts for devices, users, height_records, and weight_records (active, deleted, total).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation4/5

The tools are mostly clearly separated by purpose: users, devices, history, today's weigh-ins, latest measurement, and cache refresh. The three weight-retrieval tools overlap in data type, but their descriptions make the distinctions between filtered history, single-day convenience, and single latest record reasonably clear.

Naming Consistency4/5

Most names follow a consistent snake_case verb_noun pattern, such as list_users, get_weight_history, and refresh_sync. Minor deviations include get_todays_weigh_ins using 'weigh_ins' while other tools use 'weight', which is readable but slightly inconsistent.

Tool Count5/5

Six tools is well scoped for a read-only FitDays data server. Each tool covers a distinct access pattern or cache operation, and none feels redundant enough to remove.

Completeness4/5

The surface covers users, devices, weight history, daily weigh-ins, latest measurement, and cache refresh. A minor gap is that refresh_sync references height_records, but no tool exposes height-record history, so that part of the domain is not directly accessible.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues