rhylthyme-mcp
Rhylthyme schedules multi-step work that a person carries out against a clock (several dishes landing together, a lab protocol with overlapping incubations, an event run-of-show, a workout) and publishes it as a live timeline with timers.
The Rhylthyme MCP server is hosted. Most clients need nothing from this package: connect to the URL.
| Endpoint | For |
|---|---|
https://mcp.rhylthyme.com/mcp |
anything |
https://mcp.rhylthyme.com/kitchen/mcp |
cooking |
https://mcp.rhylthyme.com/lab/mcp |
lab protocols |
https://mcp.rhylthyme.com/events/mcp |
events |
https://mcp.rhylthyme.com/gym/mcp |
workouts |
- Claude (claude.ai, desktop, mobile): Settings → Connectors → Add custom connector → paste a URL.
- ChatGPT: Settings → Apps & Connectors → Advanced settings → Developer mode → create a connector with a URL.
- Claude Code:
claude mcp add --transport http rhylthyme https://mcp.rhylthyme.com/mcp - Cursor and others:
{ "mcpServers": { "rhylthyme": { "url": "https://mcp.rhylthyme.com/mcp" } } }
No account or API key is needed for the public tools (validate, analyze, publish a timeline, search the catalog).
What this package is
A stdio bridge, for clients that can only launch a command. It speaks MCP on stdin/stdout and passes every request through to the hosted server, so you always get the current tools, resources and prompts.
pip install rhylthyme-mcp # or: pipx install rhylthyme-mcp / uvx rhylthyme-mcp
{
"mcpServers": {
"rhylthyme": { "command": "rhylthyme-mcp", "args": ["kitchen"] }
}
}
args is optional: kitchen, lab, events, gym, or nothing for the
general endpoint. --url (or RHYLTHYME_MCP_URL) points it at a server you
host yourself. RHYLTHYME_TOKEN, if set, is sent as a bearer token; only the
account tools (your saved programs, recorded runs, imports) need one.
No MCP client at all
One HTTP request works, with no handshake and no account:
curl -s https://mcp.rhylthyme.com/mcp \
-H 'Content-Type: application/json' -H 'Accept: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Or the command-line tool: pip install rhylthyme-cli-runner, then
rhylthyme validate, rhylthyme analyze --finish-at 18:00,
rhylthyme publish (prints the live-timeline URL).
Versions
0.1.2 is 0.1.1 with its license metadata corrected: the package is Apache-2.0, like the rest of Rhylthyme.
0.1.0 was a local server with a single visualize_schedule tool that opened an
HTML file in your browser. 0.1.1 replaces it with the bridge: the same
rhylthyme-mcp command and the same client configuration, but every tool of
the hosted server, and links to live timelines instead of local files.
Docs: https://docs.rhylthyme.com/web-app/mcp/ · Source:
https://github.com/rhylthyme/rhylthyme-mcp (python/) · License: Apache-2.0
Metadata
Release files for rhylthyme-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rhylthyme_mcp-0.1.2.tar.gz | 9.6 kB | Without provenance | Details for rhylthyme_mcp-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rhylthyme_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for rhylthyme_mcp-0.1.2-py3-none-any.whl |
Total release size: 19.9 kB
Release files / rhylthyme_mcp-0.1.2.tar.gz
| Download URL | rhylthyme_mcp-0.1.2.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2a42d98d1e27725553735db3b67ef34985e47580f822e43374a3fadaec7e547
|
|
BLAKE2b-256 checksum How to use checksums |
faaaa42974744358fb40bbb9dcb65481cc9204c661d9cdb9ac227c0d4a34cca5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.9
|
Release files / rhylthyme_mcp-0.1.2-py3-none-any.whl
| Download URL | rhylthyme_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6e1135a0cf200c4ac092e4ec41c009312b01c1770d7b597159de63558182d95c
|
|
BLAKE2b-256 checksum How to use checksums |
b7ad07d701c53681c225c7b76cd1d7a686a4a73d951647d8e0828011f0a1df68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.9
|
Security for rhylthyme-mcp 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.