bookings-mcp
Related Servers
Alternatives to bookings-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to work within a user's signed-in business account to read and change bookings and client lists, including booking, rescheduling, finding open slots, and following up with clients.7Elastic 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to safely manage appointment bookings for appointment-based businesses over MCP, including searching availability, holding, confirming, rescheduling, and canceling bookings, and reading business policies.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage appointments, reschedule bookings, look up clients, and add client notes in a user's signed-in business account without requiring an API key.7Elastic 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to discover availability, place expiring holds, and confirm or cancel appointments for connected booking businesses, with idempotent retries and explicit user consent.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to check real availability, retrieve service prices and cancellation terms, and book, reschedule, or cancel appointments with connected HVAC and plumbing businesses.MIT
- AlicenseNot gradedqualityCmaintenanceScheduling and booking engine for AI agents. Check availability, hold slots, and confirm appointments with two-phase booking and conflict-free resource management.2Apache 2.0
TDQS
Scored across 6 tools
Each tool maps to a distinct step of the booking workflow: catalog (list_services), availability (find_slots), booking creation, and per-phone booking lookup/modification. The descriptions explicitly disambiguate the closest pair (find_slots = free times vs find_bookings = existing bookings) and enforce call ordering, leaving no realistic misselection.
All names are snake_case verb_noun and read predictably. The only minor deviation is mixing 'list_' and 'find_' for read operations (list_services vs find_slots/find_bookings), which is slightly inconsistent but still clear.
Six tools is well-scoped for a customer-facing appointment booking server, and each one earns its place in the flow. Nothing feels redundant or missing at the tool-count level.
The full customer lifecycle is covered: browse services, check availability, book, look up, reschedule, and cancel, including the 24-hour escalation rule. Minor gaps remain — no retrieval of a single booking's details or booking identifier, and find_bookings only returns upcoming appointments, so past or specific-booking lookups are dead ends.