resy-mcp
Related Servers
Alternatives to resy-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityFmaintenanceEnables users to search, check availability, and book restaurant reservations across Resy and OpenTable platforms. It supports direct booking for Resy and includes an automated reservation 'sniper' for securing high-demand slots the moment they become available.124-
- AlicenseAqualityAmaintenanceManage OpenTable reservations via natural language — find slots, book, cancel, manage favorites, and read your dashboard using your own browser session.14356 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to search restaurants, check availability, and book reservations on OpenTable, including managing booking history and handling multi-factor authentication.948 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables restaurant reservation management through SevenRooms API, allowing users to create reservations and query available time slots with guest details and party size information.-
- AlicenseAqualityDmaintenanceEnables AI agents to search restaurants, check availability, and book reservations on OpenTable, with persistent sessions and MFA handling.948 npm1MIT
- 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 15 tools
Each tool targets a distinct resource-action pair: reservations, profile, payment methods, venue search, slots, booking, cancellation, favorites, and notify. The only related pair is search_venues vs find_slots, but the former is venue discovery and the latter is slot-level lookup at a specific venue, so an agent can select correctly.
All tools share a clear resy_ prefix and snake_case, with a dominant verb_noun pattern (list_reservations, add_favorite, remove_notify). Minor deviations are resy_book and resy_cancel without an explicit object, plus resy_healthcheck as a non-verb_noun name, but these are still predictable and readable.
15 tools sits at the upper edge of a well-scoped server but every tool maps to a distinct, useful Resy workflow: reservation lifecycle, venue discovery, favorites, notify, payment methods, profile, and diagnostics. No tool feels redundant or filler.
The surface covers booking, listing, and cancelling reservations; venue search and detail lookup; favorite list/add/remove; notify subscribe/unsubscribe; and the necessary context of payment methods and profile. Favorites and notify have full lifecycle coverage, and reservations have the primary create/list/delete cycle with no dead ends.