myfitnesspal
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MFP_COOKIES | No | Exported MyFitnessPal cookies for environments without browser access |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_daily_summaryA | Get daily nutrition overview: calories consumed/remaining, macro breakdown, water, and goals. Args: date: Date in YYYY-MM-DD format (defaults to today) |
| get_daily_mealsA | Get detailed meal-by-meal breakdown with all foods, servings, and calories. Args: date: Date in YYYY-MM-DD format (defaults to today) |
| get_daily_exerciseA | Get exercise activities: cardio (duration, calories) and strength (sets, reps, weight). Args: date: Date in YYYY-MM-DD format (defaults to today) |
| get_daily_macrosB | Get comprehensive macro and micronutrient breakdown with all tracked nutrients. Args: date: Date in YYYY-MM-DD format (defaults to today) |
| get_water_intakeA | Get water consumption for a specific day. Args: date: Date in YYYY-MM-DD format (defaults to today) |
| get_date_range_summaryA | Get aggregate nutrition data over a date range with trends and insights. Args: start_date: Start date in YYYY-MM-DD format end_date: End date in YYYY-MM-DD format |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct data aspect: exercise, macros, meals, summary, date range summary, and water. There is no overlap; even the summary tool is clearly a high-level overview.
All tool names follow the consistent pattern 'get_daily_<aspect>' or 'get_date_range_summary' and 'get_water_intake', all using snake_case.
With 6 tools, the server is well-scoped for a read-only fitness data retrieval API. The count is appropriate for the domain.
The tool surface covers all typical daily data retrieval needs (exercise, macros, meals, water, summary, and date range). Missing write operations or weight tracking, but these may be out of scope.