cronometer-api-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRONOMETER_PASSWORD | Yes | Cronometer account password | |
| CRONOMETER_USERNAME | Yes | Cronometer account email |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_food_log | Get all diary entries for a given date. Returns every food entry logged for the day. Each "Serving" entry is enriched (best-effort) with the food's name, source, the serving measure (unit name and grams per unit), the number of servings, and that food's own nutrient profile scaled to the amount eaten. Non-food entries (exercise, biometrics) carry their own name. Note: the per-entry "nutrients" are each food's individual contribution, which is distinct from the day-level nutrition_summary aggregate below. Also returns a top-level energy_summary field with pre-computed values most relevant to the user:
Also returns a nutrition_summary field with consumed totals for every nutrient the user tracks in Cronometer (macros plus any tracked micronutrients such as saturated fat, cholesterol, or omega-3/6):
Args: date: Date as YYYY-MM-DD (defaults to today). |
| get_daily_nutrition | Get daily nutrition summary with consumed macro and micronutrient totals. Returns the amounts actually consumed for the day, covering every nutrient the user tracks in Cronometer (i.e. has a target set for). The response has:
A nutrient only appears if it's tracked in Cronometer. To surface e.g. saturated fat, cholesterol, or trans fat, set a target for it in Cronometer and it will flow through automatically. Args: date: Date as YYYY-MM-DD (defaults to today). |
| get_nutrition_scores | Get nutrition scores with per-nutrient consumed amounts and category grades. Returns category scores (All Targets, Vitamins, Minerals, Electrolytes, Antioxidants, Immune Support, Metabolism, Bone Health) with the actual consumed amount and confidence level for each tracked nutrient. This is the richest nutrition endpoint -- use it when you need to know both how much of each nutrient was consumed AND how close each is to the target. Args: date: Date as YYYY-MM-DD (defaults to today). |
| search_foods | Search Cronometer's food database by name. Returns matching foods with their IDs and source information. Pass a food_id to get_food_details for full nutrition info. Args: query: Food name or keyword (e.g. "eggs", "chicken breast"). |
| get_food_details | Get detailed food information including nutrition and serving sizes. Use this after search_foods to get the full nutrient profile and the available serving sizes for a food. Args: food_id: Food ID from search_foods results. |
| get_macro_targets | Get current macro targets including weekly schedule and templates. Returns the weekly macro schedule (which template applies to each day) and all saved macro target templates with their values. |
| get_fasting_history | Get fasting history from Cronometer. Returns fasts within the date range including status, timestamps, and duration. Args: start_date: Start date as YYYY-MM-DD (defaults to 30 days ago). end_date: End date as YYYY-MM-DD (defaults to today). |
| get_fasting_stats | Get aggregate fasting statistics. Returns total fasting hours, longest fast, average fast duration, and completed fast count. |
| add_food_entry | Add a food entry to the Cronometer diary. Use search_foods to find food_id and measure_id, then get_food_details to confirm serving sizes and gram weights. Args: food_id: Numeric food ID from search_foods results. measure_id: Measure/unit ID from get_food_details. grams: Weight of the serving in grams. date: Date to log as YYYY-MM-DD (defaults to today). translation_id: Translation ID from search results (usually 0). diary_group: LEAVE THIS AS "auto" unless the user explicitly named a meal. Do NOT infer it yourself from the time -- you do not know the user's timezone or which meals their account has, and guessing "snacks" at 11pm has repeatedly filed food under Morning Snacks. On "auto" the server reads the user's local clock and their own configured meals and picks correctly. The response includes a logged_to block naming the meal it chose, the local time, and the timezone. Tell the user which meal it went to -- that is how a misfiled entry gets caught immediately rather than days later. |
| remove_food_entry | Remove one or more food entries from the Cronometer diary. Use get_food_log to find entry IDs. Args: entry_ids: List of serving/entry IDs to remove. date: Date the entries belong to as YYYY-MM-DD (defaults to today). |
| mark_day_complete | Mark a diary day as complete or incomplete. Args: date: Date to mark as YYYY-MM-DD. complete: True to mark complete, False for incomplete. |
| copy_day | Copy all diary entries from the previous day to the given date. Additive -- does not remove existing entries on the destination date. Args: date: Destination date as YYYY-MM-DD (defaults to today). |
| add_custom_food | Create a custom food in Cronometer with specified nutrition. Nutrient amounts should be for the full serving size specified. After creation, use the returned food_id with add_food_entry to log it. Args: name: Food name. calories: Calories per serving (kcal). protein_g: Protein per serving (g). fat_g: Fat per serving (g). carbs_g: Carbs per serving (g). fiber_g: Fiber per serving (g, default 0). sugar_g: Sugar per serving (g, default 0). sodium_mg: Sodium per serving (mg, default 0). saturated_fat_g: Saturated fat per serving (g, default 0). serving_name: Name for the serving size (default "1 serving"). serving_grams: Weight of one serving in grams (default 100). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/firaskudsy/cronometer-api-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server