FatSecret MCP Server
Related Servers
Alternatives to FatSecret MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables searching and retrieving nutrition data, recipes, and managing food diary entries through the FatSecret API.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to search foods and recipes, track diet, manage weight, and log exercise using the FatSecret Platform API.4490 npm10MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to search foods and manage a personal nutrition diary, saved meals, exercise, weight, favorites, recipes, and monthly summaries via the FatSecret Platform API. It provides 39 tools with confirmation for mutating actions, OAuth 1.0 3-legged authentication, and MCP Streamable HTTP transport.MIT
- 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
- 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.90 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables logging meals, tracking calories and macros, reviewing daily and range summaries, setting weight goals, searching foods and recipes, and getting meal suggestions from any Claude client, with optional multi-user household support. Includes a local food database for items missing from FatSecret and OAuth-based authentication to FatSecret profiles.MIT
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.