Bookibles API and MCP server Let your AI agent answer every booking request.

Bookibles publishes no API and no MCP server (checked 15 Nov 2026). Cotlet runs a hosted Bookibles MCP server with 12 tools that ChatGPT and Claude use in your own business workspace. Confirmations, reschedules and customer messages wait for your OK.

  • Free 7-day trial, no card
  • Unofficial, not affiliated with Bookibles
Bookibles logo Bookibles Cloud Browser

12 tools Read and write

Appointment admin

What can your AI agent do in Bookibles? The front desk work between appointments.

  • Confirm or decline pending requests

  • Mark the day completed or no-show

  • Reschedule a booking

  • Message a signed-in customer

  • Add closures and short days

  • Review last month's completed bookings

No API, no MCP

Does Bookibles have an MCP server or an API? The official Bookibles routes, checked 15 November 2026.

Bookibles publishes no public API: there are no developer docs, API keys or API plan on its features, pricing and help pages. No Bookibles MCP server and no official ChatGPT or Claude connector was found. Its one documented integration is Google Calendar sync on Pro and above.

  • Google Calendar sync writes dated bookings to a separate calendar and imports busy times every five minutes. Edits in Google do not update Bookibles.
  • Free has 2 services and 50 bookings a month. Pro is $14 a month with 10 services; Max is $25 a month with unlimited services.
  • Service payments and deposits are handled outside Bookibles.
Bookibles Google Calendar sync, working by hand and Cotlet compared
What you need Google Calendar syncBy handCotlet
Ask ChatGPT or Claude about your bookings Dated bookings only, copied out Copy and paste Hosted MCP server
Confirm, cancel or reschedule Google edits do not reach Bookibles One booking at a time 12 tools, writes after your OK
Services, hours and closures Busy times block fixed slots In the dashboard After your OK
Run from n8n or a script Nothing to call Manual only REST, same key

Checked 15 Nov 2026. Sources: Bookibles pricing · Google Calendar sync for online booking · Booking analytics · Bookibles Help Center · Help: Connect Google Calendar · Help: Add a bookable service · Help: Set your weekly business schedule · Help: Choose fixed slots or flexible booking · Help: Manage booking statuses · Help: Message a customer about a booking

Set up once

How does the Bookibles MCP server work? The Bookibles MCP server by Cotlet: your agent works in your own business workspace.

  1. 1Sign in to Bookibles

    Once, in a browser we host for you.

  2. 2Connect your AI agent

    One address in its settings.

  3. 3Hand it the requests

    Check each one, then approve the confirmation.

Your agent works in your own signed-in Cloud Browser. Booking changes and customer messages wait for your OK. Who can see your session

Any MCP client

How to connect Bookibles to your AI agent

  1. 1

    Sign in to Bookibles in a Cloud Browser. Open bookibles.com/login in your Cotlet Cloud Browser and sign in with your email and password, or with Google.

  2. 2

    Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.

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

Bookibles sits on the shared address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned Bookibles on after connecting? Refresh the connector and the 12 Bookibles tools appear.

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: bookibles_read
6 read, 6 write

All 12 Bookibles MCP tools

One tool per owner workflow in the Bookibles Help Center, plus the analytics page. Reads run at once; every write asks first.

Bookings4

