[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# WeStrive API and MCP server: Let your AI agent onboard clients and run the check-ins.

> 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.

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.

- Free 7-day trial, no card
- Unofficial, not affiliated with WeStrive
- Page: https://cotlet.dev/integrations/westrive-api-mcp-server

## What can your AI agent do in WeStrive?

- Approve applications and invite clients
- Assign a program to a client or a tag
- Schedule weigh-ins, photo requests and surveys
- Summarize progress before check-in calls
- Message one client or all of them
- Send and chase Stripe invoices

## Does WeStrive have an MCP server or an API?

- WeStrive's Zapier examples: add a new client to a sheet, email a client who paid an invoice, invite a client from a form response.
- Its integrations page lists Stripe, YouTube, Vimeo, Zapier, Club Automation, Apple Health, Google Fit and Fit3D.
- Every account gets a free Stripe billing account for client invoices; payouts are withdrawn from the WeStrive home page.

| 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](https://www.westrive.com/api), [WeStrive integrations](https://www.westrive.com/integrations), [WeStrive pricing](https://www.westrive.com/pricing), [Help: How does WeStrive and Zapier work?](https://intercom.help/westrive/en/articles/8726936-how-does-westrive-and-zapier-work), [Help: Assign a program](https://intercom.help/westrive/en/articles/6184205-how-do-i-assign-a-program-to-my-client), [Help: Client Reminders & Events](https://intercom.help/westrive/en/articles/6184035-how-to-add-or-schedule-client-reminders-events), [Help: Track client progress](https://intercom.help/westrive/en/articles/6184061-how-do-i-track-my-client-s-progress-on-westrive), [Help: Onboarding surveys and applications](https://intercom.help/westrive/en/articles/6184056-how-do-i-create-and-assign-a-client-onboarding-survey-to-my-client-s-profile), [Help: Bill clients with Stripe](https://intercom.help/westrive/en/articles/4665370-how-do-i-bill-clients-get-paid-as-a-trainer-stripe), [Help: Mass message all clients](https://intercom.help/westrive/en/articles/9062272-how-to-send-a-mass-message-to-all-clients), [Help: Delete or archive a client](https://intercom.help/westrive/en/articles/6184188-how-do-i-delete-or-archive-a-client), [Help: Automated program price or workouts](https://intercom.help/westrive/en/articles/8261834-how-can-i-change-the-price-or-workouts-of-my-automated-program)

## How does the WeStrive MCP server work?

1. **Log in to WeStrive.** Once, in a browser we host for you.
2. **Connect your AI agent.** One address in its settings.
3. **Hand it the admin.** 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.

## How to connect WeStrive to your AI agent

1. **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.
2. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
3. **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.

ChatGPT:

```
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
```

Claude:

```
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:

```
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
```

Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

n8n:

```
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: westrive_read
```

## All 15 WeStrive MCP tools

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.

### Clients

The client list, invites, applications from your trainer website, notes, tags and archiving.

- **List clients** (`list_clients`, read): Read your client list: active, pending applications, invited or archived, optionally by tag.
- **Invite clients** (`invite_client`, write, asks first): Add a client by email, or add the email to a client you first added by name.
- **Approve client applications** (`review_client_application`, write, asks first): Read a pending application with its onboarding answers, then approve or deny it.
- **Update client notes, tags and status** (`manage_client`, write, asks first): Add a note or tag to a client, archive them, or delete them from your account or gym.

### Programs and progress

Your program library, assignments with start dates, your own exercises and each client's Progress tab.

- **Manage programs** (`manage_programs`, write, asks first): List programs, read one, edit its details, restore a completed one, or get its PDF.
- **Assign programs** (`assign_program`, write, asks first): Assign a program to a client, several clients or a tag, or move its start date.
- **Add exercises** (`add_exercise`, write, asks first): Add your own exercise with a YouTube or Vimeo video, measurement type, note and category.
- **Read and add client progress** (`manage_progress`, write, asks first): Read a client's progress, upload a progress photo, or compare two photos side by side.

### Client calendar

Reminders, nutrition goals and surveys that show up in the client's app on a schedule.

- **Schedule client reminders** (`schedule_client_reminders`, write, asks first): Schedule weigh-ins, photo and measurement requests, habits, surveys or messages on a client calendar.
- **Set nutrition goals** (`set_nutrition_goals`, write, asks first): Set a client's macros and calorie total on their calendar, on a repeating schedule.
- **Create surveys** (`manage_surveys`, write, asks first): List your surveys, or create one with 1 to 10 questions for onboarding or check-ins.

### Messages and billing

Inbox messages, scheduled auto-messages to everyone, and Stripe invoices.

- **Message clients** (`send_message`, write, asks first): Read a conversation in the Inbox, or send a client or a group a message with a link or attachment.
- **Send scheduled mass messages** (`send_mass_message`, write, asks first): Schedule one auto-message to all clients, with a link, photo or document, once or on repeat.
- **Send and cancel invoices** (`manage_invoices`, write, asks first): List invoices with their status, send a one-time or monthly invoice, or cancel one.

### Gyms

For gym accounts: locations, coaches and moving clients between them.

- **Manage gym locations and coaches** (`manage_gym_team`, write, asks first): For gyms: add a location or a coach by email, transfer a coach to another location, or move clients.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/westrive-api-mcp-server#tools

## Who can see my WeStrive session, and how do I revoke it?

- **What we store.** Your logged-in WeStrive browser profile, AES-256-GCM encrypted, in Finland. Never your password.
- **What your agent gets.** The 15 WeStrive tools. The session cookie stays in the Cloud Browser.
- **What the session sees.** The clients your trainer or gym login can open. A head location still cannot edit other locations' clients.
- **What no tool touches.** Your Stripe payouts and withdrawals, your plan and branding, your landing page and the Zapier key.
- **If WeStrive logs you out.** You log in again yourself, in the same Cloud Browser.
- **How to cut access.** 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](https://cotlet.dev/security.md)).

## What happens when WeStrive changes?

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.

## Approvals, undo and mistakes

1. **Read the application.** review_client_application returns the answers.
2. **Approve after your OK.** The applicant becomes your client.
3. **Assign the program.** assign_program, with the start date you gave.
4. **Schedule check-ins.** schedule_client_reminders books the weigh-ins.

| 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.

MCP call:

```
{
  "name": "assign_program",
  "arguments": {
    "program": "12-week strength",
    "clients": [
      "Example Client",
      "Sample Athlete"
    ],
    "start_date": "2026-11-16",
    "keep_draft": true
  }
}
```

REST:

```
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}'
```

Response:

```
{
  "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.

## How much does the WeStrive MCP server cost?

**About $20 a month** for 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.

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Your WeStrive plan and Stripe fees as they are

Credit packs are one-time purchases, not a subscription. The month above is our own example, not measured customer usage.

## WeStrive MCP server: other ways to connect

| 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.

## Who runs Cotlet

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.

## WeStrive MCP server: questions

### How do I get access?

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.

### Does WeStrive have an API?

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.

### Do archived clients still count toward my WeStrive plan?

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.

### Can the agent edit an automated program clients already bought?

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.

### Can the agent import my programs from a spreadsheet?

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.

### Is the MCP server different from the REST API?

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.

### Is Cotlet affiliated with WeStrive?

No. Cotlet is independent and not affiliated with WeStrive.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
