mijneetmeter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Bind address for --http mode. Equivalent to --host. | 127.0.0.1 |
| MCP_PORT | No | Port for --http mode. Equivalent to --port. | 8765 |
| EETMETER_EMAIL | Yes | Mijn Eetmeter login email address (required). | |
| MCP_AUTH_TOKEN | No | Bearer token required on --http requests. Required when binding to a non-loopback host. | |
| EETMETER_PASSWORD | Yes | Mijn Eetmeter password (required). | |
| EETMETER_SEARCH_MAX_RESULTS | No | Cap on the number of search_food results. | 20 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Unofficial tools for the Mijn Eetmeter food diary of the Dutch Voedingscentrum. Dates are DD-MM-YYYY. Meal moments are ontbijt, lunch, avondeten, tussendoor. Search before adding a product.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_foodA | Search for food products by name in the Mijn Eetmeter database. Returns products with Id, Type and SynonymId, which add_food needs. |
| get_diaryA | Read the diary entries for one date and meal moment. |
| get_diary_dayA | Read the diary entries of a full day. Returns {ontbijt, lunch, avondeten, tussendoor}, each a list of entries with product, amount, unit and kcal. |
| add_foodA | Add a food item to the diary. Call search_food first to get product_id, product_type and synonym_id. The result lists the units the product supports (units_available) and which one was used. |
| delete_foodB | Delete a diary entry by its consumption_id (from get_diary or get_diary_day). |
| get_favoritesB | Get the user's favourite food products. |
| todayA | Get today's date in DD-MM-YYYY format (the format the diary tools use). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools have clearly distinct resource+action targets (search_food, add_food, delete_food, get_favorites), and the search→add dependency is explicitly documented. The only real overlap is get_diary (single date + meal moment) versus get_diary_day (full day), which the descriptions do clarify but which could still be misselected by a hurried agent.
Six of seven tools follow a clean verb_noun snake_case pattern (search_food, get_diary, get_diary_day, add_food, delete_food, get_favorites). The outlier is 'today', which has no verb and breaks the pattern, a minor but noticeable deviation.
Seven tools is well-scoped for a food-diary server: discovery, day/meal reading, write, delete, favorites, and a date helper. Each tool earns its place with no redundancy or filler.
The surface covers search, read, create, and delete, but there is no update operation to change an entry's amount or unit, forcing agents to delete and re-add for edits. There is also no way to retrieve daily nutrition totals or meal-level aggregates, which limits the stated diary-management domain.