Alex
My gym log, with its own MCP server: ChatGPT plans the workout, I log sets on my phone, and ChatGPT reads the history back.
A private app I built for myself. Not a product.
- Status
- Personal tool
- When
- Nov 2026
- Stack
- Next.js · MCP · Cloudflare D1
36 automated API and MCP checks, plus an end-to-end run in production: ChatGPT planned it, I logged it, ChatGPT read it back.
Layman's Version
Alex is my gym log. I ask ChatGPT to plan the day's workout and send it to Alex. At the gym I open Alex on my phone and log each set's weight and reps, and it shows what I lifted last time.
Afterwards, ChatGPT can pull the session back, so I can ask how chest press has been going without copying anything around. It's built for one person, me, and that's the point.
Technical Version
Pieces
- ChatGPT
- Alex MCP tools
- D1 database
- phone UI
Alex runs as a private ChatGPT Site with its data in Cloudflare D1. Its MCP plugin exposes save_workout, get_today_workout, get_workout, get_latest_completed_workout, get_exercise_history, list_recent_workouts and delete_workout.
Rules the data follows
- One plan per date. Started plans and completed logs can't be overwritten.
- Planned and actual values are stored separately, so a prescription never gets mixed up with what I actually did.
- Pending changes are cached on the device, but the database is the record.
Checks
36 automated API and MCP assertions cover concurrent writes, invalid fields and ranges, idempotency and duplicate dates. The production check went end to end: ChatGPT created a throwaway plan, I logged it in the browser, reloaded, finished the session, and ChatGPT read it back.
How it was built
I built it with Codex in November 2026, for my own use.


Limitations
- It's tied to my ChatGPT account, so there's no public link.
- No background notifications; the rest timer only runs while the app is open.