‹ Round & Rest

Integrations

Round & Rest can be driven three ways without ever opening the settings screen: describe it out loud to an AI, configure it from a link, or mirror it on a BUSY Bar mounted on the wall. Here is what each one buys you, and an address to ask for the one that is missing.

Dictate your session to an AI

"Three blocks of two exercises, four rounds" becomes a complete configuration without a single field being touched by hand: that is what an MCP server plugged into the assistant changes.

What is an MCP server? The Model Context Protocol (MCP) is an open standard that lets a conversational assistant — Claude, ChatGPT — call outside tools. Round & Rest exposes one, start_workout_timer, and more importantly an interface: the assistant turns the spoken sentence into a configuration, and the timer shows up directly in the conversation instead of being merely described in text.

See how to connect Round & Rest to Claude or ChatGPT for the address to paste and the steps, assistant by assistant.

The URL configuration

Can the timer be configured from a link? Yes: one address is enough to open the timer already set, without going through the configuration screen. Each mode reads its own parameters from the query string:

ModeParametersExample
intervals work, rest, rounds /?mode=intervals&work=30&rest=15&rounds=8
emom every, rounds /?mode=emom&every=90&rounds=10
amrap total /?mode=amrap&total=1200
fortime cap /?mode=fortime&cap=1200
sequence blockRest, blocks /?mode=sequence&blocks=8:0:300.240&blockRest=0

Two parameters apply to every mode: label (forty characters at most, the name shown during the session) and lang (fr or en, to open directly in the right language). A preset exists too: preset=tabata opens the 20/10 eight-round interval already set, without writing a single one of the three interval parameters.

OPEN THE EXAMPLE — 30/15 × 8

Thirty seconds of work, fifteen of rest, eight rounds. Editable before you start.

Does Round & Rest have an API? No versioned REST API, but two programmable entry points: this URL configuration, and the MCP server described above. Both cross the same validation boundary the app applies to its own settings, so an out-of-bounds value gets clamped rather than rejected.

The same mechanism serves more than this page: sharing a session with a training partner, or opening it from a QR code posted on a wall.

The BUSY Bar

The BUSY Bar is a wall-mounted display, built to be read from across the room rather than off a phone lying on the floor. It keeps its own countdown, so a single request per phase is enough to drive it — never one per second. The channel only runs one way, since the device exposes no key-press event: you get the BUSY Bar's screen or its buttons, never both at once.

The BUSY Bar page covers the setup and what it displays.

Ask for another integration

A device, a service, an AI platform missing from this list: the address below is enough, no form needed.

REQUEST AN INTEGRATION

An address, not a form. Say which device or which service.

Other pages