Restaurant Reservation

Unifies Resy and OpenTable search, availability, and booking via a local MCP server.

javascript

0

GitHub Stars

javascript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "jrklein343-svg-restaurant-mcp": {
      "command": "node",
      "args": [
        "C:\\\\Users\\\\jrkle\\\\Desktop\\\\restaurant-mcp\\\\dist\\\\index.js"
      ]
    }
  }
}

You run a local MCP server that lets you search for restaurant reservations across Resy and OpenTable, check availability in real time, and book or obtain booking links directly from your client. This server provides a unified experience, so you don’t need to manage separate connections to each platform. It stores credentials securely and can automatically attempt reservations the moment slots become available.

How to use

Set up your MCP client to communicate with the restaurant reservation server you run locally. You will use the MCP’s available tools to search for restaurants, check availability, make reservations, and manage your bookings.

How to install

Prerequisites: you need Node.js installed on your system and access to a shell.

{
  "example": {
    "quickStart": true
  }
}

Additional setup and usage notes

The MCP server runs locally and uses a Node script built from the provided project. You will install dependencies, build the project, and then run the server through the configured entry point.

Configuration for your MCP client is provided through a standard settings file. You define a server entry named to identify the restaurant reservations service and point it to the local startup script.

Security and credentials are handled by storing sensitive information securely in the system’s credential storage. No payment data is handled by the MCP server itself.

Security

No credit card data is handled by this MCP server. Bookings use payment methods saved in your Resy/OpenTable accounts.
Credentials are kept in secure storage and never written to disk by default.
All API calls are transmitted over TLS 1.3 where available.

Troubleshooting

If you encounter credential-related errors, ensure you have correctly configured credentials in the client and that the MCP server is running and reachable on your local machine.

If a booking flow returns a URL for OpenTable, this is expected because third-party booking via API may be restricted for OpenTable. Click the URL to complete the booking on OpenTable’s site.

Notes on capabilities and limitations

The server uses unofficial APIs that could change, so availability and booking behaviors may vary over time.
OpenTable can provide search and availability but may require manual completion for bookings.
For personal use only.

Available tools

search_restaurants

Search restaurants by name or location across Resy and OpenTable with a single query.

check_availability

Retrieve available time slots for a specific restaurant, platform, and date.

make_reservation

Book a reservation using a restaurant ID, platform, slot, date, and party size.

list_reservations

List your upcoming reservations.

cancel_reservation

Cancel an existing booking.

set_credentials

Store API keys or tokens securely for future use.

set_login

Store login credentials to enable automatic token refresh.

check_auth_status

Verify that your credentials are valid and active.

refresh_token

Manually refresh the authentication token.

snipe_reservation

Schedule automatic booking when preferred slots become available.

list_snipes

View all scheduled snipes.

cancel_snipe

Cancel a scheduled snipe.