An MCP server for interacting with Cronometer's nutrition tracking service via the mobile app's reverse-engineered JSON REST API. It supports reading and editing food diary data, searching foods, viewing nutrition totals and scores, managing custom foods, macro targets, and fasting data.
From the registry: MCP server for Cronometer nutrition tracking — food logs, diary, macros, fasting
$ curl -LsSf https://astral.sh/uv/install.sh | shPlease install the `cronometer-api-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install uv** — Install uv so you can run the MCP server via uvx without a separate package installation step. Run: `curl -LsSf https://astral.sh/uv/install.sh | sh` (https://docs.astral.sh/uv/)
- **Cronometer account credentials** — Provide your Cronometer account email and password for server authentication. (https://cronometer.com/)
Canonical MCP server config (stdio transport):
- command: `uvx`
- args: ["cronometer-api-mcp"]
- required environment variables:
- `CRONOMETER_USERNAME`: Cronometer account email/username. (example: `<your-email>`)
- `CRONOMETER_PASSWORD`: Cronometer account password. (example: `<your-password>`)
Note: The default/local MCP setup uses stdio via uvx. The README also documents remote deployment modes using MCP_TRANSPORT=sse or streamable-http with additional optional auth and OAuth environment variables, but the simplest portable install path is the stdio configuration.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.CRONOMETER_USERNAMErequiredCronometer account emailCRONOMETER_PASSWORDrequiredCronometer account passwordMeta Ads MCP (Facebook + Instagram) - analyze performance, manage budgets, pause campaigns.