A
licenseA
qualityD
maintenanceEnables AI agents to search restaurants, check availability, and book reservations on OpenTable, with persistent sessions and MFA handling.
9
47 npm
1
MIT
opentable-mcp
by chrischall
Related Servers
Alternatives to opentable-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to search restaurants, check availability, and book reservations on OpenTable, including managing booking history and handling multi-factor authentication.947 npmMIT
- AlicenseBqualityFmaintenanceEnables 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.124MIT
- AlicenseAqualityAmaintenanceManage Resy reservations via natural language: search restaurants, book tables, and manage reservations, favorites, and Priority Notify.15539 npm2MIT
- AlicenseAqualityCmaintenanceEnables Claude, Codex, Cursor, or any MCP client to find restaurants in Japan by location, walking time, party size, private room, cuisine, budget, and seating window, returning real availability for the requested date. It books them in two steps through the user's own signed-in Chrome, preparing a summary and confirmation token first and placing the reservation only after the user approves it.14MIT
- 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
A4.1/5.0
Scored across 15 tools
Disambiguation5/5
Each tool targets a distinct resource+action, including the tricky preview/commit pairs (book_preview vs book, modify_preview vs modify), which are explicitly differentiated by the mandatory-token flow described in their descriptions. Favorites (list/add/remove), catalog (search/get_restaurant/get_menu), and reservation lifecycle (list/find_slots/book/modify/cancel) occupy clearly separate niches. find_slots feeding the booking tools is a documented dependency rather than an overlap.
Naming Consistency5/5
All 15 tools use the opentable_ prefix with snake_case verb_noun structure (list_reservations, add_favorite, find_slots, book_preview, get_restaurant, remove_favorite). The preview/commit naming convention is applied uniformly to both booking and modification flows. No mixed conventions or vague verbs like 'process' or 'handle'.
Tool Count5/5
15 tools sit at the top of the well-scoped range for a domain that legitimately spans search, restaurant/menu details, availability, book/modify/cancel lifecycles with mandatory previews, favorites management, profile, and a bridge diagnostic. No tool appears redundant; even the healthcheck earns its place as a transport diagnostic for the ContextMint bridge.
Completeness4/5
The surface covers the full reservation lifecycle end to end (discover → inspect → find slots → preview → book → modify → cancel) plus favorites, profile, and menus, with no obvious dead ends for core workflows. Minor gaps exist (e.g. no waitlist/notify support, no multi-restaurant availability comparison, no points/loyalty redemption), but these are non-core and agents can work around them.
Maintenance
ActivityActive
ResponsivenessResponsive