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 Settings → 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.usman-hafiz-awan1.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.usman-hafiz-awan1.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.usman-hafiz-awan1.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

The dashboard in one call — the same numbers the app shows: your pace, your goal date, both progress bars, the Reality check.

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 chapters — each cut, maintain, and build.

get_training_state

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

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 chapter and open a new cut, maintain, or build.

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.