Health & fitness
Trainerize
Clients, programs, check-ins and messages for your Trainerize business.
14 endpoints
WeStrive's API key connects its Zapier app, with no published endpoint reference and no MCP server (checked 13 Nov 2026). Cotlet runs a hosted WeStrive MCP server with 15 tools that ChatGPT and Claude use in your own trainer account. Programs, reminders, messages and invoices wait for your OK.
15 tools Read and write
WeStrive lets each trainer generate an API key from the lightning icon in the dashboard, and its help center uses that key to connect the WeStrive Zapier app. Its API page at westrive.com/api shows a heading and no endpoint reference. No WeStrive MCP server and no official ChatGPT or Claude connector was verified.
| What you need | WeStrive + Zapier | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server verified | Copy and paste | Hosted MCP server |
| Add clients and react to payments | Zap triggers | One at a time | Invites after your OK |
| Programs, reminders, progress, messages | Not documented | Client by client | 15 tools, writes after your OK |
| Run from n8n or a script | Inside Zapier | Manual only | REST, same key |
Checked 13 Nov 2026. Sources: WeStrive API page · WeStrive integrations · WeStrive pricing · Help: How does WeStrive and Zapier work? · Help: Assign a program · Help: Client Reminders & Events · Help: Track client progress · Help: Onboarding surveys and applications · Help: Bill clients with Stripe · Help: Mass message all clients · Help: Delete or archive a client · Help: Automated program price or workouts
Once, in a browser we host for you.
One address in its settings.
It onboards the client, you approve each step.
Your agent works in your own signed-in Cloud Browser. Anything your clients see in the app, and every invoice, waits for your OK. Who can see your session
Sign in to WeStrive in a Cloud Browser. Open train.westrive.com in your Cotlet Cloud Browser and log in with your own trainer or gym account.
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.
WeStrive answers on the shared address https://cotlet.dev/mcp/v1, the same one as every other app you enable, so one connector is all you add. Enabled WeStrive after connecting? Refresh the connector to see its 15 tools.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth 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" // ~/.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: westrive_read One tool per trainer workflow in the WeStrive Help Center, with related articles merged. Tools with an `action` only read on `list` and `get`; the other actions write and ask first.
The client list, invites, applications from your trainer website, notes, tags and archiving.
The same list as the Clients tab, and what Download Client List exports. Pending holds the applications from your trainer website, Invited the clients who have not signed up yet. Archived clients are not billed by WeStrive. Nothing is changed.
MCP callwestrive_read → list_clients
REST endpointGET https://cotlet.dev/api/v1/westrive/clients
| Name | Type | Description |
|---|---|---|
| section string | string | One of `active`, `pending`, `invited`, `archived`. Defaults to `active`. |
| tag string | string | Only clients with this tag. |
{
"section": "active",
"clients": [
{
"client": "Example Client",
"tags": [
"Online"
],
"program": "12-week strength",
"started": "2026-10-05"
},
{
"client": "Sample Athlete",
"tags": [
"In person"
],
"program": "Hybrid conditioning",
"started": "2026-11-02"
}
]
} WeStrive emails the client that they were added, and they sign up in the WeStrive app. If the email does not arrive, they can still sign up in the app with the same address. The invite reaches the client, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → invite_client
REST endpointPOST https://cotlet.dev/api/v1/westrive/client/invite
| Name | Type | Description |
|---|---|---|
| email string required | string | The client's email. |
| name string | string | For a client already in the Invited section without an email: their name. |
{
"email": "jane@example.com"
} {
"email": "new.client@example.com",
"section": "invited",
"invite_sent": true
} Applications come from your trainer website, where applicants answer your onboarding questions first. `get` returns those answers. Approving makes the person your client; message them afterwards with send_message. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → review_client_application
REST endpointPOST https://cotlet.dev/api/v1/westrive/client-application/review
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `approve`, `deny`. `list` and `get` only read. |
| client string required | string | Client name or email, as list_clients returns it. |
{
"action": "action",
"client": "client"
} {
"client": "New Applicant",
"answers": [
{
"question": "What type of training do you like to do?",
"answer": "Strength, three days a week"
},
{
"question": "What is your injury history?",
"answer": "Old left knee sprain"
}
],
"status": "pending"
} Notes live on the client's Notes page, for goals and call notes. Tags group clients so programs and calendars can be assigned in bulk. Archive pauses a client and stops billing for them; delete removes their data for good and cannot be undone. A client attached to another trainer at your gym must be transferred to you before you delete them. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → manage_client
REST endpointPOST https://cotlet.dev/api/v1/westrive/client/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `note`, `tag`, `archive`, `delete`. `list` and `get` only read. |
| client string required | string | Client name or email, as list_clients returns it. |
| text string | string | For `note`: the note. For `tag`: the tag name. |
{
"action": "action",
"client": "client"
} {
"client": "Example Client",
"action": "tag",
"text": "Online",
"saved": true
} Your program library, assignments with start dates, your own exercises and each client's Progress tab.
Programs are built in the WeStrive program builder; the agent reads and edits them but does not import spreadsheets, which WeStrive does not support. A program assigned to several clients at once changes for all of them when edited. An automated program is locked once a client buys it; only the WeStrive team can unlock it. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → manage_programs
REST endpointPOST https://cotlet.dev/api/v1/westrive/programs/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `details`, `uncomplete`, `pdf`. `list` and `get` only read. |
| program string | string | Program name, for everything but `list`. |
| fields object | object | For `details`: program type, duration and description. |
| client string | string | For `uncomplete`: the client whose completed program goes back on their Train tab. |
{
"action": "action"
} {
"programs": [
{
"program": "12-week strength",
"type": "Strength",
"weeks": 12,
"tab": "Templates"
},
{
"program": "Hybrid conditioning",
"type": "Conditioning",
"weeks": 8,
"tab": "Drafts"
}
]
} Each week of the program needs at least one day with an exercise, or WeStrive will not assign it. One program assigned to several clients stays shared: edits reach every calendar. Moving a start date restarts every day of the program, though personal records stay in Progress. The program appears in the client's app, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → assign_program
REST endpointPOST https://cotlet.dev/api/v1/westrive/program/assign
| Name | Type | Description |
|---|---|---|
| program string required | string | Program name. |
| clients array | array | Clients to assign it to. Give several to assign one shared program. |
| tag string | string | Or a tag: every client with it. |
| start_date string required | string | ISO date the program starts. A future date works for clients who have not paid yet. |
| keep_draft boolean | boolean | Keep a copy in Drafts to reuse. |
| change_start boolean | boolean | Set true to move the start date of a program the client already has. |
{
"program": "12-week strength",
"clients": [
"Example Client",
"Sample Athlete"
],
"start_date": "2026-11-16",
"keep_draft": true
} {
"program": "12-week strength",
"clients": [
"Example Client",
"Sample Athlete"
],
"start_date": "2026-11-16",
"shared": true,
"assigned": true
} WeStrive already has a library of exercise videos shot by certified trainers; this adds your own next to them. A photo is added for you when you give none. New exercises reach no one until you put them in a program. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → add_exercise
REST endpointPOST https://cotlet.dev/api/v1/westrive/exercises
| Name | Type | Description |
|---|---|---|
| name string required | string | Exercise name. |
| video_url string required | string | YouTube or Vimeo link. YouTube Shorts links need the watch?v= form. |
| measurement string | string | What the client logs: reps, weight, time, distance and the like. |
| category string | string | Exercise category. |
| note string | string | Coaching note. |
{
"name": "Jane Doe",
"video_url": "https://example.com"
} {
"name": "Tempo goblet squat",
"measurement": "reps",
"category": "Legs",
"saved": true
} The Progress tab holds measurements, workout records with personal records, the workout journal filled from assigned programs, bodyweight and progress photos. Clients add most of it from the app. Uploads and comparisons stay inside your account. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → manage_progress
REST endpointPOST https://cotlet.dev/api/v1/westrive/progress/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `upload_photo`, `compare_photos`. `list` and `get` only read. |
| client string required | string | Client name or email, as list_clients returns it. |
| section string | string | For `get`: `measurements`, `workout_records`, `journal`, `bodyweight` or `photos`. Leave empty for a summary. |
| photo_url string | string | For `upload_photo`: a link the Cloud Browser can download. |
| photo_type string | string | For `upload_photo`: `front`, `back`, `legs` or `side`. |
| date string | string | For `upload_photo`: ISO date of the photo. |
| photos array | array | For `compare_photos`: the two photo dates to put side by side. |
{
"action": "action",
"client": "client"
} {
"client": "Example Client",
"bodyweight": [
{
"date": "2026-10-05",
"kg": 82.4
},
{
"date": "2026-11-09",
"kg": 79.8
}
],
"workout_records": [
{
"exercise": "Barbell Back Squat",
"one_rep_max_kg": 120,
"date": "2026-11-06"
}
]
} Reminders, nutrition goals and surveys that show up in the client's app on a schedule.
These are the Add Reminders items of the client's Client Calendar. They reach the client in the WeStrive app on the schedule you set, and a day with an open reminder shows red in their calendar until it is done. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → schedule_client_reminders
REST endpointPOST https://cotlet.dev/api/v1/westrive/client-reminders/schedule
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name or email, as list_clients returns it. |
| kind string required | string | One of `weigh_in`, `progress_photos`, `message`, `fitness_test`, `measurements`, `habit`, `survey`. |
| content string | string | The message text, habit, test or survey name. |
| first_date string required | string | ISO date of the first one. |
| repeat string | string | `once`, `weekly` or `monthly`, with an interval such as every 2 weeks. |
| until string | string | ISO date to stop repeating. |
{
"client": "client",
"kind": "kind",
"first_date": "first date"
} {
"client": "Example Client",
"kind": "weigh_in",
"first_date": "2026-11-17",
"repeat": "every 2 weeks",
"until": "2026-12-29",
"scheduled": 4
} This is the Nutrition Goal button on the client's calendar. The client sees the goal in the app, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → set_nutrition_goals
REST endpointPUT https://cotlet.dev/api/v1/westrive/nutrition-goals
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name or email, as list_clients returns it. |
| calories number required | number | Daily calorie total. |
| protein_g number | number | Protein in grams. |
| carbs_g number | number | Carbohydrates in grams. |
| fat_g number | number | Fat in grams. |
| schedule string | string | Which days the goal repeats on, for example training days and rest days. |
{
"client": "client",
"calories": 1
} {
"client": "Example Client",
"calories": 2300,
"protein_g": 170,
"carbs_g": 240,
"fat_g": 70,
"schedule": "Mon, Wed, Fri",
"saved": true
} Surveys live under Client Reminders, Surveys on the Clients tab. Clients answer them on the website or in the app. Send one with schedule_client_reminders. Creating a survey reaches no one. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → manage_surveys
REST endpointPOST https://cotlet.dev/api/v1/westrive/surveys/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| name string | string | For `create`: the survey name. |
| questions array | array | For `create`: 1 to 10 questions, each with a type: `multiple_choice`, `short` or `long`. |
{
"action": "action"
} {
"name": "Onboarding",
"questions": 3,
"saved": true
} Inbox messages, scheduled auto-messages to everyone, and Stripe invoices.
Clients reply from the inbox in their app. A sent message reaches the client and cannot be recalled by the agent. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → send_message
REST endpointPOST https://cotlet.dev/api/v1/westrive/messages
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `send`. `list` and `get` only read. |
| to string required | string | A client or a group chat. |
| text string | string | For `send`: the message. |
| attachment_url string | string | For `send`: an optional image or file to attach. |
{
"action": "action",
"to": "to"
} {
"to": "Example Client",
"text": "Great squat PR this week. New block starts Monday, check your Train tab.",
"sent": true
} This is Auto-message in the Add Reminders menu, one of WeStrive's two ways to reach all clients at once besides Announcements. It reaches every client, so the agent shows you the text and schedule first. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → send_mass_message
REST endpointPOST https://cotlet.dev/api/v1/westrive/mass-messages
| Name | Type | Description |
|---|---|---|
| text string required | string | The message. |
| link string | string | Optional link. |
| attachment_url string | string | Optional photo or document. |
| send_at string required | string | ISO date and time of the first send. |
| repeat string | string | `once`, `weekly` or `monthly`. |
{
"text": "text",
"send_at": "send at"
} {
"text": "Holiday hours: the studio is closed Dec 24 to 26.",
"send_at": "2026-12-20T09:00",
"repeat": "once",
"recipients": 38,
"scheduled": true
} Invoices go through the free Stripe billing account WeStrive sets up for each trainer. The client gets the invoice in their WeStrive account and pays it with a card on file. Cancel stops a monthly invoice. Creating one reaches the client and asks for money, so it waits for your OK. Withdrawing your Stripe balance stays with you. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → manage_invoices
REST endpointPOST https://cotlet.dev/api/v1/westrive/invoices/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `cancel`. `list` and `get` only read. |
| client string | string | For `create` and `cancel`; leave empty with `list` for every client. |
| title string | string | For `create`: invoice title. |
| type string | string | For `create`: `one_time` or `monthly`. |
| amount number | number | For `create`: amount in your Stripe currency. |
{
"action": "action"
} {
"invoices": [
{
"client": "Example Client",
"title": "Online coaching, November",
"type": "monthly",
"amount": 180,
"status": "paid"
},
{
"client": "Sample Athlete",
"title": "Ten session pack",
"type": "one_time",
"amount": 650,
"status": "pending"
},
{
"client": "Demo Member",
"title": "Online coaching, November",
"type": "monthly",
"amount": 180,
"status": "pending"
}
]
} For gym accounts: locations, coaches and moving clients between them.
From the Gyms tab. A coach who already trains on WeStrive joins your gym with their clients and programs once they click the emailed link. A head location can add, edit and transfer coaches of other locations but cannot edit those locations' clients. Invites reach other people, so each waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callwestrive_write → manage_gym_team
REST endpointPOST https://cotlet.dev/api/v1/westrive/gym-team/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add_location`, `add_coach`, `transfer_coach`, `transfer_clients`. `list` and `get` only read. |
| email string | string | For `add_location` and `add_coach`: the owner's or coach's email. |
| coach string | string | For `transfer_coach` and `transfer_clients`. |
| to string | string | The location or coach that receives them. |
| clients array | array | For `transfer_clients`. |
{
"action": "action"
} {
"action": "add_coach",
"email": "coach@example.com",
"invite_sent": true
} Your logged-in WeStrive browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 15 WeStrive tools. The session cookie stays in the Cloud Browser.
The clients your trainer or gym login can open. A head location still cannot edit other locations' clients.
Your Stripe payouts and withdrawals, your plan and branding, your landing page and the Zapier key.
You log in again yourself, in the same Cloud Browser.
Disable WeStrive for agents, reset the browser, or change your WeStrive password.
Cotlet never sees your WeStrive password: you type it, and the agent works with the session it leaves. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
WeStrive's homepage lists a nutrition plan builder as coming soon. When a release like that changes the screens, Cotlet updates the WeStrive server so your agent and scripts keep the same calls.
Program rules stay WeStrive's: a shared program changes for every client on it, a moved start date restarts the program, and an automated program is locked once bought.
If WeStrive logs you out, one click in the Cotlet console reopens the Cloud Browser so you can log in again.
| Action | How to put it right |
|---|---|
| Program on the wrong date | Move the start date with assign_program; the program restarts, records stay |
| Program marked complete | Call manage_programs with uncomplete to put it back on the client's Train tab |
| Monthly invoice sent by mistake | Cancel it with manage_invoices; tell the client |
| Client deleted | WeStrive cannot retrieve deleted client data; archive instead next time |
14 of the 15 tools ask first: by default you confirm each call, and you can switch that off per tool. list_clients only reads and runs at once.
{
"name": "assign_program",
"arguments": {
"program": "12-week strength",
"clients": [
"Example Client",
"Sample Athlete"
],
"start_date": "2026-11-16",
"keep_draft": true
}
} curl -X POST https://cotlet.dev/api/v1/westrive/program/assign \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"program":"12-week strength","clients":["Example Client","Sample Athlete"],"start_date":"2026-11-16","keep_draft":true}' {
"program": "12-week strength",
"clients": [
"Example Client",
"Sample Athlete"
],
"start_date": "2026-11-16",
"shared": true,
"assigned": true
} The example gives two clients one shared copy of 12-week strength from 16 November and keeps a draft for reuse; an edit to the shared copy reaches both calendars. A cron job or n8n flow can make the same call over REST at /api/v1/westrive with the same key and price, in JSON. Failed calls are free.
About $20 a monthfor a trainer with about 30 clients, 3,500 credits. Your WeStrive plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Weekly progress review, 15 online clients | 16 × 4 | 640 |
| New client onboarding | 4 × 4 | 160 |
| Program assignments and start dates | 1 × 20 | 200 |
| Client reminders scheduled | 1 × 30 | 300 |
| Messages to clients | 1 × 44 | 440 |
| Invoices listed, sent and chased | 3 × 4 | 120 |
| Nutrition goals for new blocks | 1 × 10 | 100 |
| Scheduled mass messages | 1 × 4 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 200 calls | 3,500 |
The smallest pack, 5,000 credits for $29, covers this month. A gym with several coaches uses more calls.
Credit packs are one-time purchases, not a subscription. The month above is our own example, not measured customer usage.
| 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 |
|---|---|---|
| WeStrive + Zapier | With your WeStrive key: new clients, paid invoices and invites move between apps. | Triggers and simple actions; no programs, reminders or messages. |
| Auto-messages and reminders | WeStrive's own scheduling sends recurring messages and check-ins. | You still set each one up client by client. |
| By hand | Work the Clients, Programs and Inbox pages yourself. | Client by client, when you have the time. |
If a Zap already moves your new clients into a sheet or a mailing list, keep it. Cotlet fits when ChatGPT, Claude or a script should do the coaching admin inside WeStrive itself, from your own login, with nothing to host.
Behind Cotlet is Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019 and run by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Send questions about the WeStrive tools to contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=westrive, turn on WeStrive under Integrations in the console and log in at https://train.westrive.com/ in your Cloud Browser. Then connect your AI agent and ask it about your clients. The trial needs no card.
WeStrive lets each trainer generate an API key from the lightning icon in its dashboard, which connects its Zapier app; its API page publishes no endpoint reference (checked 13 Nov 2026). No WeStrive MCP server and no official ChatGPT or Claude connector was verified. Cotlet does not use that key: it works in your own signed-in WeStrive account.
No. WeStrive's help center says you do not pay for archived clients, and an archived client can come back later. Deleting a client removes their data for good, so manage_client archives unless you ask it to delete.
No. WeStrive locks an automated program after its first purchase, and only the WeStrive team unlocks it, on request to help@westrive.com. Before the first purchase, manage_programs can edit it like any other program.
No. WeStrive itself does not import spreadsheets of programs; programs are built in its program builder. The agent can read, edit details of, assign and export programs as PDF.
Only in how it is called. Both carry the same 15 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST. This is Cotlet's API key, not the WeStrive key for Zapier.
No. Cotlet is independent and not affiliated with WeStrive.
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