MyFitnessPal MCP server

myfitnesspal-mcp

Connect MyFitnessPal to Claude or any MCP client. Log meals by talking, search the food database with macros, track trends, and export your nutrition history, all against your real MyFitnessPal diary.

Published on PyPI as mfp-mcp.

<!-- mcp-name: io.github.Mason-Levyy/mfp-mcp -->

Unofficial. MyFitnessPal has no public API; this reverse-engineers the

web app's own endpoints. It can break whenever MFP changes their site. Use at

your own risk, with your own account.

Why this one?

MyFitnessPal moved behind Cloudflare + NextAuth, which broke the username/password login that most existing integrations rely on. This server:

fingerprint (curl_cffi), which passes Cloudflare.

• Authenticates with your browser session cookie over a real Chrome TLS

the token when it expires, and failed calls retry automatically.

• Auto-refreshes the session (optional): a headless browser profile rotates

• Writes, not just reads: log, modify, and delete real diary entries.
• Search-then-log: get candidates with macros, then log the exact item.

Quickstart

Authentication):

1. Connect your account (one-time; prompts you to paste a cookie — see

uvx mfp-mcp auth

1. Add the server to your client.

Claude Code

claude mcp add myfitnesspal -- uvx mfp-mcp

Claude Desktop (claudedesktopconfig.json)

{
     "mcpServers": {
       "myfitnesspal": {
         "command": "uvx",
         "args": ["mfp-mcp"]
       }
     }
   }

"chart my weight this month".

1. Talk to it: "log a banana as a snack", "what did I eat yesterday?",

Requires uv. Any MCP client that speaks stdio or streamable HTTP works, not just Claude.

Authentication

MyFitnessPal killed headless password login, so this uses your browser's session cookie:

Cookies → https://www.myfitnesspal.com.

1. Log in at myfitnesspal.com.
2. Open DevTools (F12) → Application (Chrome) or Storage (Firefox) →

1. Copy the value of __Secure-next-auth.session-token.
2. Paste it into the mfp-mcp auth prompt (input is hidden).

Pasting the entire Cookie: header from any request in the Network tab also works. Cookies are stored with owner-only permissions in your platform config dir, or supply them via the MFP_COOKIE environment variable instead.

Sessions last around 30 days. When one expires, either re-run auth — or enable auto-refresh so you never have to.

Auto-refresh (recommended)

With the autorefresh extra, auth also seeds a persistent headless browser profile. When MyFitnessPal rejects the session mid-call, the server tells your client it is retrying, boots the profile headlessly, lets MyFitnessPal rotate the session token, saves the fresh cookie, and retries the call.

uvx --from 'mfp-mcp[autorefresh]' playwright install chromium
uvx --from 'mfp-mcp[autorefresh]' mfp-mcp auth

Then use the same --from 'mfp-mcp[autorefresh]' form in your client config (e.g. uvx --from 'mfp-mcp[autorefresh]' mfp-mcp).

Tools

Shortened. The full README is on GitHub.