Local services & SaaS
Jane App
Schedule, Wait List, intake forms, balances and reports in your Jane clinic.
14 endpoints
Lapsula offers API access on Enterprise only, and its Zapier API just reports new and changed bookings (checked 15 Nov 2026). Cotlet runs a hosted Lapsula MCP server with 6 tools that ChatGPT and Claude use in your own Lapsula account. Bookings, classes and reminder changes wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Lapsula Bookings. Lapsula Bookings is a trademark of its owner. If Lapsula Bookings's own integrations cover what you need, use them first.
6 tools Read and write
Lapsula lists API access only on its Enterprise plan, by contact. Its public Zapier API, from the Starter plan, sends four booking events: a new booking from the booking page, a new booking from the back office, a status change and a reschedule. It has no action that creates or changes a booking. No Lapsula MCP server or ChatGPT or Claude connector was found.
| What you need | Lapsula API | Zapier API | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server | Events to a Zap | Hosted MCP server |
| Know when a booking is made or changed | Enterprise only | Four booking events | Reads the calendar |
| Book, schedule classes, set capacity | Enterprise, not verified | No actions | 6 tools, writes after your OK |
| Start today on your plan | Contact sales | Starter or above | Your login, once |
Checked 15 Nov 2026. Sources: Lapsula pricing · Lapsula Zapier API documentation · Feature: Online Booking Page · Feature: Schedule and Calendar · Feature: Group Sessions and Classes · Feature: Automatic Reminders
Once, in a browser we host for you.
One address in its settings.
It checks the calendar, you approve.
Your agent works in your own signed-in Cloud Browser. Bookings, class changes and reminder settings wait for your OK. Who can see your session
Sign in to Lapsula in a Cloud Browser. Open app.lapsula.com/login in your Cotlet Cloud Browser and sign in with your own account, by email, Google or Apple.
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.
Lapsula sits on the shared address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned Lapsula on after connecting? Refresh the connector and the 6 Lapsula tools appear.
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: lapsula_bookings_read One tool per Lapsula feature: the calendar, appointments, group sessions, reminders and the booking page. The calendar read runs at once; every write asks first.
Read each team member's day, then book one-to-one appointments. Lapsula itself blocks double bookings and keeps your buffer times.
Lapsula keeps an individual calendar per team member, and Google Calendar two-way sync blocks out busy times. Returns each booking with customer, service, start, end and status (PENDING, APPROVED, DECLINED, CALLOFF or CANCELLED, the statuses Lapsula documents). It never opens medical history or session notes, and it changes nothing.
MCP calllapsula_bookings_read → view_calendar
REST endpointGET https://cotlet.dev/api/v1/lapsula-bookings/calendars/view
| Name | Type | Description |
|---|---|---|
| from string required | string | ISO date. |
| to string | string | ISO date. Default: same day. |
| team_member string | string | One team member's calendar. Empty for everyone you can see. |
{
"from": "from"
} {
"date": "2026-11-17",
"bookings": [
{
"customer": "Example Client",
"activity": "Back massage",
"team_member": "Therapist A",
"start": "2026-11-17T10:00",
"end": "2026-11-17T11:00",
"status": "APPROVED"
},
{
"customer": "Sample Client",
"activity": "Physio follow-up",
"team_member": "Therapist B",
"start": "2026-11-17T11:30",
"end": "2026-11-17T12:15",
"status": "PENDING"
}
]
} Lapsula prevents double bookings and keeps the buffer times you set between appointments, so a clash comes back as an error rather than a second booking. A booking made from the back office is APPROVED at once, and the client's reminders follow your reminder settings. By default you confirm each call; you can switch that off for this tool.
MCP calllapsula_bookings_write → schedule_appointment
REST endpointPOST https://cotlet.dev/api/v1/lapsula-bookings/appointment/schedule
| Name | Type | Description |
|---|---|---|
| customer string required | string | Client name; add phone and email for a new client. |
| phone string | string | Client phone, for reminders. |
| email string | string | Client email, for reminders. |
| activity string required | string | The service, as it is named in Lapsula. |
| team_member string required | string | Who sees the client. |
| start string required | string | ISO date and time. |
{
"customer": "Example Client",
"phone": "+34 600 000 000",
"activity": "Back massage",
"team_member": "Therapist A",
"start": "2026-11-17T10:00"
} {
"booking": "Back massage",
"customer": "Example Client",
"team_member": "Therapist A",
"start": "2026-11-17T10:00",
"end": "2026-11-17T11:00",
"status": "APPROVED"
} Classes, group therapy and workshops, once or recurring, with a capacity that drives the waiting list.
Group sessions open to bookings once saved, on your booking page too, so the agent shows the dates and the leader first. By default you confirm each call; you can switch that off for this tool.
MCP calllapsula_bookings_write → schedule_group_session
REST endpointPOST https://cotlet.dev/api/v1/lapsula-bookings/group-session/schedule
| Name | Type | Description |
|---|---|---|
| activity string required | string | Group session name, for example Pilates mat class. |
| team_member string required | string | Who leads it. |
| start string required | string | ISO date and time of the first session. |
| repeat string | string | One of `none`, `daily`, `weekly`, `custom`. |
| until string | string | ISO date of the last session, for a recurring one. |
| capacity integer | integer | Maximum participants. Change it later with set_group_capacity. |
{
"activity": "activity",
"team_member": "team member",
"start": "start"
} {
"activity": "Pilates mat class",
"team_member": "Instructor A",
"start": "2026-11-18T18:00",
"repeat": "weekly",
"until": "2027-01-27",
"capacity": 8,
"saved": true
} Lapsula manages availability from the capacity, and when a full session gets a free place it notifies clients on the waiting list. Raising the capacity can therefore send waiting-list notices, so the change waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP calllapsula_bookings_write → set_group_capacity
REST endpointPUT https://cotlet.dev/api/v1/lapsula-bookings/group-capacity
| Name | Type | Description |
|---|---|---|
| session string required | string | Group session name and start, as view_calendar returns it. |
| capacity integer required | integer | New maximum participants. |
| all_future boolean | boolean | Also change every later session of the series. |
{
"session": "session",
"capacity": 1
} {
"session": "Pilates mat class, 2026-11-18 18:00",
"capacity_before": 8,
"capacity_after": 10,
"all_future": true
} What every client sees: reminder channels, timing and text, and your public booking page.
Reminders are sent automatically to every client with an appointment. WhatsApp goes from your own number and client replies come back to you. Email reminders are on every plan; unlimited WhatsApp and SMS start on Starter. A change reaches all upcoming clients, so the agent shows it first. By default you confirm each call; you can switch that off for this tool.
MCP calllapsula_bookings_write → configure_reminders
REST endpointPOST https://cotlet.dev/api/v1/lapsula-bookings/reminders/configure
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `update`. `get` only reads. |
| channels array | array | Any of `whatsapp`, `sms`, `email`. |
| lead_time string | string | How long before the appointment, for example 24h. |
| message string | string | The reminder text. |
{
"action": "action"
} {
"channels": [
"whatsapp",
"email"
],
"lead_time": "24h",
"message": "Reminder: your appointment with Example Clinic is tomorrow at 10:00. Reply to this message if you need to change it.",
"saved": true
} Clients book there around the clock, from the page itself or the widget embedded on your site (WordPress, Wix or any platform). A change is public at once, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP calllapsula_bookings_write → customize_booking_page
REST endpointPOST https://cotlet.dev/api/v1/lapsula-bookings/booking-page/customize
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `update`. `get` only reads, including the one-line embed code. |
| logo_url string | string | Logo, as a link the Cloud Browser can download. |
| social_links array | array | Your social media links. |
| domain string | string | Custom domain (Pro plan) or Lapsula subdomain. |
{
"action": "action"
} {
"page": "exampleclinic.lapsula.com",
"logo": "logo.png",
"social_links": 2,
"embed": "<script src=\"...\"></script>",
"saved": true
} Your signed-in Lapsula browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 6 Lapsula tools. The session cookie stays in the Cloud Browser.
The calendars and settings your Lapsula user can open, and nothing more.
Medical history, consents, AI transcriptions and session notes, invoices and payments, users and your plan.
You sign in again yourself, in the same Cloud Browser.
Disable Lapsula for agents, reset the browser, or change your Lapsula password.
Cotlet never sees or stores your password: you sign in to Lapsula yourself, by email, Google or Apple, and the agent only uses the session that sign-in leaves behind. No tool opens clinical notes or medical history. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
| Action | How to put it right |
|---|---|
| Appointment booked by mistake | Call it off in Lapsula; the client may already have a reminder |
| Group session series | Edit or remove the series in Lapsula |
| Capacity | Call set_group_capacity again; waiting-list notices already sent stay sent |
| Reminder settings or booking page | Call the tool again with the earlier values |
All 5 write tools ask first: by default you confirm each call, and you can switch that off per tool. view_calendar only reads and runs at once.
{
"name": "schedule_appointment",
"arguments": {
"customer": "Example Client",
"phone": "+34 600 000 000",
"activity": "Back massage",
"team_member": "Therapist A",
"start": "2026-11-17T10:00"
}
} curl -X POST https://cotlet.dev/api/v1/lapsula-bookings/appointment/schedule \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"customer":"Example Client","phone":"+34 600 000 000","activity":"Back massage","team_member":"Therapist A","start":"2026-11-17T10:00"}' {
"booking": "Back massage",
"customer": "Example Client",
"team_member": "Therapist A",
"start": "2026-11-17T10:00",
"end": "2026-11-17T11:00",
"status": "APPROVED"
} The example books a one-hour massage from the back office, so Lapsula saves it APPROVED. A cron job or n8n flow can make the same call over REST at /api/v1/lapsula-bookings with the same key and price, in JSON. Failed calls are free.
About $18 a monthfor a two-therapist practice with one weekly class, 3,180 credits. Your Lapsula plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning day plan per therapist | 1 × 30 | 300 |
| Bookings for callers, calendar check first | 2 × 60 | 1,200 |
| Group sessions and capacity changes | 2 × 8 | 160 |
| Reminder and booking page updates | 1 × 2 | 20 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 168 calls | 3,180 |
The smallest pack, 5,000 credits for $29, covers this month. More therapists and bookings use more calls.
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, 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 |
|---|---|---|
| Lapsula API | Listed on the Enterprise plan. | By contact; scope not published. |
| Zapier API | New bookings, status changes and reschedules sent to a Zap. | Events only: it cannot book or change anything in Lapsula. |
| Google Calendar sync | Two-way sync that blocks busy times. | Calendar time only, not bookings, classes or reminders. |
| By hand | Every screen, signed in as you. | One booking at a time, while the phone rings. |
If you only need to know when a booking arrives, the Zapier API does that. Cotlet fits when you want ChatGPT, Claude or a script to book, schedule classes and change reminders in Lapsula from your own login, with nothing to host.
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Lapsula tools.
Sign up free at https://cotlet.dev/signup?app=lapsula-bookings, turn on Lapsula under Integrations in the console and sign in at https://app.lapsula.com/login in your Cloud Browser. Then connect your AI agent and ask it for today's calendar. The trial needs no card.
Lapsula offers API access only on its Enterprise plan, by contact (pricing page, checked 15 Nov 2026). Its public Zapier API sends booking events (new bookings, status changes, reschedules) and cannot create or change bookings. There is no Lapsula MCP server and no official ChatGPT or Claude connector. Cotlet does not need either: it works in your own signed-in Lapsula account.
No. The tools cover scheduling, reminders and the booking page only. No tool opens medical history, consents, AI transcriptions or session notes.
Yes. The tools work with whatever your plan has: on Hobby that is one calendar and email reminders; WhatsApp and SMS reminders need Starter or above.
Only in how it is called. Both carry the same 6 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Lapsula or Lapsula, SL.
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