@striderlabs/mcp-opentable
Related Servers
Alternatives to @striderlabs/mcp-opentable
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to search restaurants, check availability, and book reservations on OpenTable, with persistent sessions and MFA handling.960 npm1MIT
- 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.14996 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.-
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to manage restaurant reservations through typed MCP tools, including checking table availability, creating and canceling reservations, and listing the day's confirmed bookings.-
- FlicenseNot gradedqualityBmaintenanceEnables customers and AI agents to check restaurant table availability and create bookings, returning confirmations or nearby alternative times when a slot is full, with atomic capacity control and idempotent handling.-
TDQS
Scored across 9 tools
Each tool targets a distinct concern: auth status/login/logout, restaurant search/details, availability checking, and reservation create/list/cancel. No two tools overlap in purpose, so an agent can easily select the right one.
All tools use a consistent opentable_ prefix followed by clear verb_noun names (search, get_restaurant, check_availability, make_reservation, get_reservations, cancel_reservation). Even the auth tools (status, login, logout) follow the same verb style. The pattern is predictable and uniform.
With 9 tools, the server is well-scoped for an OpenTable integration. Each tool serves a necessary function in the core workflow (auth, search, details, availability, reservation management), and none feel redundant or superficial.
The toolset covers the full reservation lifecycle: search, view details, check availability, book, list, and cancel. A minor gap is the lack of a modify/update reservation tool, but agents can work around this by canceling and rebooking. Overall, the surface is complete for the main domain.