Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Restaurant Reservation MCP Serverfind a table for 2 at Carbone in New York for tomorrow night"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Restaurant Reservation MCP Server
A local MCP server for searching and booking restaurant reservations through Resy and OpenTable.
Features
Unified Search: Search both Resy and OpenTable with a single query
Real-time Availability: Check available time slots for any date
Direct Booking: Book Resy reservations directly; get booking links for OpenTable
Reservation Sniper: Auto-book the instant slots become available
Secure Credentials: All credentials stored in Windows Credential Manager (encrypted with DPAPI)
Installation
Configure Claude Code
Add to ~/.claude/settings.json:
Getting Started
1. Set Up Resy Credentials
First, you need your Resy API key and auth token. You can find these in your browser's developer tools while logged into resy.com:
2. Search for Restaurants
You don't need to know which platform a restaurant uses! The search automatically checks both Resy and OpenTable in parallel. Each result includes a platform field (resy or opentable) and an ID like resy-12345 or opentable-67890 - just use these directly with check_availability and make_reservation.
3. Check Availability
4. Book a Reservation
Reservation Sniper
For popular restaurants that release reservations at specific times:
The sniper will:
Start polling 30 seconds before release time
Poll every 500ms once release time hits
Instantly book the first matching slot
Return confirmation or error
Available Tools
Tool | Description |
| Search restaurants by name/location on Resy and/or OpenTable |
| Get available time slots for a restaurant |
| Book a reservation |
| View your upcoming reservations |
| Cancel a booking |
| Store API key/token securely |
| Store email/password for auto-refresh |
| Verify credentials are valid |
| Manually refresh auth token |
| Schedule auto-booking when slots open |
| View scheduled snipes |
| Cancel a scheduled snipe |
Security
No credit card data: This MCP never handles payment info. Bookings use payment methods saved in your Resy/OpenTable accounts.
Windows Credential Manager: All credentials encrypted with DPAPI (same security as Chrome/Edge passwords)
No files: Credentials never written to disk files
HTTPS only: All API calls use TLS 1.3
Rate limited: Max 10 requests/minute per platform
Platform Notes
Resy
Full booking support via unofficial API
Automatic token refresh when expired
Can view and cancel reservations
OpenTable
Search and availability work without auth
Cannot complete booking via API - returns a URL to finish on OpenTable's website
Reservation listing not available
Troubleshooting
"Resy API key not configured"
Run set_credentials with your API key first.
"Resy authentication failed"
Your token expired. Run set_login to enable auto-refresh, or manually get a new token.
OpenTable booking returns URL
This is expected. OpenTable doesn't allow third-party booking - click the URL to complete on their site.
Limitations
Uses unofficial APIs that could change
OpenTable requires manual booking completion
For personal use only