Advanced integration path
AI and Agent Integrations
This page is for technical teams that need agent-driven booking workflows. It is not the main product story for most buyers. Most businesses should still start with the booking link or widget first.
MCP Server
BookingAPI includes a Model Context Protocol server for MCP-compatible clients that need to inspect availability and manage bookings through a tool-based workflow.
- ✓
list_locations - ✓
list_services - ✓
get_availability - ✓
create_booking - ✓
cancel_booking - ✓
reschedule_booking
UCP Checkout Flow
BookingAPI also includes a UCP-oriented checkout session flow for clients that want a structured appointment-booking lifecycle over REST.
- ✓Discovery manifest
- ✓Create checkout session
- ✓Read checkout session
- ✓Update checkout session
- ✓Complete checkout session
- ✓Cancel checkout session
Verified Technical Notes
MCP implementation details
- Read and write tools are registered in the server.
- Inputs are validated before the request reaches the backend workflow.
- Authentication can require an API key or use public-mode tenant context depending on deployment configuration.
- The server instructions enforce a location-first workflow for bookings.
UCP implementation details
- A discovery manifest is exposed for tenant-specific UCP access.
- The checkout-session lifecycle supports create, read, update, complete, and cancel operations.
- UCP is a technical surface for compatible clients, not a requirement for normal booking use.
Use This Lane When The Workflow Is Truly Technical
If you only need customers to book online, start with the booking link or widget. If you need agent-driven workflows, use the docs and this integration path.