FatSecret MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FatSecret MCP Server Search for 'quinoa' and show its nutrition facts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FatSecret MCP Server
An independent Python MCP server backed by the fatsecret package. It exposes
the supported FatSecret Platform API separately from experimental member-site
recipe, diary, and RDI operations.
This project has independent source code and Git history. Compatibility tool names were transcribed from a pre-existing public tool list; no implementation, schemas, configuration, tests, or architecture were copied from that project.
Install
Run the current GitHub version with a fresh dependency resolution at each MCP server start:
uvx --refresh --from git+https://github.com/ChocoTonic/fatsecret-mcp-server \
fatsecret-mcp-server --profile defaultuvx --refresh is the update mechanism. The running server does not rewrite
its own executable or dependency environment. Each server release constrains
the reviewed fatsecret backend. Official food reads prefer the latest
reviewed method and cache the newest version accepted by the configured
account; only upstream error 10 triggers an older-method fallback.
Related MCP server: fatsecret-mcp
Configure
Platform credentials:
export FATSECRET_CONSUMER_KEY=...
export FATSECRET_CONSUMER_SECRET=...
export FATSECRET_ACCESS_TOKEN=... # required for user-scoped tools
export FATSECRET_ACCESS_SECRET=...
export FATSECRET_ACCOUNT_ID=... # stable account label for mutationsMember recipe, diary, and RDI credentials:
export FATSECRET_USERNAME=...
export FATSECRET_PASSWORD=...Credentials may instead be stored in the operating-system keyring. Credential
tools are disabled unless FATSECRET_MCP_ALLOW_CREDENTIAL_TOOLS=true and should
only be exposed temporarily through the bootstrap profile.
Profiles are default, member, discovery, diary, bootstrap, and full.
The capability resolver is present in every profile. It can execute only an
explicitly reviewed read allowlist permitted by the active profile, without
advertising every backend schema. Resolved writes and authentication metadata
are blocked.
Mutation contract
Every resource mutation requires an idempotency key. Reuse the same key after a timeout; using it for a different payload is rejected. Recipe-copy resumes use their durable operation ID as the idempotency identity. Ambiguous outcomes are retained as unknown and must be reconciled before another write.
Durable state is namespaced by a one-way account identifier. Account writes are serialized across server processes, and the state directory, database, and lock files are restricted to the current operating-system user.
Recipe ingredients use a known FatSecret food_id. Omit portion_id for grams,
or first call list_member_food_portions to select an exact opaque portion ID.
The member website stores gram quantities as whole numbers; fractional grams
are rejected before writing.
Member diary tools accept both foods and owned recipes. Omit portion_id to
select grams when available or the sole recipe serving. Website portion IDs
-1 (grams) and 0 (owned recipe serving) are valid here and intentionally
remain separate from official API serving IDs. Recipe diary entries snapshot
nutrition, so delete and re-add affected diary entries after recipe changes.
Member recipe, diary, and RDI operations automate unsupported FatSecret website forms and can break when that website changes.
See architecture and the tool inventory.
Available Tools
10 toolsadd_food_entryAIdempotent
Add a food diary entry once, keyed by a durable idempotency value.
Inputs: meal (required), food_id (required), serving_id (required), food_entry_name (required), +3 more. Returns: result
check_auth_statusARead-only
Report which credential sets are configured without exposing values.
Inputs: no named parameters. Returns: object
get_foodBRead-only
Get a food by ID using the latest endpoint available to the account.
Inputs: food_id (required). Returns: result
get_recipeARead-only
Get one public recipe by exact recipe ID.
Inputs: recipe_id (required). Returns: result
get_user_food_entriesARead-only
Get authenticated food diary entries by epoch-day or entry ID.
Inputs: date, food_entry_id. Returns: result
get_user_profileARead-only
Get the authenticated Platform user's profile.
Inputs: no named parameters. Returns: result
get_weight_monthARead-only
Get authenticated weight records for the month containing an epoch-day.
Inputs: date. Returns: result
resolve_fatsecret_capabilityCRead-only
Find latest backend operations and optionally execute one safe read.
Inputs: need (required), execute, arguments. Returns: object
search_foodsBRead-only
Search foods with the latest Platform endpoint available to the account.
Inputs: query (required), page, limit, region, +1 more. Returns: result
search_recipesCRead-only
Search public recipes using the latest reviewed Platform endpoint.
Inputs: query (required), page, limit, region. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Broad, OAuth-protected provider and financial-domain API tools for research agents.
Every Canopy public API operation as a tool, run as you after a browser sign-in or on an API key.
Access Pollinations models and API capabilities through agent tools.
Discover, plan and run tools across your connected business systems through one OAuth MCP endpoint
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables searching and retrieving nutrition data, recipes, and managing food diary entries through the FatSecret API.MIT
- AlicenseNot gradedqualityCmaintenanceProvides LLM agents with read-only access to FatSecret's food and recipe database through MCP tools for searching foods and retrieving detailed nutritional information.113 npmMIT
- AlicenseBqualityCmaintenanceEnables searching FatSecret's food and recipe database, and managing personal food diary, weight, exercise, saved meals, and favorites, with multi-user support and secure OAuth authentication.28Apache 2.0
- AlicenseBqualityBmaintenanceEnables AI assistants to search foods and recipes, track diet, manage weight, and log exercise using the FatSecret Platform API.44113 npm12MIT