Pending requests, confirmed appointments and the final states: cancelled, completed and no-show. Only scheduled bookings can be moved.

  • list_bookings List bookings in the business workspace by status and date. read

    Returns each booking with service, customer, date or time where the booking type has one, status, and whether it is a linked customer, guest or manual booking. Flexible requests have no slot. Read only.

    MCP callbookibles_read → list_bookings

    REST endpointGET https://cotlet.dev/api/v1/bookibles/bookings

    Parameters

    Parameters: list_bookings
    NameTypeDescription
    status string string One of `pending`, `confirmed`, `cancelled`, `completed`, `no_show`. Leave empty for all.
    from string string ISO date to start from. Defaults to today.
    to string string ISO date to end on.

    Example response

    {
      "bookings": [
        {
          "id": "bk_1042",
          "service": "Signature facial",
          "customer": "Example Customer A",
          "start": "2026-11-18T10:00",
          "status": "pending",
          "kind": "linked"
        },
        {
          "id": "bk_1043",
          "service": "Gel manicure",
          "customer": "Example Customer B",
          "start": "2026-11-18T14:30",
          "status": "confirmed",
          "kind": "guest"
        }
      ]
    }
  • get_booking Read one booking: service, customer, time, status, timeline and the actions it allows now. read

    The actions depend on the status and your role: a pending booking can be confirmed or declined, a confirmed one cancelled, completed or marked no-show, and only scheduled bookings can be rescheduled. Read only.

    MCP callbookibles_read → get_booking

    REST endpointGET https://cotlet.dev/api/v1/bookibles/booking

    Parameters

    Parameters: get_booking
    NameTypeDescription
    booking string required string Booking ID, as list_bookings returns it.

    Example input

    {
      "booking": "booking"
    }

    Example response

    {
      "id": "bk_1042",
      "service": "Signature facial",
      "customer": "Example Customer A",
      "start": "2026-11-18T10:00",
      "status": "pending",
      "timeline": [
        {
          "at": "2026-11-15T09:12",
          "event": "Requested"
        }
      ],
      "actions": [
        "confirm",
        "decline",
        "reschedule"
      ]
    }
  • update_booking_status Confirm or decline a pending request, or cancel, complete or mark a confirmed booking no-show. writeAsks first

    Cancelled, completed and no-show are final states. Declining a request records it as cancelled. Cancelling frees the slot, but another rule or booking can still keep the time unavailable. By default you confirm each call; you can switch that off for this tool.

    MCP callbookibles_write → update_booking_status

    REST endpointPATCH https://cotlet.dev/api/v1/bookibles/booking-status

    Parameters

    Parameters: update_booking_status
    NameTypeDescription
    booking string required string Booking ID, as list_bookings returns it.
    status string required string One of `confirm`, `decline`, `cancel`, `complete`, `no_show`.
    reason string string Optional reason for `decline` and `cancel`.

    Example input

    {
      "booking": "booking",
      "status": "status"
    }

    Example response

    {
      "id": "bk_1042",
      "status": "confirmed"
    }
  • reschedule_booking Move a pending or confirmed scheduled booking to a new date or start time. writeAsks first

    The current slot stays reserved unless the new time passes Bookibles' availability and capacity checks. Flexible requests have no slot and cannot be rescheduled this way. By default you confirm each call; you can switch that off for this tool.

    MCP callbookibles_write → reschedule_booking

    REST endpointPOST https://cotlet.dev/api/v1/bookibles/booking/reschedule

    Parameters

    Parameters: reschedule_booking
    NameTypeDescription
    booking string required string Booking ID, as list_bookings returns it.
    new_date string string ISO date.
    new_start string string New start time, HH:MM, as the booking type asks.

    Example input

    {
      "booking": "bk_1043",
      "new_date": "2026-11-19",
      "new_start": "11:00"
    }

    Example response

    {
      "id": "bk_1043",
      "was": "2026-11-18T14:30",
      "now": "2026-11-19T11:00",
      "status": "Booking rescheduled"
    }

Services and booking rules3

