Health & fitness
Trainerize
Clients, programs, check-ins and messages for your Trainerize business.
14 endpoints
Your AI agent onboards clients with a program, builds workouts from your notes, logs in-person results and spots who is falling behind. Sign in to FitSW once in your own Cloud Browser. No API, no Zapier.
7 tools Read and write
FitSW has no MCP server, no ChatGPT or Claude app, no public API and no Zapier app (checked 9 Nov 2026). Cotlet runs 7 FitSW tools hosted, over MCP for agents and REST for scripts, in your own FitSW login.
| What you need | FitSW API | By hand | Cotlet |
|---|---|---|---|
| Clients and progress | No API | Yes, one by one | Yes |
| Assign programs | No API | Yes, one by one | Yes, after your OK |
| Compliance across clients | No API | Client by client | Yes |
| Ask in ChatGPT or Claude | No | No | Yes |
| Zapier app | None | None | Not needed |
Checked 8 Nov 2026. Sources: FitSW FAQ · FitSW help for trainers · FitSW help: create a multi-day program (web)
Once, in a browser we host for you.
One address in its settings.
It drafts the work, you OK what customers get.
We never keep your FitSW password, and nothing a client sees in their app changes until you approve it. Who can see your session
Sign in to FitSW in a Cloud Browser. Create a Cotlet account, open FitSW in its Cloud Browser, sign in with your trainer login and press Enable for agents.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
FitSW shares the address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned FitSW on after connecting? Refresh the connector and the 7 tools appear.
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: fitsw_read Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: fitsw_write Search by name; compliance and results come with each client. Adding a client sends their invite, so it waits for your OK.
Returns clients with ID, current program, compliance for the last 7 days and last workout.
MCP callfitsw_read → list_clients
REST endpointGET https://cotlet.dev/api/v1/fitsw/clients
| Name | Type | Description |
|---|---|---|
| query string | string | Name or email. |
| max_compliance integer | integer | Only clients at or below this compliance percent. |
| page integer | integer | Page number. Default: 1. |
{
"clients": [
{
"client_id": "U-31877",
"name": "Marcus Reed",
"program": "Hypertrophy 4-day",
"compliance_7d": "50%",
"last_workout": "2026-11-05"
}
],
"page": 1
} Returns the client's scheduled and completed workouts, recent results, metrics such as weight, and nutrition plan.
MCP callfitsw_read → get_client
REST endpointGET https://cotlet.dev/api/v1/fitsw/clients/{client_id}
| Name | Type | Description |
|---|---|---|
| client_id string required | string | Client ID from list_clients. |
{
"client_id": "client_8c41d2"
} {
"client_id": "U-31877",
"name": "Marcus Reed",
"completed": [
{
"workout": "Upper A",
"date": "2026-11-05"
}
],
"missed": [
{
"workout": "Lower A",
"date": "2026-11-07"
}
],
"weight_kg": 84.1,
"nutrition": "2,600 kcal"
} Creates the client the way Add Client on the web does; FitSW emails their free login. By default you confirm each call; you can switch that off for this tool.
MCP callfitsw_write → add_client
REST endpointPOST https://cotlet.dev/api/v1/fitsw/clients
| Name | Type | Description |
|---|---|---|
| first_name string required | string | First name. |
| last_name string required | string | Last name. |
| email string required | string | Email for the invite. |
{
"first_name": "first name",
"last_name": "last name",
"email": "jane@example.com"
} {
"client_id": "U-31940",
"name": "Olivia Hartmann",
"status": "Invited"
} New workouts sit in your library and logged results reach no one, so both run at once. Assigning waits for your OK.
Returns workouts and programs by name and length, so the agent assigns the exact one.
MCP callfitsw_read → list_programs
REST endpointGET https://cotlet.dev/api/v1/fitsw/programs
| Name | Type | Description |
|---|---|---|
| query string | string | Name contains. |
{
"programs": [
{
"name": "Hypertrophy 4-day",
"days": 28
},
{
"name": "Beginner full body",
"days": 21
}
]
} Creates the workout with exercises from the FitSW exercise list. It sits in your library until assigned, so it runs at once.
MCP callfitsw_write → create_workout
REST endpointPOST https://cotlet.dev/api/v1/fitsw/workouts
| Name | Type | Description |
|---|---|---|
| name string required | string | Workout name. |
| exercises array required | array | Exercise name, sets, reps or time, rest. |
{
"name": "Jane Doe",
"exercises": "exercises"
} {
"workout_id": "W-8812",
"name": "Lower B, knee friendly",
"exercises": 6
} Schedules the workout or program on the client's calendar; they see it in their app. By default you confirm each call; you can switch that off for this tool.
MCP callfitsw_write → assign_program
REST endpointPOST https://cotlet.dev/api/v1/fitsw/clients/{client_id}/program/assign
| Name | Type | Description |
|---|---|---|
| client_id string required | string | Client ID from list_clients. |
| program string required | string | Workout or program name. |
| start string required | string | ISO start date. |
{
"client_id": "U-31940",
"program": "Beginner full body",
"start": "2026-11-16"
} {
"client_id": "U-31940",
"program": "Beginner full body",
"start": "2026-11-16"
} Logs weights, reps or times for the workout, the way Enter Results does. Reaches no one, so it runs at once.
MCP callfitsw_write → record_result
REST endpointPOST https://cotlet.dev/api/v1/fitsw/clients/{client_id}/results
| Name | Type | Description |
|---|---|---|
| client_id string required | string | Client ID from list_clients. |
| workout string required | string | Workout name. |
| results array required | array | Exercise, set, weight, reps. |
{
"client_id": "client_8c41d2",
"workout": "workout",
"results": "results"
} {
"client_id": "U-31877",
"workout": "Upper A",
"date": "2026-11-09",
"logged_sets": 15
} Your signed-in FitSW profile, AES-256-GCM encrypted, in Finland. No password.
The 7 FitSW tools, never the session cookie.
What your trainer login sees: clients, workouts, programs, results, nutrition.
Payments, subscriptions, messages, client documents, deletes.
You sign in again yourself, in the same Cloud Browser.
Disable for agents, reset the browser, or change your FitSW password.
Cotlet never types your password: you sign in yourself, and the agent only uses the session. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
When FitSW moves a button in the client view or renames a section, we fix the tool and your agent calls it the same way. status.cotlet.dev checks the site, console and API every 3 minutes.
| Action | Undo |
|---|---|
| Add a client | Yes, archive them; the invite stays sent |
| Assign a program | Yes, remove it from the calendar |
| Build a workout or log results | Yes, edit it in FitSW |
2 of 7 tools ask first: add_client, assign_program. New workouts and logged results reach no customer, so they run at once. You can turn the wait off per tool once you trust a routine.
{
"name": "assign_program",
"arguments": {
"client_id": "U-31940",
"program": "Beginner full body",
"start": "2026-11-16"
}
} curl -X POST https://cotlet.dev/api/v1/fitsw/clients/U-31940/program/assign \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"program":"Beginner full body","start":"2026-11-16"}' {
"client_id": "U-31940",
"program": "Beginner full body",
"start": "2026-11-16"
} A cron job or n8n flow can call the same tools over REST at /api/v1/fitsw with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path.
About $23 a monthfor a trainer with about 30 clients, 4,030 credits. Your FitSW plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| New client onboarded | 3 × 5 | 150 |
| Compliance check, weekly | 12 × 4 | 480 |
| Workout built | 1 × 10 | 100 |
| In-person results logged | 2 × 60 | 1,200 |
| Progress report, weekly | 15 × 4 | 600 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 4,030 |
FitSW publishes no usage counts, so the month is our example. Dollars at the $29 pack rate.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| FitSW app | Clients, programs and results on your phone. | One client at a time; no questions in plain words. |
| Spreadsheet export | Copy results out to analyse them yourself. | By hand, every week. |
| By hand | Every screen of FitSW, one client at a time. | Your time between sessions. |
FitSW has no API or Zapier app, so there is nothing to connect a script to. To onboard, build and track from ChatGPT or Claude this week, Cotlet works in the FitSW account you already have.
Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the FitSW tools go to contact@cotlet.dev.
Sign up free at https://cotlet.dev, open FitSW under Integrations in the console and sign in to FitSW in its Cloud Browser. The trial starts with your first app and asks for no card.
Sign up at cotlet.dev, log in to FitSW once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your FitSW account through Cotlet, in their phone apps too.
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in FitSW: onboard a new client; spot low compliance; build a workout from a note. You ask in plain words, and anything that reaches other people waits for your OK first.
No. FitSW has no ChatGPT or Claude connector of its own and FitSW has no official MCP server (checked 9 Nov 2026). Cotlet is an independent one that works in ChatGPT, Claude, Cursor and any MCP client, on your signed-in account.
Yes, with Cotlet. ChatGPT assigns a workout or multi-day program from your library to a client from the date you give, after your OK.
Yes, with Cotlet. ChatGPT lists clients below the compliance you set and the workouts they missed, so you know whom to message.
Yes, with Cotlet. ChatGPT builds a workout from your note with exercises from the FitSW list, sets, reps and rest, and saves it to your library.
No. Clients keep their FitSW app and free login. What your agent assigns shows up in their app as usual.
Only in how it is called. Both carry the same 7 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST.
No. Cotlet is independent and not affiliated with FitSW.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy