[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) # MassageBook MCP server: Let your AI agent handle MassageBook bookings. > MassageBook has no MCP server, no ChatGPT or Claude app, no public API and no Zapier app; reports leave only as manual exports (checked 9 Nov 2026). Cotlet runs 5 MassageBook tools hosted, over MCP for agents and REST for scripts, in your own MassageBook login, for the schedule and client contact details only. Your AI agent books clients from texts, moves a sick day and brings regulars back. Sign in to MassageBook once in your own Cloud Browser. SOAP notes stay untouched. - Free 7-day trial, no card - Unofficial, not affiliated with MassageBook - Page: https://cotlet.dev/integrations/massagebook-api-mcp-server ## What can your AI agent do in MassageBook? - Book from texts - Find free slots - Move a sick day - Bring regulars back - See tomorrow's gaps - SOAP notes stay untouched ## Does MassageBook have an MCP server or an API? - MassageBook publishes no API or developer page. - MassageBook has no Zapier app. - MassageBook has no connector in the ChatGPT apps directory or in Claude. | What you need | MassageBook API | By hand | Cotlet | |---|---|---|---| | Schedule and free slots | No API | Yes, one by one | Yes | | Book or move | No API | Yes, one by one | Yes, after your OK | | Regulars due back | No API | Export | Yes | | Ask in ChatGPT or Claude | No | No | Yes | | SOAP notes | No API | Yes | Not touched | Checked 8 Nov 2026. Sources: [MassageBook integrations](https://pro.massagebook.com/features/business/integrations), [MassageBook pricing](https://pro.massagebook.com/pricing), [MassageBook login](https://www.massagebook.com/login/) ## How does the MassageBook MCP server work? 1. **Sign in to MassageBook.** 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 MassageBook password, the tools never open SOAP notes, and no booking or move goes through until you approve it. ## How to connect MassageBook to your AI agent 1. **Sign in to MassageBook in a Cloud Browser.** Create a Cotlet account, open MassageBook in its Cloud Browser, sign in with your professional 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. MassageBook shares the address `https://cotlet.dev/mcp/v1` with every other app you enable, so one connector covers them all. Turned MassageBook 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: massagebook_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: massagebook_write ``` ## All 5 MassageBook MCP tools ### Schedule Bookings and moves wait for your OK; MassageBook sends its usual reminders and intake forms. - **List appointments** (`list_appointments`, read): Appointments for a day or range, by therapist. - **Find free slots** (`find_free_slots`, read): Open times for a service, optionally with one therapist or room. - **Book appointment** (`book_appointment`, write, asks first): Books a service for a client. - **Reschedule appointment** (`reschedule_appointment`, write, asks first): Moves an appointment to a new time. ### Clients Contact details, last visit and next booking only. - **List clients** (`list_clients`, read): Clients with last visit and next booking. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/massagebook-api-mcp-server#tools ## Who can see my MassageBook session, and how do I revoke it? - **What we store.** Your signed-in MassageBook profile, AES-256-GCM encrypted, in Finland. No password. - **What your agent gets.** The 5 MassageBook tools, never the session cookie. - **What the session sees.** What your login sees on the schedule and client contact details. - **What no tool touches.** SOAP notes, intake answers, payments, gift certificates, deletes. - **If MassageBook 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 MassageBook 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 MassageBook changes? - **12 h** between tests of the MassageBook reads - **24 h** between tests of sends a customer would notice - **$0** for a call to a MassageBook tool paused for repair When MassageBook moves a button on the schedule or renames a 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, phone or email. 2. **Checks free slots.** For the service. 3. **Proposes the booking.** With time and therapist. 4. **Waits, then books.** The booking shows up in your Cotlet console first. | Action | Undo | |---|---| | Book an appointment | Yes, cancel it | | Move an appointment | Move it back; a reminder already sent stays sent | 2 of 5 tools ask first: book_appointment, reschedule_appointment. You can turn the wait off per tool once you trust a routine. MCP call: ``` { "name": "book_appointment", "arguments": { "client_id": "MC-7790", "service": "Swedish, 90 min", "start": "2026-11-13T14:00", "therapist": "Jen" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/massagebook/clients/MC-7790/appointments \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"service":"Swedish, 90 min","start":"2026-11-13T14:00","therapist":"Jen"}' ``` Response: ``` { "appointment_id": "MB-51177", "client": "Luis Ortega", "service": "Swedish, 90 min", "therapist": "Jen", "start": "2026-11-13T14:00", "status": "Confirmed" } ``` A cron job or n8n flow can call the same tools over REST at `/api/v1/massagebook` with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path. ## How much does the MassageBook MCP server cost? **About $27 a month** for a practice with 2 therapists, 4,650 credits. Your MassageBook plan stays as it is. | Job | Calls | Credits | |---|---|---| | Booking from a text | 3 × 80 | 2,400 | | Regulars due back, weekly | 1 × 4 | 40 | | Appointment moved | 3 × 15 | 450 | | Gaps checked, daily | 1 × 26 | 260 | | Cloud Browser, 30 days | | 1,500 | | Total | | 4,650 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Works on Launch, Practice and Clinic MassageBook publishes no booking counts, so the month is our example. Dollars at the $29 pack rate. ## MassageBook MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | MassageBook online booking | Clients book themselves from your page or the directory. | Only the client books; no moves or lists for you. | | Report export | Sales and clients out to a spreadsheet. | By hand, every time. | | By hand | Every screen of MassageBook, one booking at a time. | Your time between sessions. | MassageBook has no API or Zapier app, so there is nothing to connect a script to. To book, move and bring regulars back from ChatGPT or Claude this week, Cotlet works in the MassageBook 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 MassageBook tools go to contact@cotlet.dev. ## MassageBook MCP server: questions ### How do I get access? Sign up free at https://cotlet.dev, open MassageBook under Integrations in the console and sign in to MassageBook in its Cloud Browser. The trial starts with your first app and asks for no card. ### How do I connect MassageBook to ChatGPT or Claude? Sign up at cotlet.dev, log in to MassageBook 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 MassageBook account through Cotlet, in their phone apps too. ### What can ChatGPT do in MassageBook? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in MassageBook: book from texts; bring regulars back; move a sick day. 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 MassageBook? No. MassageBook has no ChatGPT or Claude connector of its own and MassageBook 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 massages in MassageBook? Yes, with Cotlet. ChatGPT finds the client, checks free slots and books the service, after your OK. ### Can ChatGPT find regulars who stopped booking in MassageBook? Yes, with Cotlet. ChatGPT lists clients not seen in the weeks you name with nothing booked. ### Does Cotlet read SOAP notes in MassageBook? No. The MassageBook tools cover the schedule and client contact details. SOAP notes and intake answers are not part of them. ### 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 MassageBook? No. Cotlet is independent and not affiliated with MassageBook. --- 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.