Restaurant Reservation MCP Server
Related Servers
Alternatives to Restaurant Reservation MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceManage Resy reservations via natural language: search restaurants, book tables, and manage reservations, favorites, and Priority Notify.15404 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to search restaurants, check availability, and book reservations on OpenTable, including managing booking history and handling multi-factor authentication.948 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to search restaurants, check availability, and book reservations on OpenTable, with persistent sessions and MFA handling.948 npm1MIT
- AlicenseAqualityDmaintenanceEnables restaurant discovery and reservations across multiple providers (Resy, Google Places, Yelp, Tock) with auditable and secure two-step booking.10MIT
- AlicenseAqualityAmaintenanceManage OpenTable reservations via natural language — find slots, book, cancel, manage favorites, and read your dashboard using your own browser session.14356 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents and clients to check table availability and book restaurant reservations for a given date, time, and party size, returning either a confirmed booking or the nearest alternative slots. It also supports idempotent retries so replayed requests return the original reservation rather than double-booking a table.-
TDQS
Scored across 12 tools
Most tools have distinct purposes, but there is notable overlap between 'cancel_reservation' and 'cancel_snipe', and between 'set_credentials' and 'set_login', which could confuse an agent about which to use for authentication tasks. The descriptions clarify the differences, but the boundaries are not immediately obvious from the names alone.
The tool names follow a consistent snake_case pattern throughout, which aids readability. However, there is some inconsistency in verb usage, such as 'make_reservation' versus 'snipe_reservation', and 'check_auth_status' versus 'refresh_token', which slightly detracts from predictability.
With 12 tools, the count is well-scoped for a restaurant reservation server, covering authentication, search, booking, management, and automation features. Each tool appears to serve a specific and necessary function within the domain, without feeling excessive or insufficient.
The tool set provides comprehensive coverage for the restaurant reservation domain, including search, availability checks, booking, cancellation, and automation features like sniping. A minor gap is the lack of a tool to modify existing reservations, which could be a useful addition for full lifecycle management.