MyFitnessPal MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MFP_COOKIES | No | Exported cookies for MyFitnessPal authentication, required for environments without browser access (Docker containers, remote servers, etc.). Use export_cookies.py utility to extract cookies. Cookies expire after ~30 days. |
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
Server capabilities have not been inspected yet.
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
The tools have clear distinctions in their data focus (exercise, macros, meals, summary, date range, water), but there is significant functional overlap between get_daily_summary and the more specific tools like get_daily_macros or get_daily_meals, which could lead to confusion about which to use for certain queries. The descriptions help clarify, but the boundaries are not perfectly distinct.
All tool names follow a consistent verb_noun pattern with 'get_' as the prefix, followed by descriptive nouns (e.g., get_daily_exercise, get_daily_macros). This uniformity makes the tool set predictable and easy to understand at a glance.
With 6 tools, the count is reasonable for a fitness tracking domain, covering key aspects like daily data, summaries, and date ranges. It's slightly lean but well-scoped, though it might benefit from additional tools for actions like logging or updating data.
The tool set is severely incomplete as it only provides read-only operations (all 'get_' tools) with no ability to create, update, or delete data. For a fitness app like MyFitnessPal, this misses essential CRUD functionality such as logging meals, exercises, or water intake, which are core to the domain.