Duration, price, booking type, auto-accept and bookings per slot. Your plan sets how many services you can have.

  • list_services List your bookable services with duration, price, booking type and capacity. read

    Returns each service as the service editor holds it: name, category, displayed duration in minutes and price, booking type, auto-accept and the limit per slot. Read only.

    MCP callbookibles_read → list_services

    REST endpointGET https://cotlet.dev/api/v1/bookibles/services

    Parameters

    No parameters.

    Example response

    {
      "services": [
        {
          "name": "Signature facial",
          "duration_min": 60,
          "price": 95,
          "currency": "USD",
          "booking_type": "date_and_time",
          "auto_accept": false,
          "per_slot": 1
        },
        {
          "name": "Gel manicure",
          "duration_min": 45,
          "price": 55,
          "currency": "USD",
          "booking_type": "date_and_time",
          "auto_accept": true,
          "per_slot": 1
        }
      ]
    }
  • create_service Add a service with name, description, duration, price, booking type and capacity. writeAsks first

    A new service becomes bookable on your public page when your plan allows it: Free has 2 services, Pro 10, Max unlimited. The agent shows you the settings first. By default you confirm each call; you can switch that off for this tool.

    MCP callbookibles_write → create_service

    REST endpointPOST https://cotlet.dev/api/v1/bookibles/services

    Parameters

    Parameters: create_service
    NameTypeDescription
    name string required string Service name.
    description string required string What is included, who it is for, preparation and how to reach you.
    category string string A service label.
    duration_min number number Duration in minutes, when Display duration is on.
    price number number A fixed price in the chosen currency, when Display pricing is on. Not a starting price or deposit.
    booking_type string required string One of `date_and_time`, `date_only`, `time_only`, `flexible_request`.
    auto_accept boolean boolean True starts bookings confirmed; false makes each one a pending request.
    per_slot number number Limit bookings per slot.

    Example input

    {
      "name": "Jane Doe",
      "description": "description",
      "booking_type": "booking type"
    }

    Example response

    {
      "service": "Brow shape and tint",
      "duration_min": 30,
      "price": 40,
      "booking_type": "date_and_time",
      "auto_accept": false,
      "active": true
    }
  • set_booking_rules Change a service's booking type, auto-accept or bookings per slot. writeAsks first

    Bookibles suggests flexible requests when duration varies a lot from customer to customer. The limit per slot applies to one service only, so two services sharing one person can still take the same time. By default you confirm each call; you can switch that off for this tool.

    MCP callbookibles_write → set_booking_rules

    REST endpointPUT https://cotlet.dev/api/v1/bookibles/booking-rules

    Parameters

    Parameters: set_booking_rules
    NameTypeDescription
    service string required string Service name, as list_services returns it.
    booking_type string string One of `date_and_time`, `date_only`, `time_only`, `flexible_request`.
    auto_accept boolean boolean Turn off when each request must start pending.
    per_slot number number Limit bookings per slot.

    Example input

    {
      "service": "service"
    }

    Example response

    {
      "service": "Signature facial",
      "booking_type": "flexible_request",
      "auto_accept": false,
      "saved": true
    }

Availability2

The recurring week, breaks and dated closures, in the business time zone.

  • get_availability Read the business time zone, the recurring week, breaks and dated closures. read

    Availability is shown in the business time zone set on the Public page, not the browser's. Services use this schedule unless they have a Custom schedule. Read only.

    MCP callbookibles_read → get_availability

    REST endpointGET https://cotlet.dev/api/v1/bookibles/availability

    Parameters

    No parameters.

    Example response

    {
      "time_zone": "America/New_York",
      "week": [
        {
          "day": "Monday",
          "open": "09:00",
          "close": "17:00"
        },
        {
          "day": "Sunday",
          "closed": true
        }
      ],
      "breaks": [
        {
          "day": "Monday",
          "label": "Lunch",
          "starts": "12:00",
          "ends": "13:00"
        }
      ],
      "closures": [
        {
          "date": "2026-11-26",
          "label": "Thanksgiving",
          "closed": true
        }
      ]
    }
  • edit_availability Change opening hours per day, recurring breaks, or closures and custom hours on a date. writeAsks first

    Times are in the business time zone. A break blocks every service; a closure takes the whole day off. Customers see the new slots on your booking page as soon as it saves. By default you confirm each call; you can switch that off for this tool.

    MCP callbookibles_write → edit_availability

    REST endpointPATCH https://cotlet.dev/api/v1/bookibles/availability

    Parameters

    Parameters: edit_availability
    NameTypeDescription
    week array array Days with open and close times, or closed.
    breaks array array Recurring breaks: day, label, starts, ends.
    dates array array Closures and custom dates: date, label, closed, or opens and closes.

    Example response

    {
      "saved": true,
      "closures": [
        {
          "date": "2026-12-24",
          "label": "Christmas Eve",
          "opens": "09:00",
          "closes": "13:00"
        }
      ]
    }

Messages and analytics3

