mcpField
C
Calorie Tracker MCP Server

Calorie Tracker MCP Server

Local
github.com/thitiph0nHealth4Updated 55w ago

About Calorie Tracker MCP Server

Calorie Tracker MCP Server is a calorie and profile tracking server for people monitoring food intake and body metrics. It records food macros and calculates BMR and TDEE with the Mifflin-St Jeor equation.

Key features

  1. 01Food entries with macros
  2. 02BMR and TDEE calculations
  3. 03Profile and activity updates
  4. 04Weight and body composition history
  5. 05OAuth 2.1 with PKCE

Use cases

  1. 01Logging daily food intake
  2. 02Estimating energy needs from profile data
  3. 03Reviewing weight and body composition trends

MCP support

Exposes food-entry, profile, history, and user administration tools to MCP clients. Authentication uses OAuth 2.1 with PKCE support.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"calorie-tracker": {
"command": "npx",
"args": [
"-y",
"wrangler"
]
}
}
}
Run commandnpx -y wrangler

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmwrangler

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Calorie Tracker MCP Server

Calorie Tracker MCP Server

MCP server for tracking daily calorie intake with accurate BMR/TDEE calculations. Built on Cloudflare Workers with D1 database.

Features

  • Food Tracking: Add, update, delete food entries with macros
  • Profile Management: BMR/TDEE calculations using Mifflin-St Jeor equation
  • Historical Data: Track weight, body composition over time
  • Secure: OAuth 2.1 authentication with PKCE support

Quick Setup

pnpm install

# Create resources and update wrangler.jsonc with IDs
npx wrangler d1 create calorie-tracker
npx wrangler kv:namespace create OAUTH_KV

# Run migrations and start dev server
npx wrangler d1 migrations apply calorie-tracker --local
pnpm run dev

OAuth Client Registration

Set an admin API key:

# Development: Update wrangler.jsonc vars.ADMIN_API_KEY
# Production: Use secrets
npx wrangler secret put ADMIN_API_KEY

Register an OAuth client to obtain credentials:

curl -X POST http://localhost:8787/oauth/register \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_ADMIN_API_KEY" \
  -d '{
    "client_name": "Claude Desktop",
    "redirect_uris": ["http://127.0.0.1/callback", "http://localhost/callback"],
    "user_id": "admin"
  }'

Note: Claude Desktop will specify its callback URL during the OAuth flow. If you get a redirect URI mismatch error, check Claude Desktop's OAuth logs for the actual callback URL it expects.

Response:

{
  "client_id": "uuid-client-id",
  "client_secret": "generated-secret",
  "client_name": "Claude Desktop"
}

Claude Configuration

Option 1: Bearer Token (Personal/Pro/Max)

Simple authentication using client secret as bearer token:

  1. Register OAuth client:

    curl -X POST http://localhost:8787/oauth/register \
      -H "Content-Type: application/json" \
      -H "X-API-Key: YOUR_ADMIN_API_KEY" \
      -d '{
        "client_name": "Claude Desktop",
        "redirect_uris": ["https://claude.ai/api/mcp/auth_callback"],
        "user_id": "admin"
      }'
    

    Save the client_secret from response.

  2. Claude Desktop config (claude_desktop_config.json):

    {
      "mcpServers": {
        "calorie-tracker": {
          "command": "npx",
          "args": ["mcp-remote", "http://localhost:8787/sse"],
          "env": {
            "BEARER_TOKEN": "<client_secret from registration>"
          }
        }
      }
    }
    
Option 2: OAuth with Client Credentials (Team/Enterprise Only)

Private connector with Client ID/Secret:

  1. Register OAuth client with callback URL https://claude.ai/api/mcp/auth_callback

  2. Add custom connector in Claude:

    • Name: Calorie Tracker
    • Remote MCP server URL: https://YOUR-WORKER.workers.dev/sse
    • OAuth Client ID: <client_id from registration>
    • OAuth Client Secret: <client_secret from registration>
Production Deployment

Deploy to Cloudflare Workers for mobile/web access:

pnpm run deploy
pnpm run migrate
npx wrangler secret put ADMIN_API_KEY

Tools

Food Tracking:

  • list_entries - List food entries with pagination
  • add_entry - Add food entry with macros
  • update_entry - Update existing entry
  • delete_entry - Delete entry

Profile Management:

  • get_profile - Get profile with BMR/TDEE calculations
  • update_profile - Update profile data (height, weight, activity level)
  • get_profile_history - Historical tracking data

Admin:

  • register_user - Register new user
  • revoke_user - Revoke user access

BMR/TDEE Calculations

Uses Mifflin-St Jeor equation (gold standard):

Male: BMR = (10 × weight) + (6.25 × height) - (5 × age) + 5
Female: BMR = (10 × weight) + (6.25 × height) - (5 × age) - 161

TDEE: BMR × Activity Multiplier (1.2 - 1.9)

Development

pnpm test           # Run tests
pnpm run type-check # TypeScript validation
pnpm run deploy     # Deploy to production
pnpm run migrate    # Run migrations on remote

Tech Stack

  • Runtime: Cloudflare Workers
  • Database: D1 (SQLite)
  • Language: TypeScript
  • Validation: Zod
  • Testing: Vitest

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.