Fitatu MCP Unofficial

Unofficial Model Context Protocol (MCP) server for Fitatu. It exposes selected Fitatu account operations as typed MCP tools so an MCP client can inspect and update your own meal plan.

[!IMPORTANT] This project is not affiliated with, endorsed by, or sponsored by Fitatu. Fitatu credentials and account data are sensitive. Use this server only with your own account.

Features

• Streamable HTTP MCP endpoint at /mcp.
• Fitatu authentication through local environment variables.
• Safe profile and day-plan read tools.
• Diet summary tool for an inclusive date range, including period energy, key nutrients, and full nutrient details.
• Food search with product and measure identifiers for follow-up mutations.
• Meal item add, update, move, and remove tools.
• Docker workflow for local/private deployment.

Requirements

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

Quick Start

Install dependencies:

npm install

Create local configuration:

cp .env.example .env

Fill in FITATU_EMAIL and FITATU_PASSWORD in .env, then start the development server:

npm run dev

The MCP endpoint is available at:

http://localhost:3000/mcp

MCP Client Setup

If your MCP client supports remote Streamable HTTP servers, use this endpoint directly:

http://localhost:3000/mcp

For clients that launch MCP servers through a command, use mcp-remote:

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

When using a public tunnel, replace the local URL with the tunnel URL and keep the /mcp path.

To test the server manually in a browser-based tool, run the MCP Inspector and connect it to the Streamable HTTP endpoint:

npx @modelcontextprotocol/inspector

Use this URL in the Inspector:

http://localhost:3000/mcp

Available Tools

Tool	Purpose	Mutates Fitatu data
get_current_user	Returns a safe subset of the authenticated Fitatu user profile.	No
get_day_plan_items	Returns meals and food items for a YYYY-MM-DD date.	No
get_diet_summary	Returns an agent-friendly nutrition and energy summary for an inclusive date range.	No
search_food	Searches Fitatu food catalogs for product, recipe, and measure identifiers.	No
add_meal_items	Adds one or more products or recipes to a meal.	Yes
update_meal_item	Updates quantity, measure, or eaten state for an existing meal item.	Yes
move_meal_item	Moves a meal item to another meal, date, or both.	Yes
remove_meal_items	Removes active product meal items by productIds across the whole day.	Yes

Typical workflow:

1. Call get_day_plan_items to inspect available meals, items, and canonical string productId values for a specific day.
2. Call search_food to find a matching foodId, foodType, and measureId.
3. Call add_meal_items with the canonical foodId and measureId strings (plus foodType when available), or use another mutation tool. Pass productId strings from get_day_plan_items directly to remove_meal_items.productIds.
4. After add_meal_items returns accepted, wait for synchronization and call get_day_plan_items again. Treat accepted only as confirmation that Fitatu accepted the synchronization request, and verify that each requested item is present before reporting that it was added.

An agent may also use get_diet_summary to fetch periodic diet data and track nutrition over time.

Fitatu applies some mutations asynchronously, so a very fast follow-up read may briefly return the previous state. An accepted synchronization request can still omit an individual item when its foodId, measureId, or foodType is not recognized by Fitatu.

Configuration

Runtime configuration is read from environment variables and validated at startup.

Variable	Required	Default	Sensitive	Description
FITATU_EMAIL	Yes	none	Yes	Fitatu account email address.
FITATU_PASSWORD	Yes	none	Yes	Fitatu account password.
PORT	No	3000	No	HTTP server port.
NODE_ENV	No	development	No	development, production, or test.
SERVER_NAME	No	fitatu-mcp	No	MCP server name.
SERVER_VERSION	No	1.0.0	No	MCP server version.
LOG_LEVEL	No	info	No	error, warn, info, or debug.

Do not commit .env. The repository keeps .env.example as documentation only.

Local Development

Start the server in watch mode:

npm run dev

Build the project:

npm run build

Start the built server:

npm start

Run quality checks:

npm run lint
npm run format:check
npm run test:ci
npm run build

Integration tests require valid Fitatu credentials in .env and may read or mutate data in the authenticated account.

Docker

Create .env before building the image:

cp .env.example .env

Fill in your Fitatu credentials in .env.

Build the Docker image:

docker build -t fitatu-mcp .

The build copies .env into the image so the server can read it at runtime. Treat the built image as sensitive. Do not push it to a public registry or share it with other people.

Run the container:

docker run --name fitatu-mcp -p 3000:3000 fitatu-mcp

If a container with that name already exists, recreate it:

docker stop fitatu-mcp
docker rm fitatu-mcp
docker run --name fitatu-mcp -p 3000:3000 fitatu-mcp

Exposing a Local Server with Cloudflare Tunnel

When the server is running locally on port 3000, expose it through a temporary Cloudflare Tunnel:

cloudflared tunnel --url http://localhost:3000

Cloudflare will print a public tunnel URL. Use that URL with the /mcp path as the MCP endpoint.

Security Notes

• Use this server only with your own Fitatu account.
• Do not commit Fitatu credentials, tokens, cookies, account identifiers, nutrition logs, body measurements, or profile data.
• Do not expose full upstream Fitatu responses in issues, logs, tests, fixtures, or MCP responses.
• Captured HTTP traffic should be used only for legitimate work with your own account and your own network traffic.
• Review mutation tool calls carefully before allowing an MCP client to execute them.

Contributing

See CONTRIBUTING.md for contribution guidelines.

License

This project is licensed under the MIT License.