Works where you already work.

The idea

The best place to log is wherever you already are

Every app wants to be the one you open. That's a reasonable thing for an app to want and a bad basis for a training log, because the session you don't record is the one missing from the chart a year later — and the most common reason it goes unrecorded is that logging it meant switching context.

So Workout Chat doesn't insist on being opened. It has a perfectly good chat of its own — and it also runs a remote MCP server, which means any assistant that speaks the protocol can write to your log and read from it. Use whichever door is nearest.

What stays constant

Several doors, one room

A session logged from Claude on the train is in the web app before you get home, and a correction typed into the web app is what ChatGPT sees next time you ask. There is one log; the interfaces are just ways of reaching it.

Exercise names are resolved the same way on every path in, so logging "incline DB press" from an editor and "incline dumbbell press" from the browser doesn't quietly create two progressions. That consistency is what makes multiple entry points safe rather than a slow way of corrupting your own history.

Connecting

One approval, no keys to manage

Authentication is OAuth 2.1 with PKCE and dynamic client registration. In practice that means you paste a URL, a browser tab opens, you approve, and you're connected — there's no API key to copy into a config file, no secret sitting in a dotfile, and nothing to rotate. Revoke from your profile and the token dies immediately.

Discovery documents are published too, so a client that knows how to look can find the authorisation server, the protected resource, and the server card without being told where they are.

Setup guides and full API reference →