Kitchen Timer

com.tnyforgePublished by tnyforge.comOfficial publisherv1.0.0Updated Oct 27, 2026

Plan a meal and run kitchen timers that ring on your phone. No sign-in.

VerifiedStreamable HTTPWeb executableLocation & LifestyleProductivity & Workflow

Overview

AI-generated overview

Plans multi-dish meals and runs kitchen timers that ring on the cook's phone, with tools to check, pause, adjust, skip, add and cancel.

What you can do
  • Create a meal plan from dishes you break down yourself, getting a phone link, QR code and schedule
  • Check what is next in a plan and how long until it, optionally including phone timers
  • Pause or resume the running dishes of a plan on the phone
  • Add or remove minutes on a dish, or skip the rest of a dish's current wait
  • Add another dish to an existing plan, or cancel the plan and remove its phone timers
When to use it
Useful when an assistant helps coordinate cooking several dishes so they finish together, and the cook wants alarms on a phone in the kitchen. Also handy for adjusting timing mid-cook without touching the phone.
Requirements
A remote endpoint at kt.tnyforge.com over streamable HTTP; no sign-in, packages, environment variables or headers are declared. The plan's code (the last part of its link) is needed for most tools, and a control key for the ones that change a plan. The cook must open the link on a phone and tap Start before pause, resume, skip and live timer changes work.
Before you install
Several tools change or remove state: adjust_dish, skip_step, add_dish, pause_meal, resume_meal and cancel_meal need the plan's control key, and cancel_meal makes the link stop working and removes the phone timers, so the person should be asked first. Anyone holding the plan code can read status; the control key should be treated as a secret. Meal plans and schedules are sent to a third-party service.

Installation

In SourceWeft

  1. Open Kitchen Timer in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.tnyforge%2Fkitchen-timer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "kitchen-timer": {
      "type": "http",
      "url": "https://kt.tnyforge.com/mcp/open"
    }
  }
}

Tools

8

plan_meal

Plan a meal

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).

ParametersdishesrequiredreadyAtstartNowtimeZonereadyInMinutes

meal_status

What is next in a meal plan

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.

Parameterskeycoderequired

pause_meal

Pause the meal

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.

Parameterskeyrequiredcoderequired

resume_meal

Resume the meal

Resume the paused dishes of this plan on the phone. Needs the plan's code and control key.

Parameterskeyrequiredcoderequired

adjust_dish

Add or take off time

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.

Parameterskeyrequiredcoderequireddishrequiredminutesrequired

skip_step

Skip ahead on a dish

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.

Parameterskeyrequiredcoderequireddishrequired

add_dish

Add a dish to the plan

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.

Parameterskeyrequiredcoderequirednamerequiredstepsminutesrequired

cancel_meal

Cancel the meal

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.

Parameterskeyrequiredcoderequired

Version history

1
  1. v1.0.0LatestOct 22, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.