OneRep
All updates

Your log now talks to your AI assistant

Platform2 min read

OneRep speaks the Model Context Protocol, so Claude or any other MCP client can read your training and nutrition log and, if you allow it (and only if), add to it. Read-only by default, revocable in a tap, and there is nothing it can delete. That last part was not an accident.

You already talk to an assistant about your training; let's not pretend otherwise, it's 2026. Until now that conversation happened beside your log rather than with it: you described your week from memory, the assistant gave you advice about a week that may or may not have occurred, and nothing either of you said went anywhere. Two unreliable narrators, comparing notes. Charming, useless.

From this release OneRep speaks the Model Context Protocol. Point Claude (or anything else that speaks MCP) at your account, and it reads the actual log. The one with the real sets in it.

What it can do

Ten tools. Five read, five write, and the symmetry ends there.

  • Read: one day in full, a date range, recent sessions with every set, your goals, your weigh-ins.
  • Write: water, a food entry, a weigh-in, a completed workout, and marking days as deliberate rest.

So "how did last week compare to the one before?" gets answered from your sets rather than your recollection (and your recollection was flattering you, it always is), while "log that I did the push session this morning, same as Monday" ends as an actual row in your actual training log.

What it cannot do

Nothing deletes. No tool removes an entry, clears a day, or resets anything. Deleting is a thing you do yourself, in the app, deliberately. An agent having a bad night can scribble in the margins; it cannot tear out pages.

Read-only means read-only. Tokens come in two kinds. A read-only token is never shown the write tools, and is refused if it goes looking for them anyway. Start there. Upgrade after you've watched it behave; trust being a thing that gets earned by request, not granted by default.

Coach stays out of it. Nothing reachable over MCP spends an AI allowance, because "whose quota does an agent-invoked coach call spend?" deserves a better answer than yours, silently. Until we have a better answer, the door stays shut. We've all been billed by that door before.

Setting it up

Settings → API & MCP. Mint a token, copy it (shown once, because we store only a hash and cannot show it to you again, which is precisely the point), and paste it into your client with the endpoint printed on the same screen.

claude mcp add --transport http onerep https://<your-deployment>.convex.site/mcp \
  --header "Authorization: Bearer onerep_sk_…"

Revoking is one tap and lands on the very next request. Each token is rate limited on its own, so an assistant stuck in a loop at 3 AM burns its own budget, not your ability to open your own app.

The full reference, with every tool, every limit, and everything an agent is prevented from doing and why, is on the MCP documentation.

Free, part of OneRep Core, and off until you turn it on. As it should be.

Common questions

Do I need a subscription to use it?
No. The MCP interface is part of OneRep Core, which is free. Coach and photo logging are not reachable over MCP at all, so nothing an assistant does spends your AI allowance. Your quota is yours; a machine doesn't get to spend it on your behalf.
Can an assistant delete my data?
No. There is no delete tool of any kind: no removing entries, no clearing days, no bulk anything. The only way to delete something in OneRep is to do it yourself, in the app, on purpose. Some doors we simply did not build.
What can a read-only token actually see?
Every day you have logged: food entries and totals, water, workouts with every set, weigh-ins, and your goals. A token is your whole log, so treat it like a password, because that is exactly what it is wearing a friendlier name.
What happens if I revoke a token?
It stops working on the very next request. Anything already written stays, the same as if you had typed it yourself, and you delete it the normal way. Revocation ends the relationship; it does not rewrite its history. Little does.