fatsecret-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FATSECRET_CLIENT_ID | Yes | Your FatSecret API Client ID | |
| FATSECRET_ACCESS_TOKEN | Yes | User-level OAuth access token | |
| FATSECRET_CLIENT_SECRET | Yes | Your FatSecret API Client Secret | |
| FATSECRET_ACCESS_TOKEN_SECRET | Yes | User-level OAuth access token secret |
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 |
|---|---|
| fatsecret_search_foodA | Search the FatSecret food database by name. Returns food items with basic nutrition info per serving. Use this to find food_id and serving_id needed for logging diary entries. Args:
Returns: List of foods with id, name, description (brief nutrition summary). |
| fatsecret_get_foodA | Get detailed nutrition information for a specific food by its food_id. Returns all available servings with full macro and micronutrient breakdown. Use this after fatsecret_search_food to get the serving_id and nutrition data needed for logging. Args:
Returns: Food name, servings list with serving_id, serving description, calories, protein, carbs, fat, and available micronutrients. |
| fatsecret_create_food_entryA | Create a food diary entry for the user. Logs a specific food + serving to a meal on a given date. You need food_id and serving_id from fatsecret_search_food / fatsecret_get_food. Args:
Returns: Created food entry with nutrition totals. |
| fatsecret_edit_food_entryA | Edit an existing food diary entry. Can change serving size, number of units, or meal type. Args:
Returns: Updated entry with new nutrition values. |
| fatsecret_delete_food_entryA | Delete a food diary entry by its ID. Args:
Returns: Confirmation of deletion. |
| fatsecret_get_food_entriesA | Get all food diary entries for a specific date. Shows what was logged for each meal with full nutrition breakdown. Args:
Returns: All food entries grouped by meal with calories, protein, carbs, fat per entry and daily totals. |
| fatsecret_get_food_entries_monthA | Get daily calorie/macro totals for an entire month. Useful for tracking adherence and trends. Args:
Returns: Daily totals for each logged day in the month. |
| fatsecret_create_saved_mealA | Create a reusable meal template (e.g., "Post-Workout Chicken & Rice"). After creating, add foods to it with fatsecret_add_food_to_saved_meal. Args:
Returns: Created saved meal with its ID. |
| fatsecret_add_food_to_saved_mealA | Add a food item to an existing saved meal template. Args:
Returns: Confirmation with nutrition details. |
| fatsecret_get_saved_mealsA | Get all saved meal templates for the user. Shows meal names, IDs, and food items within each. Returns: List of saved meals with their IDs, names, and food contents. |
| fatsecret_copy_saved_meal_to_diaryA | Copy all foods from a saved meal template into the food diary for a specific date and meal. Args:
Returns: Confirmation that entries were created. |
| fatsecret_update_weightA | Log a weight measurement for a specific date. Args:
Returns: Confirmation of logged weight. |
| fatsecret_get_weights_monthA | Get weight entries for an entire month. Useful for tracking weight trends during bulk/cut phases. Args:
Returns: All weight entries for the month with dates. |
| fatsecret_get_recently_eatenA | Get the user's recently eaten foods for quick re-logging. Returns food IDs and serving info ready to use with fatsecret_create_food_entry. Returns: List of recently logged foods with IDs and serving details. |
| fatsecret_copy_dayA | Copy all food entries from one date to another. Useful for repeating a day's meals. Args:
Returns: Confirmation. |
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 15 tools
Each tool targets a distinct action or resource (food entries, saved meals, weight, search, monthly views). There is no overlap; even the two copy tools copy different things (day vs saved meal to diary). High clarity.
All tool names follow a consistent 'fatsecret_verb_noun' pattern in snake_case (e.g., fatsecret_create_food_entry, fatsecret_get_weights_month). No deviations or mixed conventions.
15 tools cover the domain of nutrition tracking comprehensively without bloat. Each tool serves a clear purpose, and the count is appropriate for the scope (food diary, saved meals, weight, search).
The tool surface covers core CRUD for food entries and weight, saved meal templates, search, and monthly summaries. Minor gaps exist (e.g., no update/delete for saved meals), but the essential workflows are completable.