Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 9 tools

Disambiguation5/5

Each tool has a clearly distinct role: plan creation, dish addition, dish timing adjustment, dish linking, status reading, pause/resume/cancel lifecycle, and step skipping. The descriptions make boundaries explicit, especially around add_dish vs adjust_dish and pause_meal vs cancel_meal.

Naming Consistency4/5

Most names follow a clean verb_noun snake_case pattern: add_dish, adjust_dish, cancel_meal, link_dish, pause_meal, plan_meal, resume_meal, skip_step. The only clear deviation is meal_status, which reads as noun_noun rather than verb_noun.

Tool Count5/5

Nine tools is well-scoped for a meal-planning and kitchen-timer server. Each tool covers a meaningful operation in the plan lifecycle without obvious redundancy.

Completeness4/5

The surface covers plan creation, dish management, status, pause/resume/cancel, and step skipping. A remove_dish or broader dish-edit operation is missing, so removing one dish likely requires canceling or recreating the whole plan.

Available Tools

9 tools
add_dishAdd a dish to the planAInspect

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.

Inputs: key (required), code (required), name (required), minutes (required), +1 more. Returns: message

adjust_dishAdd or take off timeAInspect

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.

Inputs: key (required), code (required), dish (required), minutes (required). Returns: message

cancel_mealCancel the mealA
Destructive
Inspect

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.

Inputs: key (required), code (required). Returns: message

meal_statusWhat is next in a meal planA
Read-onlyIdempotent
Inspect

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.

Inputs: code (required), key. Returns: code, next, links, state, +5 more

pause_mealPause the mealAInspect

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.

Inputs: key (required), code (required). Returns: message

plan_mealPlan a mealAInspect

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

Inputs: dishes (required), readyAt, startNow, timeZone, +1 more. Returns: url, code, links, alarms, +5 more

resume_mealResume the mealAInspect

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

Inputs: key (required), code (required). Returns: message

skip_stepSkip ahead on a dishAInspect

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.

Inputs: key (required), code (required), dish (required). Returns: message

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Your 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources