About this integration
MCP server for FatSecret API - food search, nutrition, diary, recipes, weight tracking (unofficial)
- Transport
- stdio
- Authentication
- oauth
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.0.8
- Package
- fatsecret-mcp
- Last compatibility test
- Not independently tested
Connect your agent
fatsecret-mcpOAuth is used as the primary classification because personal-data tools require user authorization. No FatSecret account was accessed.
Capabilities: Search foods and recipes, Manage food diary and exercise data, Track weight, favorites, and saved meals
Connected profiles
Additional details
io.github.fliptheweb/fatsecret-mcp
Source ↗ · Checked 2026-09-170.0.8
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17FATSECRET_CLIENT_ID, FATSECRET_CLIENT_SECRET, FATSECRET_CONSUMER_SECRET
Source ↗ · Checked 2026-09-17fatsecret-mcp
Source ↗ · Checked 2026-09-190.0.9
Source ↗ · Checked 2026-09-19The MCP client launches the npm package with npx.
Source ↗ · Checked 2026-09-19Client credentials enable public data, while OAuth authorization is required for profile, diary, and weight tools.
Source ↗ · Checked 2026-09-19The local stdio process connects to FatSecret after credential setup and, for personal data, user authorization.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19