FitFo works with AI assistants.

Your assistant logs and plans. You stay in charge.

  1. Your assistantasks to connect
  2. FitFoshows what it wants
  3. Youapprove or say no
  • You pick what it may do.
  • Disconnect any time: Settings, Connected AI.
  • Your password never reaches it.

What it can do

  • FitFo app: log workouts
    Log workouts
  • FitFo app: log food
    Log food
  • FitFo app: plan sessions
    Plan sessions
  • FitFo app: read progress
    Read progress

Same things you can do in the app.

Pick your route

It depends on your assistant.

MCP

  • Claude
  • Grok Bot
  • Cursor
  • Any remote MCP app
https://api.fitfo.app/mcp
How to connect
  1. Add the URL above as a server.
  2. Your assistant sends you to fitfo.app/connect. Sign in and choose exactly what it may do.
  3. Nothing is granted until you approve it there.

The connection uses OAuth. A prompt to start with:

Starter prompt
Connect to my FitFo account through the FitFo MCP server.

When I say I'm starting a workout, call start_workout once. Its timer starts then. Each time I tell you an exercise, add it with add_exercises. Never start a new workout for each exercise. When I say I'm done, call finish_workout. Only use log_workout for a workout that's already over. If I say it's a rest day, call log_rest_day.

Resolve exercise names against FitFo's catalog first so they match what's already in my history, and use the weights and reps exactly as I say them. Before I train, check my recovery map and my last session for that lift so you can tell me what I did last time.

Two things to remember. Finishing or logging a workout isn't silent. It counts toward my streak and points and can post to the community feed, so tell me when that happens. And don't invent sets. If I'm vague, ask.

You can read my training, log workouts and food, and plan sessions. You can't message anyone, post publicly unless I explicitly allowed it, spend money, change my account, or see anything from my WHOOP, Garmin, or Apple Health. FitFo doesn't pass wearable data to connected apps.

Browser assistant

  • Instinct
  • ChatGPT Work’s cloud browser
  • Claude in Chrome
https://www.fitfo.app/agent
How to connect
  1. In the FitFo app: Settings, Connected AI, Connect an assistant. Pick yours.
  2. You get a pairing code: 8 characters, single-use, good for 10 minutes.
  3. The app writes the whole message with your code in it. Copy it and send it to your assistant. It looks like this:
Message to your assistant
Go to https://www.fitfo.app/agent and sign in with the pairing code XXXX-XXXX. That's my workout app, and the page is plain HTML built for you, so read it as-is. The code works once and expires 10 minutes after I got it. If it fails, ask me for a new one, because retrying the same code won't work.

The home page lists every page, shows my units and timezone, and says whether a workout is in progress. https://www.fitfo.app/agent/actions.json is the machine-readable version, including what each error means.

When I say I'm starting a workout, start one at /agent/session. Its timer starts then. Each time I tell you an exercise, add it to that same workout, one exercise per line like "Bench press 3x5 @185". Never start a new workout for each exercise. When I say I'm done, finish it. If I tell you about a workout that's already over, log it at /agent/log instead. If I say it's a rest day, mark it at /agent/rest-day.

After each add, tell me what the page says it added, so I can catch a wrong match. Before you finish a workout or log a separate one, show me what you're about to write, and afterwards tell me exactly what the confirmation page said. It reports whether it extended my streak or posted to the feed, and I want to know.

You can read my training, log workouts and food, and plan sessions. You can't message anyone, post publicly unless I explicitly allowed it, spend money, change my account, or see anything from my WHOOP, Garmin, or Apple Health. FitFo doesn't pass wearable data to connected apps.
  1. Your assistant signs in at https://www.fitfo.app/agent with the code and starts from there.

The code is worth nothing once redeemed, and expires after 10 minutes unused. Your FitFo password never reaches the assistant. That is why this uses a code, not a login form.

REST API

  • Anything that can make an HTTP request
https://api.fitfo.app/v1/agent
Machine-readable entry points

A versioned API for anything that does not speak MCP. Entry points:

Muse: not yet

Meta has not published a connector spec for Muse, so there is nothing to build against yet. What Muse's custom-connector option would need, a documented REST API with standard OAuth, already exists. What is missing is on Meta's side.

It can never

  • Message anyone
  • Spend money
  • Change your account
  • Touch other members
  • Read your DMs
  • See WHOOP, Garmin or Apple Health
The exact rules

These are not settings. No page or endpoint for any of them exists on the member routes above, so a member's assistant cannot:

  • Send a direct message, a community chat message, or anything that reaches another person.
  • Touch money: subscriptions, coaching purchases, payment methods, coach payouts.
  • Change the account: email, phone, password, username, sign-in methods, or deleting it.
  • Act on another member's data, including friend requests, or joining or leaving a coaching relationship.
  • Read direct messages or private coaching conversations.
  • Read anything synced from WHOOP, Garmin or Apple Health. Those vendors' terms do not let us pass their data to a third party, even with your consent.

A coach's own assistant has a separate surface, below.

How it logs a workout

Like you would: start, add each exercise, finish. One workout, not one per exercise.

  • Start starts the timer. If one is already going, it returns that one.
  • Add puts an exercise in the open workout. With none open, it starts one.
  • Finish logs it. That is when it counts toward your streak and points, and can post to the community feed, as if you logged it.
  • A workout that is already over is logged in one step. While one is open, FitFo refuses that unless the assistant says it is separate, so yours is never split by accident.
  • Rest days keep your streak and are not a workout. Refused if you already trained today.

A workout left open 6 hours with nothing added is never closed silently. FitFo stops the next add or start and says to finish or discard it first, so it has to ask you.

Web: /agent/session, /agent/rest-day. MCP: start_workout, add_exercises, finish_workout, log_rest_day.

Who can connect

Any account with an active subscription or an active coaching plan, including access through a coach. If access lapses, the connection pauses on its next use and picks back up once access is back. Nothing is deleted.

For coaches

A coach can connect their own assistant to run their coaching dashboard: read the inbox and client threads, answer clients, send waiting plan drafts, and handle plan-change requests and check-ins. This is separate from everything above.

  • The coach chooses, permission by permission, what it may do.
  • Anything that reaches a client shows a preview first.
  • Everything done is recorded where the coach can read it.

Start with the guide: /agent/coach/guide. Sign in at /agent/coach/login with a pairing code the coach generates (Profile, then Assistant access). Every page and form: /agent/coach/actions.json.