Online Booking System MCP Tools
Online Booking System MCP tools follow a booking operations workflow across services, locations, staff, rooms and equipment, slots, blackout rules, customers, bookings, deposits and payments, reschedule and cancellation policies, package session deduction, reminders, waitlists, attendance and no-shows, capacity analytics, and audit logs.
Read booking timezone, slot interval, booking window, payment, reminder, reschedule, and cancellation defaults.
Governance
Read-only; baseline context before booking writes.
Safety
Do not expose payment secrets, API keys, or private notes.
booking.services.list
readList bookable services, categories, duration, base price, capacity, deposit, and package deduction rules.
Read first
booking.config.get
Governance
Read-only; used before releasing slots or creating bookings.
Safety
Show only active or authorized services; avoid exposing internal drafts.
Read one service's duration, buffers, eligible resources, pricing, deposit, cancellation, and reschedule constraints.
Read first
booking.services.list
Governance
Read-only; required before service edits or booking creation.
Safety
Do not expose unauthorized cost, commission, or margin fields.
booking.locations.list
readList branches, service locations, opening hours, addresses, timezone, and available services.
Read first
booking.config.get
Governance
Read-only; used for location-based availability searches.
Safety
Hide internal warehouses, staff-only locations, or unpublished addresses.
booking.resources.list
readList staff, rooms, equipment, capacity, and compatible services to prevent conflicts.
Read first
booking.services.list, booking.locations.list
Governance
Read-only; used before slot release and assignment.
Safety
Mask staff personal data and internal resource costs by permission.
booking.staff_schedules.list
readRead staff rosters, leave, service eligibility, daily limits, and assigned bookings.
Read first
booking.resources.list
Governance
Read-only; used for slot release, reschedule, and staffing decisions.
Safety
Return work availability only; do not expose pay or private calendar details.
booking.blackout_rules.list
readRead holidays, maintenance, internal events, temporary blocks, and minimum notice rules.
Read first
booking.config.get, booking.locations.list
Governance
Read-only; must be applied before availability search or slot release.
Safety
Show only necessary reason labels; avoid sensitive internal details.
booking.availability.search
readSearch available slots by service, location, staff, date, capacity, and pricing rules.
Read first
booking.service.get, booking.staff_schedules.list, booking.blackout_rules.list
Governance
Read-only; used before self-service or staff-assisted booking.
Safety
Do not show other customer names; return capacity and availability state only.
Read a slot's service, resources, capacity, booked count, waitlist, pricing, and payment requirements.
Read first
booking.availability.search
Governance
Read-only; verify before booking, reschedule, block, or release.
Safety
Do not return full customer lists unless staff permission allows it.
booking.bookings.list
readList bookings by date, service, staff, location, status, payment status, or customer.
Read first
booking.config.get
Governance
Read-only; used before operations, reminders, reschedule, and no-show handling.
Safety
Mask customer PII by role; avoid bulk export.
Read one booking's customer, service, slot, resources, payment, reminders, reschedule, and audit history.
Read first
booking.bookings.list
Governance
Read-only; required before cancel, reschedule, refund, package deduction, or attendance updates.
Safety
Show contact details and notes only to authorized staff.
booking.customers.search
readSearch booking customers by phone, email, name, or member number.
Read first
booking.config.get
Governance
Read-only; used before staff-assisted booking or history lookup.
Safety
Limit results and mask partial phone and email values.
Read customer booking history, preferences, no-show records, consent state, and package balance summary.
Read first
booking.customers.search
Governance
Read-only; verify before booking, reminders, or package deduction.
Safety
Protect medical, minor, or sensitive notes with extra permissions.
booking.packages.list
readList customer packages, remaining sessions, expiry, eligible services, and deduction limits.
Read first
booking.customer.get, booking.service.get
Governance
Read-only; used before package deduction, booking confirmation, or refund.
Safety
Do not expose payment amounts or contract terms to unauthorized roles.
booking.payment_settings.get
readRead Stripe, PayMe, FPS, deposit ratio, refund window, and payment deadline rules.
Read first
booking.config.get
Governance
Read-only; used before payment capture, deposit refund, and booking confirmation.
Safety
Never return secret keys, full card data, or sensitive bank details.
booking.payments.list
readList booking payments, deposits, balances, refunds, payment proofs, and gateway states.
Read first
booking.booking.get, booking.payment_settings.get
Governance
Read-only; used before refund, payment follow-up, or payment confirmation.
Safety
Mask sensitive payment data beyond transaction references.
booking.reminder_rules.list
readRead confirmation, reschedule, cancellation, pre-service reminder, and no-show follow-up rules.
Read first
booking.config.get
Governance
Read-only; used before sending or updating reminders.
Safety
Do not expose WhatsApp tokens or provider secrets.
booking.reschedule_policy.get
readRead latest reschedule time, cancellation fee, refund, waitlist, and manual approval policies.
Read first
booking.service.get, booking.payment_settings.get
Governance
Read-only; required before reschedule, cancellation, and refund previews.
Safety
Policy exceptions must show source; do not infer penalty waivers.
booking.waitlist.list
readList waitlist entries, preferred slots, notification state, expiry, and ranking reasons.
Read first
booking.slot.get, booking.customer.get
Governance
Read-only; used before releasing capacity or offering a slot.
Safety
Waitlist ranking must be explainable without exposing other customers' PII.
booking.booking_summary.get
readRead booking volume, conversion, cancellation rate, no-shows, revenue, deposits, and refunds.
Read first
booking.bookings.list, booking.payments.list
Governance
Read-only; used for operations reports and improvement suggestions.
Safety
Aggregate reporting; avoid single-customer sensitive data.
booking.capacity_summary.get
readRead peak slots, capacity utilization, staff utilization, room/equipment load, and waiting demand.
Read first
booking.availability.search, booking.bookings.list
Governance
Read-only; used for next-month slot release and staffing.
Safety
Avoid public individual staff performance comparisons.
booking.audit_logs.list
readList audit logs for bookings, payments, refunds, reschedules, cancellations, package deductions, and reminders.
Read first
booking.booking.get
Governance
Read-only; used for disputes, errors, and approval history.
Safety
Audit logs are restricted to authorized administrators.
booking.slot_release.preview
previewPreview next-month slot release impact on staff, rooms, capacity, pricing, and conflicts.
Read first
booking.services.list, booking.resources.list, booking.staff_schedules.list, booking.blackout_rules.list, booking.capacity_summary.get
Governance
Preview required; slots can open only after approval.
Safety
Do not override blackouts, staff leave, or capacity limits automatically.
booking.create_booking.preview
previewPreview whether a booking would conflict, require deposit, deduct package sessions, waitlist, or trigger reminders.
Read first
booking.slot.get, booking.customer.get, booking.payment_settings.get, booking.packages.list
Governance
Preview must be confirmed before staff-assisted or AI-created bookings.
Safety
Do not bypass customer consent, deposit requirements, or blocklist constraints.
booking.reschedule.preview
previewPreview old-slot release, new-slot availability, fees, reminders, and waitlist impact for rescheduling.
Read first
booking.booking.get, booking.reschedule_policy.get, booking.availability.search
Governance
Customer or staff approval required before reschedule.
Safety
Do not reschedule outside policy; late changes need manual approval.
booking.cancellation.preview
previewPreview refund, deposit forfeiture, slot release, waitlist notification, and reminder cancellation.
Read first
booking.booking.get, booking.reschedule_policy.get, booking.payments.list, booking.waitlist.list
Governance
Cancellation and refund require policy compliance or admin approval.
Safety
Do not waive cancellation fees or refund limits without authorization.
booking.deposit_refund.preview
previewPreview deposit or payment refund amount, gateway state, fees, refund window, and accounting impact.
Read first
booking.booking.get, booking.payment_settings.get, booking.payments.list
Governance
Refunds require approval by an authorized role.
Safety
Prevent duplicate refunds; verify gateway transaction state.
booking.package_deduction.preview
previewPreview package session deduction, expiry, and balance changes after confirmation or attendance.
Read first
booking.booking.get, booking.packages.list
Governance
Confirm eligible service, sufficient balance, and customer identity before deduction.
Safety
Avoid duplicate deductions; idempotency key required.
booking.reminders.preview
previewPreview confirmation, reschedule, cancellation, pre-service, and waitlist reminder content, channels, and recipients.
Read first
booking.booking.get, booking.reminder_rules.list, booking.customer.get
Governance
Confirm content and recipients before bulk or customized sends.
Safety
Respect consent, opt-out, and message template limits.
booking.service.upsert
writeCreate or update service name, duration, capacity, pricing, deposit, resource requirements, and booking rules.
Read first
booking.service.get, booking.payment_settings.get
Governance
Public service or price changes require approval before publishing.
Safety
Keep version history; do not alter existing booking prices unless explicitly requested.
booking.resource_availability.upsert
writeCreate or update availability, capacity, service compatibility, and block rules for staff, rooms, or equipment.
Read first
booking.resources.list, booking.staff_schedules.list, booking.blackout_rules.list
Governance
Approval required when public availability or existing bookings are affected.
Safety
Do not remove booked resources without conflict warnings.
booking.slot_batch.open
writeBulk-open bookable slots for a date range with staff, room, capacity, and pricing rules.
Read first
booking.slot_release.preview
Governance
Must execute from an approved preview.
Safety
Requires idempotency; avoid duplicate release or blackout overrides.
Block slots for breaks, maintenance, internal events, or temporary unavailability.
Read first
booking.slot.get, booking.bookings.list
Governance
If bookings exist, handle notification, reschedule, or refund approval first.
Safety
Never silently cancel customer bookings.
booking.booking.create
writeCreate a customer booking and reserve slot, service, resources, deposit requirement, and notification tasks.
Read first
booking.create_booking.preview
Governance
Requires customer confirmation or authorized staff confirmation.
Safety
Check capacity, consent, payment requirements, and idempotency.
booking.booking.confirm
writeConfirm a tentative or payment-pending booking and update payment, deposit, package, and reminder state.
Read first
booking.booking.get, booking.payments.list, booking.package_deduction.preview
Governance
Verify payment or package deduction before confirmation.
Safety
Prevent unpaid bookings from being confirmed incorrectly.
booking.booking.reschedule
writeMove a booking to a new slot, release old slot, and update resources, fees, reminders, and audit.
Read first
booking.reschedule.preview
Governance
Requires customer or authorized staff approval; late reschedule needs admin approval.
Safety
Do not release the old slot before confirming the new slot is available.
booking.booking.cancel
writeCancel a booking and handle refund, deposit forfeiture, slot release, waitlist, and notifications.
Read first
booking.cancellation.preview
Governance
Execute after policy-based or admin approval.
Safety
Cancellation reason, actor, and refund decision must be audited.
booking.booking.check_in
writeMark customer arrival and trigger package deduction, balance handling, or service completion workflow.
Read first
booking.booking.get, booking.package_deduction.preview
Governance
Frontline staff may execute by permission; deductions must be traceable.
Safety
Prevent duplicate check-ins or package deductions.
booking.booking.mark_no_show
writeMark no-show and update customer record, deposit handling, waitlist release, and follow-up notification.
Read first
booking.booking.get, booking.reschedule_policy.get, booking.payments.list
Governance
Admin approval required if fees or customer restrictions are applied.
Safety
Keep staff and timestamp records to avoid false no-show marking.
booking.deposit.capture
writeCapture or confirm deposit, full payment, or payment proof and update booking payment state.
Read first
booking.booking.get, booking.payment_settings.get, booking.payments.list
Governance
Offline payment confirmation requires authorized staff; online capture requires gateway verification.
Safety
Never store full card data; prevent duplicate charges.
booking.refund.create
writeCreate an approved refund and update payment, booking, and accounting records.
Read first
booking.deposit_refund.preview
Governance
Authorized role must approve refund amount and reason.
Safety
Use idempotency and verify gateway refund state.
booking.package_session.deduct
writeDeduct package sessions for confirmed or attended bookings and record balance and source.
Read first
booking.package_deduction.preview
Governance
Execute by service and package rules; exceptions require approval.
Safety
Must prevent duplicate deduction for the same booking.
booking.waitlist.offer_slot
writeOffer a released slot to a waitlisted customer, set acceptance deadline, and temporarily hold capacity.
Read first
booking.waitlist.list, booking.slot.get, booking.reminders.preview
Governance
Send based on waitlist ranking or staff approval.
Safety
Do not permanently hold the same capacity for too many customers.
booking.staff.assign
writeAssign or change booking staff while checking eligibility, roster, and conflicts.
Read first
booking.booking.get, booking.staff_schedules.list, booking.slot.get
Governance
Changing staff on confirmed bookings requires permission or admin approval.
Safety
Do not assign ineligible, off-duty, or overloaded staff.
booking.reminder.send
writeSend confirmation, payment, reschedule, cancellation, pre-service, waitlist, or no-show follow-up messages.
Read first
booking.reminders.preview
Governance
Automated reminders follow rules; manual or bulk sends require confirmation.
Safety
Respect consent, opt-out, frequency caps, and template approval.
booking.reminder_rule.upsert
writeCreate or update reminder rules, channels, send timing, templates, and eligible services.
Read first
booking.reminder_rules.list, booking.reminders.preview
Governance
Rules affecting many customer notifications require admin approval.
Safety
Prevent rapid duplicate sends or template policy violations.
booking.analytics_snapshot.record
writeRecord operational snapshots for bookings, capacity, revenue, cancellations, no-shows, and channel performance.
Read first
booking.booking_summary.get, booking.capacity_summary.get
Governance
Writes aggregate reporting data only; does not modify customers or bookings.
Safety
Avoid writing personal data into analytics snapshots.
booking.action_request.status
statusCheck write request, approval, execution, failure, retry, and audit status for booking actions.
Read first
booking.audit_logs.list
Governance
Read-only status; tracks slot release, refund, reschedule, and notification actions.
Safety
Status endpoint must not re-execute writes.