MCP server for FatSecret API - food search, nutrition, diary, recipes, weight tracking (unofficial)
Fatsecret MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for FatSecret API - food search, nutrition, diary, recipes, weight tracking (unofficial).
An MCP (Model Context Protocol) server that connects Claude/Cursor to the FatSecret Platform API. Search foods, track your diet, manage recipes, and monitor weight directly from your AI assistant.
Once Fatsecret MCP is connected, these are the calls the assistant has available:
check_auth_status — Check if credentials and profile auth are configured. Call this first.setup_credentials — Save FatSecret API credentials to persistent configstart_auth — Start OAuth 1.0 authorization — returns URL for user to visitcomplete_auth — Complete OAuth with verifier PIN from authorization pagesearch_foods — Search the food databaseget_food — Get detailed nutrition info for a foodfind_food_by_barcode — Find food by GTIN-13 barcodeautocomplete_foods — Get search autocomplete suggestionssearch_recipes — Search recipes with filtersget_recipe — Get recipe details with ingredients and directionsget_food_categories — Get food categoriesget_food_sub_categories — Get food sub categoriesThe server ships on npm as fatsecret-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need 3 environment variables: FATSECRET_CLIENT_ID, FATSECRET_CLIENT_SECRET, FATSECRET_CONSUMER_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Fatsecret MCP's toolset — check_auth_status, setup_credentials, start_auth and 11 more — is a fair guide to whether it matches your workflow. It is maintained by fliptheweb; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| check_auth_status | Check if credentials and profile auth are configured. **Call this first.** |
| setup_credentials | Save FatSecret API credentials to persistent config |
| start_auth | Start OAuth 1.0 authorization — returns URL for user to visit |
| complete_auth | Complete OAuth with verifier PIN from authorization page |
| search_foods | Search the food database |
| get_food | Get detailed nutrition info for a food |
| find_food_by_barcode | Find food by GTIN-13 barcode |
| autocomplete_foods | Get search autocomplete suggestions |
| search_recipes | Search recipes with filters |
| get_recipe | Get recipe details with ingredients and directions |
| get_food_categories | Get food categories |
| get_food_sub_categories | Get food sub categories |
| get_brands | Get food brands |
| get_recipe_types | Get recipe types |
{
"mcpServers": {
"fatsecret": {
"command": "npx",
"args": ["-y", "fatsecret-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| FATSECRET_CLIENT_ID | Credential the server authenticates with. | Yes |
| FATSECRET_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| FATSECRET_CONSUMER_SECRET | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.