[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Fitatu API and MCP server

> Fitatu has no public API: its site and help center list no developer docs and no official MCP server (checked 13 Oct 2026). The only data paths are two-way sync with Google Health Connect and Apple Health on the phone, and links that bring workouts in from Strava, Garmin Connect and Polar Flow.

Calorie counter and food diary app from Poland: a database of over a million products and meals, a barcode scanner, daily calorie and macro goals, water, body measurements and meal planning.

## What is the Fitatu API?

Cotlet's Fitatu API exposes 11 endpoints for your own Fitatu account: get diary, search food, get nutrition summary, get daily goals, list measurements, get water, log food, log quick entry, delete diary item, copy day and log measurement. The get_diary endpoint returns everything logged on one day, grouped by meal, with calories and macros per entry and for the day. Each endpoint takes simple JSON inputs like date, limit or from and works both as an operation of the fitatu_read or fitatu_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Health & fitness](https://cotlet.dev/integrations/category/health-fitness.md)
- **Endpoints:** 11 (6 read, 5 write)
- **Updated:** 2026-10-20

Fitatu has no public API: its site and help center list no developer docs and no official MCP server (checked 13 Oct 2026). Cotlet is a hosted MCP server and REST API for Fitatu with 11 endpoints (6 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Fitatu have an official API?

Fitatu has no public API: its site and help center list no developer docs and no official MCP server (checked 13 Oct 2026). The only data paths are two-way sync with Google Health Connect and Apple Health on the phone, and links that bring workouts in from Strava, Garmin Connect and Polar Flow.

| Task | Fitatu official | Cotlet |
|---|---|---|
| Read the food diary for a day | Partly: Fitatu sends meals to Health Connect and Apple Health on the phone, with no way to read them from code | Yes |
| Search the food database | No | Yes |
| Log a food in a meal | No | Yes |
| Quick add calories and macros | No | Yes |
| Copy a day to another day | No | Yes |
| Read calorie and macro totals for a period | Partly: Same phone sync of meals; totals are built in the app only | Yes |
| Log weight and body measurements | No: Fitatu sends weight to Health Connect and Apple Health but does not import it from other apps | Yes |
| Read daily calorie and macro goals | No | Yes |

Sources: [Fitatu Help: Can Fitatu sync with other devices and apps?](https://www.fitatu.com/en/help/can-fitatu-sync-with-other-devices-and-apps), [Fitatu Help: Can I import weight data from smart scales or synced apps?](https://www.fitatu.com/en/help/can-i-import-weight-data-from-smart-scales-or-synced-apps-into-fitatu), [Fitatu Help: Is Fitatu available on desktop?](https://www.fitatu.com/en/help/is-fitatu-available-on-desktop), [Fitatu Help center](https://www.fitatu.com/en/help)

## For AI agents

```text
Fitatu has no public API: its site and help center list no developer docs and no official MCP server (checked 13 Oct 2026). The only data paths are two-way sync with Google Health Connect and Apple Health on the phone, and links that bring workouts in from Strava, Garmin Connect and Polar Flow.
Cotlet provides a hosted MCP server and REST API for Fitatu: 11 tools (6 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=fitatu, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    fitatu_read, fitatu_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/fitatu, each operation at its own route, e.g. POST /api/v1/fitatu/quick-entries
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   get_diary, search_food, get_nutrition_summary, get_daily_goals, list_measurements, get_water, log_food, log_quick_entry, delete_diary_item, copy_day, log_measurement
Confirm      delete_diary_item, copy_day, log_measurement (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/fitatu-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=fitatu, requests Fitatu in the Cotlet console and creates an API key there.
2. The user signs in to Fitatu once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Fitatu for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Fitatu server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Fitatu in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Fitatu only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Fitatu login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Fitatu's terms; Cotlet is not affiliated with Fitatu.
```

## What can an AI agent do in Fitatu?

Cotlet is best for Fitatu Premium users who track food and weight and want their AI agent to log entries and report weekly totals without running or fixing a server.

- **[Log your weight automatically](https://cotlet.dev/integrations/fitatu-api-mcp-server/log-weight-automatically.md)** (runs: daily): "Log 81.4 as my weight in Fitatu for today, skip it if I already logged one, and tell me my change over the last 14 days." → `list_measurements`, `log_measurement`
- **[Log diet catering meals in bulk](https://cotlet.dev/integrations/fitatu-api-mcp-server/log-diet-catering-meals.md)** (runs: weekly): "Here is this week's catering menu with calories and macros per meal. Add each meal to Fitatu on its day and tell me the daily totals." → `get_diary`, `log_quick_entry`
- **[Export your food diary to a spreadsheet](https://cotlet.dev/integrations/fitatu-api-mcp-server/export-food-diary-to-spreadsheet.md)** (runs: weekly): "Every Monday, pull last week's calories and macros from Fitatu, compare them with my daily goal and give me rows to append to my sheet." → `get_nutrition_summary`, `get_daily_goals`, `get_diary`
- **Copy a day of meals to another day** (runs: weekly): "Copy everything I ate last Monday to this Monday, then show me the diary for that day." → `copy_day`, `get_diary`
- **Log a meal from a description**: "I had two eggs, a slice of rye bread and a coffee with milk for breakfast today. Find them in the Fitatu database and log them." → `search_food`, `log_food`, `get_diary`

## Can Fitatu automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Fitatu connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to log your weight automatically, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/fitatu/measurements. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/fitatu/measurements with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 11 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Fitatu.

### get_diary

Everything logged on one day, grouped by meal, with calories and macros per entry and for the day. Access: read. REST: `GET /api/v1/fitatu/diary`. MCP: `fitatu_read → get_diary`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `date` | date | no | Day to read, YYYY-MM-DD. Default: today. |

Returns the food diary for one day, meal by meal, in the order of your meal scheme. Each entry has an item_id, the amount you logged and its calories, protein, fat and carbohydrates. Totals cover the whole day. Use item_id with delete_diary_item.

Example response:

```json
{
  "date": "2026-10-13",
  "meals": [
    {
      "meal": "breakfast",
      "items": [
        {
          "item_id": "it_5c20",
          "name": "Rye bread",
          "amount": "2 slices",
          "kcal": 160,
          "protein_g": 6,
          "fat_g": 2,
          "carbs_g": 30
        },
        {
          "item_id": "it_5c21",
          "name": "Egg",
          "amount": "2 pieces",
          "kcal": 144,
          "protein_g": 12,
          "fat_g": 10,
          "carbs_g": 1
        }
      ]
    }
  ],
  "totals": {
    "kcal": 304,
    "protein_g": 18,
    "fat_g": 12,
    "carbs_g": 31
  }
}
```

### search_food

Search the Fitatu database of products and meals, with calories and macros per 100 g or 100 ml. Access: read. REST: `GET /api/v1/fitatu/foods/search`. MCP: `fitatu_read → search_food`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Product or meal name, e.g. "rye bread". |
| `database` | enum | no | Polish, English, Dutch, French, Italian, German or Spanish. Default: the database set on your account. |
| `from_fitatu_only` | boolean | no | Only generic products from Fitatu, not tied to a brand. |
| `limit` | integer | no | 1 to 50. Default: 20. |

Searches the Fitatu product and meal database, which holds over a million entries from raw basics to restaurant meals. Choose the database country, or limit results to products from Fitatu, the generic entries checked by its dietitians. Pass food_id to log_food. Results are ranked as the app ranks them.

Example response:

```json
{
  "foods": [
    {
      "food_id": "fd_88a1",
      "name": "Rye bread",
      "brand": null,
      "kcal_per_100": 259,
      "protein_g_per_100": 8.5,
      "fat_g_per_100": 3.3,
      "carbs_g_per_100": 48,
      "measures": [
        "slice",
        "gram"
      ]
    }
  ],
  "next_cursor": null
}
```

### get_nutrition_summary

Total and average calories, protein, fat and carbs for a date range, with the gap to your goal. Access: read. REST: `GET /api/v1/fitatu/nutrition-summary`. MCP: `fitatu_read → get_nutrition_summary`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | yes | First day, YYYY-MM-DD. |
| `to` | date | yes | Last day, YYYY-MM-DD. |

Returns the same balance the Summary view shows: total and average calorie intake and macros over the period, and the difference to your calorie goal. Free Fitatu accounts can read 1 to 7 days. Premium and Premium+AI accounts can read any period. Totals can be underestimated when manufacturers give incomplete data.

Example response:

```json
{
  "from": "2026-10-06",
  "to": "2026-10-12",
  "days": 7,
  "total_kcal": 14420,
  "average_kcal": 2060,
  "goal_kcal": 2150,
  "vs_goal_kcal": -630,
  "protein_g": 880,
  "fat_g": 484,
  "carbs_g": 1636
}
```

### get_daily_goals

Your calorie and macro goals, as set under Settings > Goals > Daily Goals. Access: read. REST: `GET /api/v1/fitatu/daily-goals`. MCP: `fitatu_read → get_daily_goals`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `date` | date | no | Day to read, YYYY-MM-DD. Default: today. |

Returns the daily calorie goal and the protein, fat and carbohydrate goals for your account. On Premium and Premium+AI, where goals can differ per weekday, pass date to get the goal for that day.

Example response:

```json
{
  "date": "2026-10-13",
  "kcal": 2150,
  "protein_g": 130,
  "fat_g": 70,
  "carbs_g": 250
}
```

### list_measurements

Weight and body measurements you logged, newest first, from the Measurements tab. Access: read. REST: `GET /api/v1/fitatu/measurements`. MCP: `fitatu_read → list_measurements`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | string | no | Measurement type, e.g. weight, body_fat or waist. Default: all. |
| `from` | date | no | Only entries on or after this date. |
| `to` | date | no | Only entries on or before this date. |
| `limit` | integer | no | 1 to 100. Default: 30. |

Lists entries from the Measurements tab, newest first. Types include weight, height, BMI, body fat, circumferences such as waist and hips, and metrics you defined. BMI is calculated by Fitatu. Filter by type and by date range.

Example response:

```json
{
  "measurements": [
    {
      "measurement_id": "ms_2209",
      "type": "weight",
      "value": 81.9,
      "unit": "kg",
      "date": "2026-10-12"
    },
    {
      "measurement_id": "ms_2201",
      "type": "weight",
      "value": 82.3,
      "unit": "kg",
      "date": "2026-10-09"
    }
  ],
  "next_cursor": null
}
```

### get_water

Water you logged for a day, your daily requirement and your glass size. Access: read. REST: `GET /api/v1/fitatu/water`. MCP: `fitatu_read → get_water`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `date` | date | no | Day to read, YYYY-MM-DD. Default: today. |

Returns the water you logged for one day, the requirement Fitatu calculated from your setup data and the glass size set under Settings > Water. The requirement rises on days when you log a workout.

Example response:

```json
{
  "date": "2026-10-13",
  "drunk_ml": 1250,
  "requirement_ml": 2400,
  "glass_ml": 250
}
```

### log_food

Add a product or meal from the database to a meal on a day. Access: write. REST: `POST /api/v1/fitatu/foods/{food_id}`. MCP: `fitatu_write → log_food`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `food_id` | string | yes | Product or meal ID from search_food. |
| `meal` | string | yes | Meal name from your Fitatu meal scheme. By default: breakfast, second breakfast, lunch, dinner, snack or supper. |
| `amount` | number | yes | How much, in the unit below. |
| `unit` | string | yes | gram, milliliter or a measure the product lists, e.g. slice, teaspoon, handful or package. |
| `date` | date | no | Day to log on, YYYY-MM-DD. Default: today. |

Adds one product or meal from search_food to the chosen meal and day, in grams, milliliters or a handy measure the product offers, such as a slice or a package. It reaches no one and is undone with one call, delete_diary_item, so it runs without asking first.

Example response:

```json
{
  "item_id": "it_5c20",
  "date": "2026-10-13",
  "meal": "breakfast",
  "name": "Rye bread",
  "amount": "2 slices",
  "kcal": 160,
  "status": "logged"
}
```

### log_quick_entry

Add calories and macros to a meal without picking a product, like Quick add in the app. Access: write. REST: `POST /api/v1/fitatu/quick-entries`. MCP: `fitatu_write → log_quick_entry`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `meal` | string | yes | Meal name from your Fitatu meal scheme. By default: breakfast, second breakfast, lunch, dinner, snack or supper. |
| `kcal` | number | yes | Calories of the entry. |
| `protein_g` | number | no | Protein in grams. |
| `fat_g` | number | no | Fat in grams. |
| `carbs_g` | number | no | Carbohydrates in grams. |
| `date` | date | no | Day to log on, YYYY-MM-DD. Default: today. |

Enters nutrition values straight into a meal, the way Quick add does: useful for diet catering or values copied from a label. The entry is not saved to your Own list. It reaches no one and is undone with one call, delete_diary_item, so it runs without asking first.

Example response:

```json
{
  "item_id": "it_7a31",
  "date": "2026-10-14",
  "meal": "lunch",
  "kcal": 624,
  "protein_g": 38,
  "fat_g": 24,
  "carbs_g": 64,
  "status": "logged"
}
```

### delete_diary_item

Remove one entry from a day in the diary. Access: write, asks the user first. REST: `DELETE /api/v1/fitatu/items/{item_id}/diary-items`. MCP: `fitatu_write → delete_diary_item`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `item_id` | string | yes | Diary entry ID from get_diary. |

Removes a single product or meal entry, the same as tapping the X on its card. The entry is gone from that day, and logging it again is a new call. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "item_id": "it_5c21",
  "status": "deleted"
}
```

### copy_day

Copy all meals of one day to another day. Premium and Premium+AI. Access: write, asks the user first. REST: `POST /api/v1/fitatu/day/copy`. MCP: `fitatu_write → copy_day`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from_date` | date | yes | Day to copy from, YYYY-MM-DD. |
| `to_date` | date | yes | Day to copy to, YYYY-MM-DD. |

Transfers all meals from one day to another, the same as Copy Day in the app, which Fitatu lists among its Premium features. Use it to repeat a plan ahead of time. Read the target day with get_diary afterwards. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "from_date": "2026-10-06",
  "to_date": "2026-10-13",
  "items_copied": 9,
  "status": "copied"
}
```

### log_measurement

Add a weight or body measurement for a day to the Measurements tab. Access: write, asks the user first. REST: `POST /api/v1/fitatu/measurements`. MCP: `fitatu_write → log_measurement`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | string | yes | Measurement type, e.g. weight, body_fat or waist. |
| `value` | number | yes | Value in the unit your account uses. |
| `date` | date | no | Day of the measurement, YYYY-MM-DD. Default: today. |

Adds one entry to Measurements, such as weight, body fat or a circumference. Fitatu does not import weight from scales or other apps, so this is how a reading from a script reaches the chart. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "measurement_id": "ms_2210",
  "type": "weight",
  "value": 81.4,
  "unit": "kg",
  "date": "2026-10-13",
  "status": "saved"
}
```

## How do I connect Fitatu to Claude Code, Codex or Cursor?

Connecting Fitatu takes three steps: sign up, sign in to Fitatu once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Fitatu to your agent.

1. **Create an account** Sign up and add Fitatu in the console. Your API key is there too.

2. **Sign in to Fitatu in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Fitatu there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Fitatu tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Log 81.4 as my weight in Fitatu for today, skip it if I already logged one, and tell me my change over the last 14 days.
```

### Call Fitatu from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/fitatu with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/fitatu/quick-entries \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"2026-10-14","meal":"lunch","kcal":624,"protein_g":38,"fat_g":24,"carbs_g":64}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "item_id": "it_7a31",
  "date": "2026-10-14",
  "meal": "lunch",
  "kcal": 624,
  "protein_g": 38,
  "fat_g": 24,
  "carbs_g": 64,
  "status": "logged"
}
```

## Why use Cotlet for Fitatu?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Fitatu yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Fitatu changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Fitatu to Cotlet?

Yes. You sign in to Fitatu yourself, in your own Cloud Browser, and we never save your password. Your agents only get Fitatu once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Fitatu integration?**

No, Cotlet is independent of Fitatu. Fitatu has no public API. Cotlet works through your own Fitatu account, the way you use Fitatu in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Fitatu in your console: your agents lose access at once and you stay signed in. Signing out of Fitatu in the browser works too, and Reset browser deletes the whole profile.

## Is there a Fitatu MCP server on GitHub?

Without an API, Fitatu users log by hand in the app. Phone sync with Health Connect or Apple Health moves meals and weight out of Fitatu, but not in, and it cannot be driven from an agent. Cotlet signs in to your Fitatu account and does the logging and reading for you.

|  | By hand in the app | Cotlet |
|---|---|---|
| Setup | Install the app, open the diary, tap + on each meal | Sign up, sign in to Fitatu once, add one MCP server or API key |
| When Fitatu changes | You learn the new screens yourself | Our team tests it daily and fixes it for you; failed calls are free |
| Your Fitatu session | Signed in on your phone | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | You sign in again in the app | Your Cloud Browser keeps you signed in; if Fitatu logs you out, your agent gets a link to sign in again |
| Upkeep | Typing every weight and catering meal, every day | Nothing to host or update |
| Where it runs | Your phone, when you remember | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Fitatu changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Fitatu API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Fitatu API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Fitatu account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Fitatu yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Fitatu only after you enable it. When Fitatu signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Fitatu, sign out of Fitatu in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Fitatu's terms:** You use your own Fitatu account and stay responsible for following Fitatu's terms. Cotlet is independent and not affiliated with Fitatu. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Fitatu in the console and press Request access. Then you create your API key and connect Fitatu there.

**Do I need to be technical?**

No. You sign in to Fitatu once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Fitatu to Cotlet?**

Yes. You sign in to Fitatu yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Fitatu once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Fitatu sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Fitatu cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Fitatu's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Fitatu sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Fitatu login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Fitatu offers no OAuth or API for this, so there is no scoped token to hold. That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need Fitatu Premium to use Cotlet with Fitatu?**

Yes. Cotlet works through your Fitatu account in the browser, and Fitatu offers its web version, with limited functionality, on the Premium and Premium+AI plans. Copy Day and summaries longer than 7 days are Premium features as well.

**Which food database does search_food use?**

The Fitatu database of over a million products and meals. You can search the Polish, English, Dutch, French, Italian, German or Spanish database, or only the generic products Fitatu checks with its dietitians.

**Can my agent post or send messages in Fitatu without asking me?**

No. Every call to delete_diary_item, copy_day or log_measurement waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. log_food, log_quick_entry runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Fitatu API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/fitatu from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.