Bring your own agent.

Get a key

You need a Fit Rocket account first. It's free, with a Google sign-in. Every agent key acts as the user who minted it: there's no anonymous mode and no shared credential.

In the app, go to You → Connected agents and mint a key. You choose what it may do. Read only, or read & write, and name it for the agent that will hold it, so you can tell your keys apart later. The key is shown exactly once; copy it then, because Fit Rocket can't show it again.

Revoke any key from the same list, any time. Revocation takes effect within about a minute.

Point your agent at it

The endpoint is https://fit-rocket-proxy.fitrocket.workers.dev/mcp. Streamable HTTP, stateless. The key rides as a header:

Authorization: Bearer <agent key>

With the Claude Code CLI, one command connects it:

claude mcp add --transport http fitrocket https://fit-rocket-proxy.fitrocket.workers.dev/mcp --header "Authorization: Bearer YOUR_KEY"

Most other clients take an mcpServers block in their config file:

{
  "mcpServers": {
    "fitrocket": {
      "type": "http",
      "url": "https://fit-rocket-proxy.fitrocket.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

A client that can't set headers may append ?token=<key> to the URL instead. URLs end up in logs more often than headers do, so prefer a read-only key there.

What an agent can do

Reads · any key

get_overview

Your numbers in one call. The same numbers the app shows: your goal date and its likely range, your pace, both progress bars, what your logs miss.

get_daily_logs

Daily logs. Weigh-ins, intake, burn, for a date range.

get_meals

Meal entries for a day or range, with ids for deleting.

get_workouts

Recent workout diary entries, with ids.

get_phase_history

The journey's past phases, each cut, maintain, and build.

get_training_state

The active lifting block and run plan, and what's next in each.

get_exercise_history

One lift over time. Every session's top set and working sets, with an estimated one-rep max.

find_exercises

See how an exercise name would be logged before logging it, browse the catalog, or find a lift that's been logged under two names. Writes nothing.

get_routines

The training sessions an agent has planned for you, and the last time you did each exercise in them. Reads your lifting only.

get_strength_day

One day's lifting, set by set in the order you did it, with each set's time and the rest before it when it was logged live.

get_quick_add

The meals one tap logs again, as Quick add lists them: your saved meals, then whole meals from the last two weeks.

get_run_plan

Your running plan's paces and the runs coming up, step by step.

Writes · read & write keys only

log_daily

Log a day's weigh-in, intake, or burn, and get back what it replaced, so the agent can undo itself.

log_meal

Add a meal entry; it feeds intake like any meal logged in the app.

delete_meal

Remove one meal entry.

log_workout

Add a workout to the diary. Workouts never feed the deficit. Same as in the app.

delete_workout

Remove one workout.

update_profile

Change profile basics, returning the previous values.

start_new_phase

Close the current phase and open a new cut, maintain, or build.

log_strength_sets

Log a lifting session set by set, into the same strength history the app keeps. Each set can carry the time it was done. Sending the same day again is safe: the day is written to match.

save_routines

Plan training sessions: the exercises in order, each set with its target, the rests and the supersets. They show on Train's Today. Anything it can't use stops the whole save, so nothing is half-written.

quick_add_meal

Log a Quick add meal again, whole, the way one tap in the app does. It can make the portion bigger or smaller.

complete_run

Tick off a run from your plan, with its distance, its time and how the paces felt, or skip it. A finished run goes in the workout diary too.

How it's kept safe

An agent key is your own credential, sealed so that only Fit Rocket's own server can open it. Every agent call passes through the same per-user security rules as the app itself. There is no service account and no admin backdoor anywhere in the system. An agent can only ever touch the one account whose key it holds.

Revoking a key deletes its registration and cuts it off within about a minute.

One honest note: a read & write key acts as you. Treat it like a password. Hand it only to an agent you trust, and revoke it the moment you stop.

For machines

Agents and tools can also read https://fitrocket.in/llms.txt and https://fitrocket.in/.well-known/mcp.json.