Kitchen Timer
Server Details
Plan a meal and run kitchen timers that ring on your phone. No sign-in.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Score is being calculated.
Available Tools
8 toolsadd_dishAdd a dish to the planInspect
Add one more dish to this plan. The ready time stays, so the new dish goes in at the ready time minus its cooking time and must still fit. Before the person taps Start it joins the plan on the sheet; afterwards it goes onto the phone too. Same rules as plan_meal: a plain-text name, at most 12 dishes. Needs the plan's code and control key.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link. | |
| code | Yes | The plan's code, or its whole link. | |
| name | Yes | Plain text, 80 characters at most. | |
| steps | No | Optional moments inside the cooking time. | |
| minutes | Yes | Total cooking time in minutes. |
Output Schema
| Name | Required | Description |
|---|---|---|
| message | Yes |
adjust_dishAdd or take off timeInspect
Add time to a dish (a positive number of minutes) or take time off (negative). Before the person taps Start this changes the plan, and the ready time stays; afterwards it changes that dish's timer on the phone. Needs the plan's code and control key.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link. | |
| code | Yes | The plan's code, or its whole link. | |
| dish | Yes | The dish's name as in the plan, or its number in the plan (1 is the first dish). | |
| minutes | Yes | Minutes to add (positive) or take off (negative), such as 2 or -1.5. Not zero. |
Output Schema
| Name | Required | Description |
|---|---|---|
| message | Yes |
cancel_mealCancel the mealDestructiveInspect
Cancel this plan: its link stops working, and if the person already started it, its timers are removed from the phone. Only that plan's timers; nothing else on the phone. Needs the plan's code and control key. Ask the person first.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link. | |
| code | Yes | The plan's code, or its whole link. |
Output Schema
| Name | Required | Description |
|---|---|---|
| message | Yes |
meal_statusWhat is next in a meal planRead-onlyIdempotentInspect
Say what is next in a meal plan made with plan_meal, and how long until it. Give the plan's code (the last part of its link). Only reads; never changes a plan. Give the control key too, if you have it, to also see the timers on the phone.
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | Optional: the plan's secret control key. With it the answer also says whether the person has started the timers on the phone and what each one is doing. | |
| code | Yes | The plan's code, or its whole link. |
Output Schema
| Name | Required | Description |
|---|---|---|
| code | Yes | |
| next | No | |
| state | Yes | |
| timers | No | Only with the key, once the phone has started: each dish's state on the phone. |
| claimed | No | Only with the key: a phone has tapped Start. |
| upcoming | No | |
| readyAtMs | Yes | |
| serverNowMs | No |
pause_mealPause the mealInspect
Pause every dish of this plan that is running on the phone (the cook can resume on the phone or you can call resume_meal). Needs the plan's code and control key. Only works after the person has tapped Start on the phone; before that it says so.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link. | |
| code | Yes | The plan's code, or its whole link. |
Output Schema
| Name | Required | Description |
|---|---|---|
| message | Yes |
plan_mealPlan a mealInspect
Make a meal plan: each dish starts at the right moment so everything is ready at the same time. Returns a link (open it on the phone in the kitchen, where the alarms ring), a QR code for that link, and the schedule. YOU do the cooking knowledge: break a recipe into dishes, each with its total cooking minutes, and put the timed moments inside a dish as steps ("simmer 20, rest 5" is a dish of 25 minutes with a step "Rest" at 20). If the person did not say when they want to eat, ASK before calling; use readyInMinutes for "we eat in 90 minutes", readyAt (an ISO date-time with a UTC offset, or local time plus timeZone) for "at 7", or startNow to start cooking now (a single timer is a one-dish plan with startNow). Keep times realistic and use only what the person gave you; at most 12 dishes and 12 hours. Dish names are plain text, no links. The reply link works for anyone who has it and the plan is deleted about a day after the meal. Tell the person the alarms ring on the phone page, not in this chat. The reply also holds a secret CONTROL KEY (starts with ktpk_): remember it for the rest of the chat, do not show it or put it in any link, and pass it with the plan's code to the control tools to keep managing this plan. Once it works you may offer the person to manage their whole kitchen from now on (⋯ → Link an agent in the app gives the connector address and a 6-digit code).
| Name | Required | Description | Default |
|---|---|---|---|
| dishes | Yes | What is being cooked. A single timer is one dish. | |
| readyAt | No | Everything ready at this time: ISO 8601 with a UTC offset (2026-10-17T19:00:00+01:00), or without an offset when timeZone is given, or epoch milliseconds. | |
| startNow | No | True: start every dish now (the longest dish sets when it is ready). | |
| timeZone | No | Optional IANA time zone such as Europe/London. Only used to word the schedule text; the card and the phone show times in the viewer's own clock. | |
| readyInMinutes | No | Everything ready this many minutes from now. Give exactly one of readyInMinutes, readyAt, startNow. |
Output Schema
| Name | Required | Description |
|---|---|---|
| url | Yes | Open this on the phone in the kitchen. |
| code | Yes | |
| alarms | No | |
| dishes | No | |
| schedule | Yes | |
| readyAtMs | Yes | |
| expiresAtMs | No | |
| serverNowMs | No |
resume_mealResume the mealInspect
Resume the paused dishes of this plan on the phone. Needs the plan's code and control key.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link. | |
| code | Yes | The plan's code, or its whole link. |
Output Schema
| Name | Required | Description |
|---|---|---|
| message | Yes |
skip_stepSkip ahead on a dishInspect
Skip the rest of the current wait for one dish: a dish still waiting to go in starts now, and a dish that is cooking finishes now. Only works after the person has tapped Start on the phone. Needs the plan's code and control key.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | The secret control key plan_meal gave you for this plan (starts with ktpk_). Never show it or put it in a link. | |
| code | Yes | The plan's code, or its whole link. | |
| dish | Yes | The dish's name as in the plan, or its number in the plan (1 is the first dish). |
Output Schema
| Name | Required | Description |
|---|---|---|
| message | Yes |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
8 tool updates
- First observed
add_dish - First observed
adjust_dish - First observed
cancel_meal - First observed
meal_status - First observed
pause_meal - First observed
plan_meal - First observed
resume_meal - First observed
skip_step
Related MCP Connectors
Real-time multi-track schedules for cooking, lab protocols, events and workouts. Validate and share.
Shareable timer links for countdowns, clock times, Pomodoro, Tabata and step recipes. No account.
Find free public recipes; import links and plan meals from your cookbook. Private tools need a plan.
Put timed plans on the person's phone: steps, questions and waits that ring when a rest is over.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceYour digital kitchen, powered by AI. Track what you have, discover what you can cook, and get guided through every recipe — step by step, timer by timer.MIT
- AlicenseNot gradedqualityBmaintenanceEnables a voice assistant to backward-plan a multi-dish, multi-cook dinner from serve time, hand each cook their next job, and track progress by voice. When a dish runs late, it re-solves the entire landing — reassigning cooks, compressing steps, and reporting an honest projected serve time rather than hiding the slip.MIT
- AlicenseNot gradedqualityBmaintenanceEnables a voice assistant to plan a whole multi-dish dinner backwards from serve time, respecting one cook's hands, burners, oven racks and temperatures, then walk the cook through each step with timed cues and adapt the plan when they fall behind.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to create and persist meal plans, track parallel timers and progress, recover from interruptions or constraint changes, and inspect revised schedules through MCP tools.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.