Fitatu MCP Unofficial MCP server

Fitatu MCP Unofficial

Unofficial Model Context Protocol (MCP) server for accessing and updating data in your own Fitatu account. It provides typed tools for profile data, meal plans, nutrition summaries, food search, and recipe management over stdio or Streamable HTTP.

[!IMPORTANT]

This project is not affiliated with, endorsed by, or sponsored by Fitatu. Use it only with your own account and treat Fitatu credentials and account data as

sensitive.

Features

• Profile, day-plan, and nutrition summary queries.
• Latest or date-specific body measurement lookup and partial updates for explicit calendar dates.
• Food and recipe search with identifiers required by mutation tools.
• Meal item creation, update, replacement, movement, and removal.
• Recipe creation, inspection, update, and deletion.
• MCP transports for local stdio and Streamable HTTP clients.
• Local development and Docker workflows.

Requirements

• Node.js >=22.18.0
• npm
• A Fitatu account

Docker and ngrok are optional and required only for their respective workflows.

Quick start

Install dependencies and create the local configuration file:

npm install
cp .env.example .env

Set FITATUEMAIL and FITATUPASSWORD in .env, then start the development server:

npm run dev

The default MCP endpoint is http://localhost:3000/mcp.

MCP client configuration

Choose one transport with MCP_TRANSPORT:

stdio

Build the server before configuring the client:

npm run build

Use absolute paths to the repository's .env and dist/index.js files:

{
	"mcpServers": {
		"fitatu": {
			"command": "node",
			"args": [
				"--env-file=/absolute/path/to/fitatu-mcp-unofficial/.env",
				"/absolute/path/to/fitatu-mcp-unofficial/dist/index.js"
			],
			"env": {
				"MCP_TRANSPORT": "stdio"
			}
		}
	}
}

The client starts and stops the server. In stdio mode, logs are written to stderr because stdout is reserved for the JSON-RPC stream.

Streamable HTTP

Start the server with npm run dev, or build and run it with:

npm run build
npm start

Clients with native Streamable HTTP support can connect directly to:

http://localhost:3000/mcp

For a client that launches remote MCP connections through a command, use mcp-remote:

{
	"mcpServers": {
		"fitatu": {
			"command": "npx",
			"args": ["mcp-remote", "http://localhost:3000/mcp"]
		}
	}
}

To inspect the local server interactively:

npm run inspector

Connect the Inspector to http://localhost:3000/mcp.

Remote MCP access with ngrok

Install and authenticate ngrok. In .env, configure two different Fitatu accounts using FITATU and FITATUINTEGRATION_*, then add your assigned domain:

NGROK_DOMAIN=your-assigned-domain.ngrok-free.dev

npm run dev:all           # Both accounts and the tunnel
npm run dev:test-account # Test account only (alternative)

In any MCP client that supports remote Streamable HTTP connections, use one of these URLs without authentication:

• Personal: https://YOURNGROKDOMAIN/personal/mcp
• Test: https://YOURNGROKDOMAIN/test/mcp

Addresses stay the same after restarting. Keep the command running; Ctrl+C stops everything. Optional port settings are in .env.example.

Anyone with the URL can access that account while the tunnel runs. Use it only for temporary development sessions.

Available tools

Shortened. The full README is on GitHub.