Bodylog MCP Server

Agent-first workout and food log: sets and meals from chat, USDA and Open Food Facts macros, cards.

Local serverstdio

What is the Bodylog MCP Server?

Bodylog is an MCP integration. Agent-first workout and food log: sets and meals from chat, USDA and Open Food Facts macros, cards.

Packages and local setup

The published pypi package is bodylog, version 0.1.0. Its declared MCP transport is stdio.

The package declares BODYLOG_DB: SQLite file for the log (default ~/.bodylog/log.db); BODYLOG_CARDS: Directory for rendered card PNGs (default ~/.bodylog/cards); FDC_API_KEY: USDA FoodData Central API key (free at api.data.gov); DEMO_KEY is used without one; BODYLOG_OFFLINE: Set to 1 to use only the bundled USDA table, no network lookups.

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
BODYLOG_DBSQLite file for the log (default ~/.bodylog/log.db)Optional
BODYLOG_CARDSDirectory for rendered card PNGs (default ~/.bodylog/cards)Optional
FDC_API_KEYUSDA FoodData Central API key (free at api.data.gov); DEMO_KEY is used without oneOptional
BODYLOG_OFFLINESet to 1 to use only the bundled USDA table, no network lookupsOptional