FatSecret MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FATSECRET_PASSWORD | No | Password for member recipe and RDI operations. | |
| FATSECRET_USERNAME | No | Username for member recipe and RDI operations. | |
| FATSECRET_ACCOUNT_ID | No | Stable account label used for mutations. | |
| FATSECRET_ACCESS_TOKEN | No | Access token required for user-scoped tools. | |
| FATSECRET_CONSUMER_KEY | Yes | FatSecret consumer key used for API authentication. | |
| FATSECRET_ACCESS_SECRET | No | Access token secret required for user-scoped tools. | |
| FATSECRET_CONSUMER_SECRET | Yes | FatSecret consumer secret used for API authentication. | |
| FATSECRET_MCP_ALLOW_CREDENTIAL_TOOLS | No | Set to 'true' to enable credential tools; should only be exposed temporarily through the bootstrap profile. | false |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_auth_statusA | Report which credential sets are configured without exposing values. |
| search_foodsB | Search foods with the latest Platform endpoint available to the account. |
| get_foodB | Get a food by ID using the latest endpoint available to the account. |
| search_recipesC | Search public recipes using the latest reviewed Platform endpoint. |
| get_recipeA | Get one public recipe by exact recipe ID. |
| get_user_profileA | Get the authenticated Platform user's profile. |
| get_user_food_entriesA | Get authenticated food diary entries by epoch-day or entry ID. |
| add_food_entryA | Add a food diary entry once, keyed by a durable idempotency value. |
| get_weight_monthA | Get authenticated weight records for the month containing an epoch-day. |
| resolve_fatsecret_capabilityC | Find latest backend operations and optionally execute one safe read. |
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 10 tools
Each domain tool has a clear target resource and action, so search_foods, get_food, search_recipes, and get_recipe are easy to separate. However, resolve_fatsecret_capability is a broad meta-tool that can optionally execute a safe read, creating mild overlap with the read operations.
All tool names follow a consistent lower_snake_case verb_noun pattern, such as search_foods, get_recipe, add_food_entry, and get_weight_month. The naming is predictable and makes the toolset easy to navigate.
With 10 tools, the server is well-scoped for a nutrition and food-tracking API. It covers auth, food search, recipe search, user profile, diary entries, and weight without feeling bloated or sparse.
Core workflows like searching foods/recipes, viewing profiles, adding food entries, and reading weight are present. However, there is no update/delete operation for food diary entries and no way to write weight records, which are notable gaps in a logging/tracking domain.