Productivity

rhylthyme.com

Validates, analyzes, visualizes, and imports Rhylthyme multi-track schedules for parallel workflows such as recipes, lab protocols, event run-of-shows, and training plans.

1 endpoint18 known toolsFirst detected September 17, 2026Last detected September 17, 2026

ENDPOINT 1

https://mcp.rhylthyme.com/mcp

No auth detected

MCP server metadata

Name: rhylthyme-mcp
Version: 1.3.0

Capabilities

tools.listChangedresources.listChangedprompts.listChanged

Server 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: **search_public_recipes** → **load_public_recipe** (or the one-shot tool). The result already includes the live URL. - New content: build the program → **validate_program** (fix every error it reports) → optionally **analyze_schedule** (makespan, critical path, conflicts, wall clock when you pass finishAt/startAt) → **visualize_schedule** for the shareable live timeline. visualize_schedule validates too and refuses invalid programs. - Never describe a schedule in prose when a timeline is possible; the URL is the deliverable. Quote the Gantt / itinerary from the result when summarizing. - **login** is only needed for the private library (list_my_programs, load_program, save_program) 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 analyze_schedule for wall-clock start times. 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). Without multi-message prompt support, read `rhylthyme://guide/extraction` for the same four turns. `rhylthyme://guide/authoring` is the cheat-sheet, `rhylthyme://schema/program` the full JSON schema, `rhylthyme://examples/*` complete valid programs.

Known tools 18

validate_program

Check a Rhylthyme program for structural and scheduling errors BEFORE visualizing or saving it: missing/duplicate ids, dangling afterStep references, dependency cycles, steps that overlap within a track, tasks with no resourceConstraint, unparseable durations, invalid choice references, and schema 0.

Inferred read-only

analyze_schedule

Resolve a Rhylthyme program onto the clock and report what the live runner will do: every step's start/end (seconds from start and, if you pass `finishAt` or `startAt`, ISO wall-clock times), total makespan, the critical path, `bindingConstraints` (what gates each critical-path edge — an in-flight cap, a saturated task, an offset, or a plain dependency), resource conflicts tagged `kind: "maxConcurrent"` (more steps claim a task than its maxConcurrent allows) or `kind: "inFlight"` (more instances of a replicated step are between it and its barrier than `replicates.

Inferred read-only

visualize_schedule

Render a multi-step parallel schedule as a live timeline (cooking, lab protocols, event run-of-show, training).

Inferred read-only

import_from_source

Import a recipe or lab protocol from an external source into a Rhylthyme program.

Inferred read-only

import_text

Turn a block of pasted text — a recipe, a lab protocol, a run-of-show, a training plan — into a validated multi-track Rhylthyme program.

Inferred read-only

create_environment

Create a Rhylthyme environment definition with resource constraints for a workspace (lab, kitchen, bakery, etc.

Potential side effects

login

Inferred read-only

list_my_programs

List your saved Rhylthyme schedules.

Inferred read-only

load_program

Load a specific saved program by ID.

Inferred read-only

list_runs

List the recorded executions of one saved program, newest first: when it ran, how it ended, and the actual makespan against the planned one.

Inferred read-only

load_run

Open one recorded execution by run id: planned versus actual start, end and duration for every step, what ended each step (a person, a timer, an abort), time the clock was paused, and the recorded variance factors.

Inferred read-only

calibrate_program

Propose new durations for one of the user's saved programs from its recorded runs, with the evidence.

Inferred read-only

list_public_runs

List the runs other people have contributed for one exact program version: when each ran, how it ended, actual against planned total, and the variance factors that run was recorded with.

Inferred read-only

search_public_recipes

Search the public Rhylthyme catalog of cookable recipes, lab protocols, event templates, and workouts.

Inferred read-only

load_public_recipe

Load a single public recipe / protocol / workout / event template by id.

Inferred read-only

save_program

Save a Rhylthyme program to your account.

Inferred read-only

preview_timeline

Render a Rhylthyme program as a static Gantt-chart image so the user can SEE what the live timeline looks like, without committing to opening the live URL.

Inferred read-only

get_renderer_source

Returns the source code of the open-source Rhylthyme timeline renderer (Apache-2.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.rhylthyme-mcp]
url = "https://mcp.rhylthyme.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "rhylthyme-mcp": {
      "type": "http",
      "url": "https://mcp.rhylthyme.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: rhylthyme-mcp
Remote MCP URL: https://mcp.rhylthyme.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "rhylthyme-mcp": {
      "url": "https://mcp.rhylthyme.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "rhylthyme-mcp": {
      "type": "http",
      "url": "https://mcp.rhylthyme.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "rhylthyme-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.rhylthyme.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.