[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) # FitSW MCP server: Let your AI agent do the FitSW admin. > 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. 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. - Free 7-day trial, no card - Unofficial, not affiliated with FitSW - Page: https://cotlet.dev/integrations/fitsw-api-mcp-server ## What can your AI agent do in FitSW? - Onboard new clients - Assign programs - Build workouts from notes - Log in-person results - Spot low compliance - Weekly progress reports ## Does FitSW have an MCP server or an API? - FitSW has no API, webhook or developer page. - FitSW has no Zapier app. - FitSW has no connector in the ChatGPT apps directory or in Claude. | 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](https://www.fitsw.com/faq/), [FitSW help for trainers](https://www.fitsw.com/help/for-trainers/), [FitSW help: create a multi-day program (web)](https://www.fitsw.com/help/for-trainers/workouts-trainers/how-to-create-a-multi-day-program-web/) ## How does the FitSW MCP server work? 1. **Sign in to FitSW.** Once, in a browser we host for you. 2. **Connect your AI agent.** One address in its settings. 3. **Hand it the busywork.** 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. ## How to connect FitSW to your AI agent 1. **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. 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. 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. 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" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` 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, Tool: fitsw_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: fitsw_write ``` ## All 7 FitSW MCP tools ### Clients Search by name; compliance and results come with each client. Adding a client sends their invite, so it waits for your OK. - **List clients** (`list_clients`, read): Clients, searchable by name, with program and compliance. - **Get client** (`get_client`, read): One client with workouts, results, metrics and nutrition. - **Add client** (`add_client`, write, asks first): Adds a client and invites them to the app. ### Workouts and programs New workouts sit in your library and logged results reach no one, so both run at once. Assigning waits for your OK. - **List programs** (`list_programs`, read): Your workouts and multi-day programs. - **Create workout** (`create_workout`, write): Builds a workout in your library from exercises, sets and reps. - **Assign program** (`assign_program`, write, asks first): Assigns a workout or program to a client from a start date. - **Record workout result** (`record_result`, write): Enters a client's results for a session you trained in person. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/fitsw-api-mcp-server#tools ## Who can see my FitSW session, and how do I revoke it? - **What we store.** Your signed-in FitSW profile, AES-256-GCM encrypted, in Finland. No password. - **What your agent gets.** The 7 FitSW tools, never the session cookie. - **What the session sees.** What your trainer login sees: clients, workouts, programs, results, nutrition. - **What no tool touches.** Payments, subscriptions, messages, client documents, deletes. - **If FitSW signs you out.** You sign in again yourself, in the same Cloud Browser. - **How to cut access.** 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](https://cotlet.dev/security.md)). ## What happens when FitSW changes? - **12 h** between tests of the FitSW reads - **24 h** between tests of sends a customer would notice - **$0** for a call to a FitSW tool paused for repair 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](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the week.** Completed and missed workouts per client. 2. **Works out compliance.** Against the threshold you set. 3. **Lists who is behind.** With the sessions they missed. 4. **Leaves the message to you.** Nothing is sent to clients. | 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. MCP call: ``` { "name": "assign_program", "arguments": { "client_id": "U-31940", "program": "Beginner full body", "start": "2026-11-16" } } ``` REST: ``` 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"}' ``` Response: ``` { "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. ## How much does the FitSW MCP server cost? **About $23 a month** for 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 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Works on your current FitSW plan FitSW publishes no usage counts, so the month is our example. Dollars at the $29 pack rate. ## FitSW MCP server on GitHub, Zapier or hosted: which to use | 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. ## Who runs Cotlet 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. ## FitSW MCP server: questions ### How do I get access? 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. ### How do I connect FitSW to ChatGPT or Claude? 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. ### What can ChatGPT do in FitSW? 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. ### Is there an official ChatGPT or Claude app for FitSW? 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. ### Can ChatGPT assign workouts in FitSW? 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. ### Can ChatGPT check client compliance in FitSW? Yes, with Cotlet. ChatGPT lists clients below the compliance you set and the workouts they missed, so you know whom to message. ### Can ChatGPT build workouts in FitSW? 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. ### Do my clients need to do anything? No. Clients keep their FitSW app and free login. What your agent assigns shows up in their app as usual. ### Is the MCP server different from the REST API? 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. ### Is Cotlet affiliated with FitSW? No. Cotlet is independent and not affiliated with FitSW. --- 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.