[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) # WellnessLiving MCP server: Let your AI agent run the WellnessLiving front desk. > WellnessLiving has no MCP server and no ChatGPT or Claude app. Its API starts with a staging request, and "Production API access is a paid subscription"; its Zapier app sends events such as new leads (WellnessLiving help, checked 9 Nov 2026). Cotlet runs 5 WellnessLiving tools hosted, over MCP for agents and REST for scripts, in your own staff login. Your AI agent books classes and appointments from messages, finds members who stopped coming and logs leads. Sign in to WellnessLiving once in your own Cloud Browser. No paid API. - Free 7-day trial, no card - Unofficial, not affiliated with WellnessLiving - Page: https://cotlet.dev/integrations/wellnessliving-api-mcp-server ## What can your AI agent do in WellnessLiving? - Book classes from messages - Book appointments - Find quiet members - Log leads - See spaces left - Look up any client ## Does WellnessLiving have an MCP server or an API? - WellnessLiving charges for production API access. - Its Zapier app sends events and books nothing. - WellnessLiving has no connector in the ChatGPT apps directory or in Claude. | What you need | WellnessLiving API | Zapier app | Cotlet | |---|---|---|---| | Book classes and appointments | Paid | No | Yes, after your OK | | Clients and memberships | Paid | Profile events | Yes | | Leads | Paid | Lead events | Yes | | Ask in ChatGPT or Claude | No | No | Yes | | Developer needed | Yes | Zap setup | No | Checked 8 Nov 2026. Sources: [WellnessLiving help: Getting started with the API](https://help.wellnessliving.com/en/articles/10697645-getting-started-with-the-wellnessliving-api), [WellnessLiving on Zapier](https://zapier.com/apps/wellnessliving/integrations), [WellnessLiving pricing](https://www.wellnessliving.com/pricing/) ## How does the WellnessLiving MCP server work? 1. **Sign in to WellnessLiving.** 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 WellnessLiving password, and no booking goes through until you approve it. ## How to connect WellnessLiving to your AI agent 1. **Sign in to WellnessLiving in a Cloud Browser.** Create a Cotlet account, open WellnessLiving in its Cloud Browser, sign in with your staff 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. WellnessLiving shares the address `https://cotlet.dev/mcp/v1` with every other app you enable, so one connector covers them all. Turned WellnessLiving on after connecting? Refresh the connector and the 5 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: wellnessliving_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: wellnessliving_write ``` ## All 5 WellnessLiving MCP tools ### Schedule Classes and appointments with spaces left. Bookings wait for your OK. - **List schedule** (`list_schedule`, read): Classes and appointments for a day or range, with spaces left. - **Book client into class** (`book_class`, write, asks first): Books a client into a class with their pass or membership. - **Book appointment** (`book_appointment`, write, asks first): Books a service appointment for a client. ### Clients and leads Search clients; new leads reach no one by themselves, so they run at once. - **List clients** (`list_clients`, read): Clients with membership, passes left and last visit. - **Add lead** (`add_lead`, write): Adds a lead from an enquiry. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/wellnessliving-api-mcp-server#tools ## Who can see my WellnessLiving session, and how do I revoke it? - **What we store.** Your signed-in WellnessLiving profile, AES-256-GCM encrypted, in Finland. No password. - **What your agent gets.** The 5 WellnessLiving tools, never the session cookie. - **What the session sees.** What your staff login sees: schedule, clients, memberships, leads. - **What no tool touches.** Point of sale, payments, prices, marketing sends, client notes, deletes. - **If WellnessLiving 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 WellnessLiving 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 WellnessLiving changes? - **12 h** between tests of the WellnessLiving reads - **24 h** between tests of sends a customer would notice - **$0** for a call to a WellnessLiving tool paused for repair When WellnessLiving moves a button on the schedule or renames a client tab, 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. **Finds the client.** By name, email or phone. 2. **Checks the class.** Spaces left. 3. **Proposes the booking.** With the pass it uses. 4. **Waits, then books.** The booking shows up in your Cotlet console first. | Action | Undo | |---|---| | Book a class or appointment | Yes, cancel the booking | | Add a lead | Yes, edit it in WellnessLiving | 2 of 5 tools ask first: book_class, book_appointment. New leads reach no customer, so they run at once. You can turn the wait off per tool once you trust a routine. MCP call: ``` { "name": "book_class", "arguments": { "class_id": "CL-8812", "client_id": "C-20977" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/wellnessliving/clients/C-20977/class/CL-8812 \ -H "Authorization: Bearer $COTLET_API_KEY" ``` Response: ``` { "class_id": "CL-8812", "client": "Jordan Ellis", "status": "Booked", "pass_left": 6 } ``` A cron job or n8n flow can call the same tools over REST at `/api/v1/wellnessliving` with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path. ## How much does the WellnessLiving MCP server cost? **About $37 a month** for a studio with about 300 members, 6,340 credits. Your WellnessLiving plan stays as it is. | Job | Calls | Credits | |---|---|---| | Class booking from a message | 3 × 120 | 3,600 | | Appointment booked | 2 × 40 | 800 | | Quiet members, weekly | 1 × 4 | 40 | | Lead added | 1 × 40 | 400 | | Cloud Browser, 30 days | | 1,500 | | Total | | 6,340 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Works on any WellnessLiving plan WellnessLiving publishes no booking counts, so the month is our example. Dollars at the $29 pack rate. ## WellnessLiving MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | WellnessLiving API | Schedule, clients and sales for your own developer. | Paid production access; you build and host the code. | | Zapier app | Lead and client events to other apps. | Books nothing. | | By hand | Every screen of WellnessLiving, one booking at a time. | Your front desk's time. | If you already pay for production API access and have a developer, building on it is cheaper for syncing data. To book and follow up from ChatGPT or Claude this week, Cotlet works in the WellnessLiving 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 WellnessLiving tools go to contact@cotlet.dev. ## WellnessLiving MCP server: questions ### How do I get access? Sign up free at https://cotlet.dev, open WellnessLiving under Integrations in the console and sign in to WellnessLiving in its Cloud Browser. The trial starts with your first app and asks for no card. ### How do I connect WellnessLiving to ChatGPT or Claude? Sign up at cotlet.dev, log in to WellnessLiving 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 WellnessLiving account through Cotlet, in their phone apps too. ### What can ChatGPT do in WellnessLiving? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in WellnessLiving: book from DMs; win back members; book a massage. 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 WellnessLiving? No. WellnessLiving has no ChatGPT or Claude connector of its own and WellnessLiving 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 book classes in WellnessLiving? Yes, with Cotlet. ChatGPT checks spaces and books the client with their pass or membership, after your OK. ### Can ChatGPT book appointments in WellnessLiving? Yes, with Cotlet. ChatGPT books services such as massages with the staff member and time you name, after your OK. ### Can ChatGPT find members who stopped coming in WellnessLiving? Yes, with Cotlet. ChatGPT lists clients with no visit in the days you name. ### Is the MCP server different from the REST API? Only in how it is called. Both carry the same 5 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with WellnessLiving? No. Cotlet is independent and not affiliated with WellnessLiving. --- 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.