Rhylthyme

Rhylthyme schedules work that has to happen against a clock, with several things going at once: a Thanksgiving dinner on one oven, a cell-culture protocol around an incubator, a conference run-of-show, an interval workout.

A schedule is a Rhylthyme program: parallel tracks of timed steps, with dependencies between steps (after, with a buffer, a hand-off before another step ends, manual gates) and resource limits such as one oven or two centrifuges. Key features:

What you can ask

Turn a goal ("Thanksgiving dinner for 8 with one oven, ready at 6pm"), or a source text, into a validated Rhylthyme program and a live timeline URL. Four turns: read the source back, confirm the program model, extract the steps with the words each came from, then assign tracks and triggers and run validate → analyze → visualize.
Example path

MCP connector

Server URL: https://mcp.rhylthyme.com/mcp
Login: API key
Protocol: MCP 2026-07-28
Instructions: Rhylthyme schedules any real-time, multi-track process — cooking, lab protocols, event run-of-shows, workouts, manufacturing, turnarounds. A "program" is JSON: parallel tracks of sequential steps, each with a duration and a startTrigger (programStart / afterStep / programStartOffset / afterStepWithBuffer / manual), plus resourceConstraints (e.g. one oven) that the live runner enforces. Workflow:
Existing content: → (or the one-shot tool). The result already includes the live URL.
New content: build the program → (fix every error it reports) → optionally (makespan, critical path, conflicts, wall clock when you pass finishAt/startAt) → for the shareable live timeline. validates too and refuses invalid programs.
returns the live timeline URL together with an ASCII Gantt and an itinerary.
login is only needed for the private library (, , ) and for imports. Public catalog tools need no token. Authoring rules: stepIds unique across the whole program; steps in one track never overlap (chain with afterStep); every task used by a step has a matching resourceConstraint; durations in seconds (numbers) or time strings ("5m", "1h30m"); repeated work is replicates on ONE step with instances: "each"/"all" and maxInFlight, never copied steps; to make everything finish together, delay short tracks with programStartOffset or afterStep, and pass finishAt to for wall-clock start times; step alerts ({event:"end", offsetSeconds:"-2m", message}) notify the person. Authoring from a goal or a source text: run the plan_schedule prompt — four turns (read the source back → confirm the program model → extract the steps with the words they came from → assign tracks and triggers). The same four turns are documented in rhylthyme://guide/extraction for clients without multi-message prompt support. rhylthyme://guide/authoring is the cheat-sheet, rhylthyme://guide/tools the long form of each tool, rhylthyme://schema/program the full JSON schema, rhylthyme://examples/* complete valid programs.

Tools

Reads data16

Deletes or can't be undone3

Skills

None in the store listings or on the server

What you can ask

Turn a goal ("Thanksgiving dinner for 8 with one oven, ready at 6pm"), or a source text, into a validated Rhylthyme program and a live timeline URL. Four turns: read the source back, confirm the program model, extract the steps with the words each came from, then assign tracks and triggers and run validate → analyze → visualize.

Example path

MCP connector

Server URL

https://mcp.rhylthyme.com/mcp

API key

Protocol

MCP 2026-07-28

Instructions

Rhylthyme schedules any real-time, multi-track process — cooking, lab protocols, event run-of-shows, workouts, manufacturing, turnarounds. A "program" is JSON: parallel tracks of sequential steps, each with a duration and a startTrigger (programStart / afterStep / programStartOffset / afterStepWithBuffer / manual), plus resourceConstraints (e.g. one oven) that the live runner enforces. Workflow:

Existing content: → (or the one-shot tool). The result already includes the live URL.

New content: build the program → (fix every error it reports) → optionally (makespan, critical path, conflicts, wall clock when you pass finishAt/startAt) → for the shareable live timeline. validates too and refuses invalid programs.

returns the live timeline URL together with an ASCII Gantt and an itinerary.

login is only needed for the private library (, , ) and for imports. Public catalog tools need no token. Authoring rules: stepIds unique across the whole program; steps in one track never overlap (chain with afterStep); every task used by a step has a matching resourceConstraint; durations in seconds (numbers) or time strings ("5m", "1h30m"); repeated work is replicates on ONE step with instances: "each"/"all" and maxInFlight, never copied steps; to make everything finish together, delay short tracks with programStartOffset or afterStep, and pass finishAt to for wall-clock start times; step alerts ({event:"end", offsetSeconds:"-2m", message}) notify the person. Authoring from a goal or a source text: run the plan_schedule prompt — four turns (read the source back → confirm the program model → extract the steps with the words they came from → assign tracks and triggers). The same four turns are documented in rhylthyme://guide/extraction for clients without multi-message prompt support. rhylthyme://guide/authoring is the cheat-sheet, rhylthyme://guide/tools the long form of each tool, rhylthyme://schema/program the full JSON schema, rhylthyme://examples/* complete valid programs.

Tools