Nutrition MCP

A remote MCP server for personal nutrition tracking — log meals with calories, macros, fiber, total sugar and caffeine, log water and body weight, review nutrition history, and import an existing food diary from another app, all through conversation. Alcohol tracking is opt-in and off by default.

Help me pay for the servers on Patreon

Table of Contents

• Quick Start

• Demo

• Tech Stack

• MCP Tools

• MCP Resources

• Self-hosting

  • 0. Get the code

  • 1. Supabase setup

  • 2. Environment variables

  • 3. Google sign-in (optional)

• Development

  • Testing and quality

• Connect to Claude.ai

• API Endpoints

• Deploy

• License

Related MCP server: nutrition-mcp

Quick Start

Already hosted and ready to use — just connect it to your MCP client:

https://nutrition-mcp.com/mcp

On Claude.ai: Customize → Connectors → + → Add custom connector → paste the URL → Connect (see Connect to Claude.ai below for the full walkthrough)

On first connect you'll be asked to register with an email and password. Your data persists across reconnections.

Switching from another tracker? See the nutrition-app alternatives — how it compares to MyFitnessPal, Cronometer, Lose It!, MacroFactor, Yazio, and Lifesum. Bring your history with you: say "import my meals" and an importer opens in the chat, where you pick the CSV you exported from your old app, map its columns, and check what will be added before anything is saved. Exports from MyFitnessPal, Cronometer, Lose It! and MacroFactor are recognised automatically; any other CSV works by mapping its columns yourself. In clients that can't show in-chat panels, paste the export instead and the AI imports it for you. If your export has an alcohol column and you want it kept, turn alcohol tracking on before importing — the importer skips that column while tracking is off, and re-importing the same file later won't backfill it.

Demo

Read the story behind it: How I Replaced MyFitnessPal and Other Apps with a Single MCP Server

Tech Stack

• Bun — runtime and package manager

• Hono — HTTP framework

• MCP SDK — Model Context Protocol over Streamable HTTP

• Supabase — PostgreSQL database + user authentication

• OAuth 2.0 — authentication for Claude.ai connectors

MCP Tools

MCP Resources

Self-hosting

0. Get the code

git clone https://github.com/akutishevsky/nutrition-mcp.git
cd nutrition-mcp
bun install
cp .env.example .env   # fill in real values as you go through the steps below

Requires Bun 1.x (matches the Dockerfile's oven/bun:1 base image; no exact minor version is pinned).

Making it yours: The public site includes the maintainer's personal bits — Google Analytics, Patreon/GitHub/contact links, and the nutrition-mcp.com domain. Run bun run gen:all to produce the public pages, then bun run depersonalize to strip the personal bits in one pass (analytics + CSP, the Support/Contact sections, social links, and the domain → a your-domain.com placeholder). Use bun run depersonalize --dry to preview without writing. Afterwards, swap in your own public/og.png, favicon.ico, and apple-touch-icon.png, and replace the domain placeholder with your real domain. This script only touches public/*.html and src/index.ts — it doesn't touch this README, so if you're publishing your own fork, also edit or remove the Patreon line near the top of this file and the Medium link in Demo.

1. Supabase setup

1. Create a Supabase project.

2. Enable Email Auth (Authentication → Providers → Email) and disable email confirmation.

3. Apply the schema. The full schema lives in supabase/migrations/. With the Supabase CLI:

   supabase link --project-ref <your-project-ref>
   supabase db push

   This creates every table, index, RLS policy, and foreign key the app needs. No local Postgres is involved — migrations run against your hosted project.

4. Copy the service role key from Project Settings → API and use it as SUPABASE_SECRET_KEY.

2. Environment variables

Generate OAuth credentials:

bun run generate-oauth-creds

or manually:

openssl rand -hex 16   # use as OAUTH_CLIENT_ID
openssl rand -hex 32   # use as OAUTH_CLIENT_SECRET

Patreon posts, one-time setup: PATREON_ACCESS_TOKEN / PATREON_REFRESH_TOKEN are only ever read once, at server boot, to seed the patreon_tokens table if it's still empty — the server refreshes and stores its own pair from then on, so leaving these two set permanently is safe (every later boot is a no-op). You never need to touch the database by hand.

3. Google sign-in (optional)

Email/password works out of the box. To also offer "Continue with Google", follow docs/google-auth-setup.md to create a Google OAuth client, enable the Google provider in Supabase, and set GOOGLE_CLIENT_ID / GOOGLE_CLIENT_SECRET. This adds the GET /authorize/google and GET /auth/google/callback routes — see API Endpoints.

Development

bun install
cp .env.example .env   # fill in your credentials — see Self-hosting above for what to put here
bun run dev             # regenerates public/ pages, then starts with hot reload on http://localhost:8080

The generated pages under public/ (index, tools, privacy, terms, login, /alternatives, locale mirrors, sitemap.xml) are build artifacts, not tracked in git — they're regenerated on every Docker build, in CI, and once at each bun run dev start. --watch only restarts the src/index.ts process on save, so it does not rerun generation — after editing src/copy/, src/routes.ts, or scripts/site-partials.ts, run bun run gen:all yourself to pick up the change.

Testing and quality

bun test                # run the test suite
bun run format           # format with Prettier (4-space indentation)
bun run format:check     # verify the tree is prettier-clean
bun run typecheck        # typecheck src/

CI runs format:check and typecheck on every PR; typecheck is scoped to src/, so a type error in a test file or under scripts/ won't be caught by it.

For in-chat widget development (public/widgets/), bun run harness starts a local host simulator so you can test widgets without a real MCP client.

Connect to Claude.ai

1. Open Claude.ai and click Customize

2. Click Connectors, then the + button

3. Click Add custom connector

4. Fill in:

   • Name: Nutrition Tracker

   • Remote MCP Server URL: https://nutrition-mcp.com/mcp

5. Click Connect — sign in or register when prompted

6. After signing in, Claude can use your nutrition tools. If you reconnect later, sign in with the same email and password to keep your data.

API Endpoints

Deploy

The project includes a Dockerfile for container-based deployment.

1. Push your repo to a hosting provider (e.g. DigitalOcean App Platform)

2. Set the environment variables listed above

3. The app auto-detects the Dockerfile and deploys on port 8080

4. Point your domain to the deployed URL

License

MIT