Conversations with signed-in customers, and the Pro analytics of completed bookings.

  • read_conversation Read the Messages conversation with a signed-in customer. read

    Only bookings by signed-in customers have a conversation; guest and manual bookings do not. One conversation can cover several appointments. Read only.

    MCP callbookibles_read → read_conversation

    REST endpointGET https://cotlet.dev/api/v1/bookibles/conversations/read

    Parameters

    Parameters: read_conversation
    NameTypeDescription
    customer string required string Customer name, from a linked booking.

    Example input

    {
      "customer": "customer"
    }

    Example response

    {
      "customer": "Example Customer A",
      "messages": [
        {
          "from": "customer",
          "at": "2026-11-15T09:15",
          "text": "Is there parking near the studio?"
        }
      ],
      "read_only": false
    }
  • message_customer Send a message to a signed-in customer about their booking. writeAsks first

    Works only for bookings by an eligible signed-in customer; guest and manual bookings have no conversation, so use the contact details on the booking instead. The agent never puts passwords, card data or health information in a message. By default you confirm each call; you can switch that off for this tool.

    MCP callbookibles_write → message_customer

    REST endpointPOST https://cotlet.dev/api/v1/bookibles/customer/message

    Parameters

    Parameters: message_customer
    NameTypeDescription
    booking string required string Booking ID, as list_bookings returns it.
    text string required string The message. Name the service and the date or time it is about.

    Example input

    {
      "booking": "booking",
      "text": "text"
    }

    Example response

    {
      "booking": "bk_1042",
      "customer": "Example Customer A",
      "sent": true
    }
  • get_booking_analytics Read completed bookings, completion rate, repeat-booking share, lead time and completed booking value. read

    Analytics is on Bookibles Pro and above; Free shows an upgrade view. Completed booking value comes from the prices captured with each booking, so it is not money collected and not an accounting record. Read only.

    MCP callbookibles_read → get_booking_analytics

    REST endpointGET https://cotlet.dev/api/v1/bookibles/booking-analytics

    Parameters

    Parameters: get_booking_analytics
    NameTypeDescription
    from string required string ISO date the period starts.
    to string required string ISO date the period ends.

    Example input

    {
      "from": "from",
      "to": "to"
    }

    Example response

    {
      "period": "2026-10-01/2026-10-31",
      "completed": 96,
      "completion_rate": 0.89,
      "repeat_share": 0.41,
      "completed_booking_value": 6840,
      "currency": "USD"
    }
Encrypted, revocable

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

  • What we store

    Your signed-in Bookibles browser profile, AES-256-GCM encrypted, in Finland. Never your password.

  • What your agent gets

    The 12 Bookibles tools. The session cookie stays in the Cloud Browser.

  • What the session sees

    The bookings, services and messages your Bookibles role can manage in your business workspace.

  • What no tool touches

    Your plan and billing settings, the Google Calendar connection, team members and your public business profile.

  • If Bookibles signs you out

    You sign in again yourself, in the same Cloud Browser.

  • How to cut access

    Disable Bookibles for agents, reset the browser, or change your Bookibles password.

Cotlet never sees or stores your password. You type it yourself, or use Continue with Google, and the agent only uses the session that sign-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).

We keep it working

What happens when Bookibles changes? The tools work through the same dashboard screens you use.

Cotlet watches the apps it serves and updates the Bookibles server when the dashboard changes, so your agent keeps working without a change on your side.

The agent sees what your plan and role allow. On Free, analytics shows an upgrade view and a third service cannot be published; Pro and Max raise those limits.

If Bookibles signs you out, one click in the Cotlet console reopens the Cloud Browser so you can sign in again.

6 tools ask first

Approvals, undo and mistakes Customers hear nothing and slots move only when you say so.

  1. 01 Read the booking get_booking returns the time, status and allowed actions.
  2. 02 Check the hours get_availability shows breaks and closures on the new day.
  3. 03 Show you the move Old and new time, before anything is saved.
  4. 04 Save after your OK reschedule_booking moves it; the slot is kept until the new time passes.
Fixing a Bookibles change that went wrong
ActionHow to put it right
Service settings, booking rules, hours and closuresCall create_service, set_booking_rules or edit_availability again with the earlier values
RescheduleReschedule again to the old time, if it is still free
Cancel, decline, complete or no-showFinal in Bookibles: the customer books again
Message to a customerAlready with them: send a correction

