@striderlabs/mcp-opentable
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENTABLE_EMAIL | No | Email address for your OpenTable account. | |
| OPENTABLE_PASSWORD | No | Password for your OpenTable account. Highly recommend using .env file. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| opentable_statusA | Check if the user is logged in to OpenTable. Returns login status and instructions if not authenticated. Call this before any other OpenTable operations. |
| opentable_loginA | Get the OpenTable login URL and instructions for the user to authenticate. Use this when opentable_status returns not logged in. |
| opentable_logoutA | Clear the stored OpenTable session cookies. Use this to log out or reset the authentication state. |
| opentable_searchB | Search for restaurants on OpenTable by location, cuisine, party size, date, and time. |
| opentable_get_restaurantB | Get detailed information about a specific restaurant including description, address, hours, and features. |
| opentable_check_availabilityA | Check available reservation time slots for a restaurant on a specific date and party size. |
| opentable_make_reservationA | Book a restaurant reservation on OpenTable. Set confirm=false to preview before booking, confirm=true to actually book. Requires the user to be logged in. |
| opentable_get_reservationsA | List all upcoming reservations for the logged-in user. Requires authentication. |
| opentable_cancel_reservationA | Cancel an existing reservation. Set confirm=false to preview, confirm=true to actually cancel. This action cannot be undone. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.