MyFitnessPal MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MFP_USERNAME | Yes | Your MyFitnessPal username. | |
| MFP_SESSION_COOKIE | Yes | Your MyFitnessPal session cookie from browser. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_diaryA | Get food diary entries for a specific date. Returns all meals with their food entries and calorie/macro totals. |
| get_nutrition_summaryA | Get a nutrition summary for a specific date, including calories, carbs, fat, protein, sodium, and sugar with their goals. |
| get_goalsA | Get your daily calorie and macro goals from MyFitnessPal. |
| quick_add_caloriesB | Add calories to your diary using Quick Add. Optionally specify carbs, fat, and protein. |
| search_foodA | Search the MyFitnessPal food database. Returns food items with calories and macros. |
| get_food_detailsA | Get detailed nutrition information and serving sizes for a specific food item. Use the food ID from search_food results. |
| add_foodA | Add a food item to your diary. Use search_food to find the food ID first. Optionally use get_food_details to find a specific serving size. |
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 7 tools
Most tools are clearly distinct: search_food and get_food_details relate to the food database, while get_diary and get_nutrition_summary relate to daily records. There is minor overlap between get_diary and get_nutrition_summary since both expose calorie/macro totals, but their descriptions clarify the different levels of detail.
Tool names follow a consistent snake_case verb_noun pattern: get_diary, get_goals, search_food, add_food, quick_add_calories. The naming style is uniform and predictable across all seven tools.
Seven tools is a well-scoped size for a nutrition diary server. Each tool covers a meaningful part of the workflow—viewing data, searching foods, and logging entries—without unnecessary redundancy.
The server covers core read and add workflows: viewing diary data, searching foods, getting details, and adding entries. However, it lacks update and delete operations for diary entries, which is a notable gap when correcting mistakes or modifying logged food.