# Rhylthyme Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Rhylthyme

Plan cooking, lab work, events and workouts with parallel tracks, resource conflicts and timing.

- Record: https://musedirectory.ai/connector/rhylthyme
- Category: Productivity
- Developer: Rhylthyme (https://www.rhylthyme.com)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 1009ms, checked 2026-09-28T09:01:32Z
- Endpoint: https://mcp.rhylthyme.com/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T18:46:01Z)
- Source: Found in the official MCP Registry (com.rhylthyme/rhylthyme) https://registry.modelcontextprotocol.io/v0/servers?search=com.rhylthyme%2Frhylthyme

Rhylthyme turns recipes, protocols and training plans into multi-track schedules. It validates steps, detects resource conflicts, calculates critical paths, and shows when to start each task to finish on time. Share live timelines.

Example request: "Plan a dinner so all dishes finish at 6pm, showing when to start each one."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Rhylthyme to help me. It is a free service with an MCP server at https://mcp.rhylthyme.com/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- validate_program: Check a program before publishing or saving it: ids, dangling or cyclic triggers, steps overlapping in a track, tasks with no resourceConstraint, durations, replicates/instances misuse. Every finding has a code, a message and a suggested fix. Pure computation.
- analyze_schedule: Put a program on the clock: each step's start and end, total length, the critical path and what gates it, resource conflicts, slack per track. Pass finishAt to answer 'when do I start X so everything is ready at 6pm?'. Pure computation. With `history` (run records) or `program_id
- visualize_schedule: Publish a program as a live, shareable timeline (a public share link) and return its URL, with an ASCII Gantt and an itinerary. For a schedule the user wants to follow or share ('plan this so it all finishes at 6', 'when do I start each thing'). Validates first and refuses an inv
- import_from_source: Import a recipe or protocol from a URL or service into a program. source: spoonacular, themealdb (recipes); protocolsio, opentrons, benchling (lab); cooklang (.cook URL). action: search (no account needed), import (query = URL or id), random. import, random and benchling need the
- import_text: Turn pasted text (a recipe, protocol, run sheet or training plan) into a validated multi-track program on the server, in four model turns, with a table of the source span each step came from. Capped per day. Needs the user's Rhylthyme account.
- create_environment: Describe a workspace's equipment limits (one oven, two centrifuges, one stage) as resourceConstraints to copy into a program, so steps that share equipment are scheduled around each other.
- login: For apps that cannot connect the Rhylthyme account directly: returns a sign-in URL, then accepts the pasted token. Only the user's own saved programs, runs and imports need it; everything public works without. Tokens last about an hour.
- list_my_programs: List the user's saved programs. Needs the user's Rhylthyme account.
- load_program: Open one of the user's saved programs by id: summary plus live-timeline URL. Needs the user's Rhylthyme account.
- list_runs: List recorded runs of a saved program: when, how it ended, actual against planned length. For 'how long did this take last time?'. Needs the user's Rhylthyme account.
- review_program: A model reads an imported program against its source and reports what looks wrong: a default duration on "simmer for an hour", a step the importer dropped, steps chained that could overlap, a total that disagrees with the source. Changes nothing; returns findings to show the user
- load_run: Open one recorded run: planned against actual timing per step, what ended each step, pauses. Shows where a plan drifts. Needs the user's Rhylthyme account.
- calibrate_program: Propose durations for a saved program from its recorded runs: median as the default, P10 to P90 as the range, at least as wide as the author's, with the evidence per step and the effect on total length. Saves nothing; with `accept` it returns the calibrated program. Needs the use
- list_public_runs: List anonymous runs other people contributed for one exact program version: actual against planned length, and their conditions. For 'how long does this really take?'. No account needed. Takes `program` or `program_hash`.
- search_public_recipes: Search the public catalog of recipes, lab protocols, event templates and workouts by name or keyword. Returns ids, names, descriptions and URLs; no account needed.
- load_public_recipe: Open a public catalog entry by id: summary plus live-timeline URL.
- save_program: Save a program to the user's account ('save this for later'); the same programId updates it. Needs the user's Rhylthyme account.
- preview_timeline: Return a static Gantt image of a program with a caption, for 'show me a preview' or 'a picture of the timeline'. The image is served from a public share link. Planned versus actual: with `run` (a run record) it draws the actual bars over the plan.
- get_renderer_source: Return the open-source timeline renderer's JavaScript (Apache-2.0, about 90 KB, no dependencies) for an HTML page or artifact that cannot load external scripts; it defines Rhylthyme.renderTimeline(container, program).

Screening checks:
- MCP handshake: pass (Answered in 843ms)
- Domain against threat feeds (Cloudflare security DNS): pass (mcp.rhylthyme.com, www.rhylthyme.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (19 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)