All 6 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 6 read tools run at once.

MCP call
{
  "name": "reschedule_booking",
  "arguments": {
    "booking": "bk_1043",
    "new_date": "2026-11-19",
    "new_start": "11:00"
  }
}
REST
curl -X POST https://cotlet.dev/api/v1/bookibles/booking/reschedule \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"booking":"bk_1043","new_date":"2026-11-19","new_start":"11:00"}'
Response
{
  "id": "bk_1043",
  "was": "2026-11-18T14:30",
  "now": "2026-11-19T11:00",
  "status": "Booking rescheduled"
}

The example moves a gel manicure from Wednesday 14:30 to Thursday 11:00 and waits for Bookibles to say Booking rescheduled. A cron job or n8n flow can make the same call over REST at /api/v1/bookibles with the same key and price, in JSON. Failed calls are free.

Pay per call

How much does the Bookibles MCP server cost?

About $26 a monthfor a studio taking about 120 bookings a month, 4,550 credits. Your Bookibles plan stays as it is.

Illustrative month, our assumption: successful calls for this workload
JobCallsCredits
Morning list of pending requests2 × 26520
Confirm or decline a request1 × 60600
Evening close-out: completed or no-show1 × 1201,200
Reschedules with a customer message3 × 15450
Other customer messages1 × 20200
Hours, breaks and closures2 × 360
Monthly analytics review2 × 120
Cloud Browser, 30 days1,500
Total305 calls4,550

The smallest pack, 5,000 credits for $29, covers this month. A busier studio 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 Bookibles Free, Pro or Max plan applies as it is

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

Cotlet credit packs: price, credits and calls at 10 credits each
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.

Other options

Bookibles MCP server: other ways to connect What each route does for a booking business, and where it stops.

Other ways to work with Bookibles, checked 15 Nov 2026
OptionWhat it doesWhere it stops
Google Calendar sync (Pro and Max)Writes dated bookings to a "Bookibles" calendar and imports busy times every five minutes.Edits in Google do not change Bookibles; flexible requests are not written.
A calendar connector in your AI appLets the AI read the synced Google calendar.Sees only copied events; cannot confirm, cancel or reschedule a booking.
Bookibles analytics (Pro and Max)Completed bookings, completion rate, repeat share, lead time.Inside the dashboard, one period at a time.
By handOpen each booking in the dashboard.Only while you are at the desk, between clients.

If all you need is your bookings in a calendar, Google Calendar sync does it. Cotlet fits when you want ChatGPT, Claude or a script to act on bookings, services and hours in Bookibles itself, from your own login, with nothing to host.

EU company, since 2019

Who runs Cotlet A company you can look up.

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

Bookibles MCP server: questions

How do I get access?

Sign up free at https://cotlet.dev/signup?app=bookibles, turn on Bookibles under Integrations in the console and sign in at https://bookibles.com/login in your Cloud Browser. Then connect your AI agent and ask it about today's bookings. The trial needs no card.

Does Bookibles have an API?

Bookibles publishes no public API: bookibles.com/api and /developers show no developer docs, and its features, pricing and help pages name no API keys or API plan (checked 15 Nov 2026). No Bookibles MCP server and no official ChatGPT or Claude connector was found; its one documented integration is Google Calendar sync on Pro and above. Cotlet does not need one: it works in your own signed-in Bookibles account.

Can the agent message guest bookings?

No. Bookibles opens a conversation only with signed-in customers. Guest and manual bookings have no conversation, so the agent gives you the contact details on the booking instead.

Does the agent take payments or deposits?

No. Bookibles handles no service payments or deposits; they stay outside Bookibles, and no Cotlet tool touches billing. The completed booking value in analytics is a price snapshot, not money collected.

Which Bookibles user should I sign in with?

The owner, or a member whose role can manage services, availability and bookings. The agent can do only what that role can do.

Is the MCP server different from the REST API?

Only in how it is called. Both carry the same 12 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.

Is Cotlet affiliated with Bookibles?

No. Cotlet is independent and not affiliated with Bookibles.

Hand tomorrow's Bookibles requests to your agent.

Free 7-day trial with 2,000 credits, no card needed.