realtycalendar-web-mcp
Related Servers
Alternatives to realtycalendar-web-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to search for available desk space, submit room reservations, and let admins approve or reject booking requests through a scoped MCP API.-
- 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 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.Elastic 2.0
- AlicenseAqualityBmaintenanceBook a table, an appointment or a place in a class at a real local business. Live availability, instant confirmation, no account and no API key. Eight tools: search, fetch, get_business, check_availability, create_booking, check_booking, cancel_booking and request_listing. Guest emails in eight languages. Hosted at https://g-guest.app/api/mcp810 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceEnables managing restaurant table bookings through natural language conversations with an AI assistant, with built-in safety measures like no deletion and explicit write enable.MIT
TDQS
Scored across 4 tools
Each tool targets a distinct object and action: availability/pricing by date, room-category inventory, booking search by period, and single booking by id. The descriptions explicitly fence off the tempting confusions (check_availability vs list_bookings for 'is room X free', list_rooms vs check_availability for availability/prices), so an agent can select correctly.
All four tools follow a strict snake_case verb_noun pattern (check_availability, list_rooms, list_bookings, get_booking). List vs get vs check is used in the conventional, predictable way.
Four tools is lean but each covers a genuinely separate query axis, and there is no redundancy. It sits at the thin edge for a hotel/booking domain, where one might expect at least a write or payment operation.
Read coverage is solid (availability, inventory, booking search, booking detail), but the surface is read-only: no create/update/cancel booking or payment recording. get_booking even references 'a write' and a 'preview' that do not exist as tools here, which is a dead end for an agent trying to follow that instruction.