reservations-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RESY_API_KEY | No | Resy API key. Defaults to the public key embedded in Resy's web client; override if it rotates. | |
| YELP_API_KEY | No | Free from the Yelp Fusion console. | |
| RESY_AUTH_TOKEN | No | Required for Resy availability/booking. Obtain from resy.com DevTools. | |
| GOOGLE_PLACES_API_KEY | No | Google Places API (New) key. | |
| RESY_PAYMENT_METHOD_ID | No | Default card for bookings. List IDs via resy_payment_methods. |
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 |
|---|---|
| discover_restaurantsA | Find restaurants by free-text criteria (e.g. 'Hudson River waterfront with Manhattan skyline view, outdoor seating, kid-friendly, great cocktails'). Read-only. Uses Google Places (richest: returns goodForChildren / outdoorSeating / servesCocktails) and/or Yelp depending on which API keys are configured. |
| resy_searchA | Search Resy's own venue index by name/keyword. Returns Resy venue ids needed for availability and booking. |
| resy_availabilityA | List available reservation slots for a Resy venue on a date for a party size. Each slot includes a bookToken used by resy_booking_preview. |
| resy_booking_previewA | STEP 1 of booking. Resolves a slot bookToken into a confirmable booking and surfaces the time, seating type, and any cancellation/no-show fee. Does NOT book. Returns a real book_token to pass to resy_book. |
| resy_bookA | STEP 2 of booking — IRREVERSIBLE. Books the reservation from a book_token returned by resy_booking_preview. Requires confirm:true. May incur a cancellation/no-show fee per the venue's policy. |
| resy_payment_methodsA | List the payment method ids saved on your Resy account (needed for bookings that require a card). |
| resy_loginA | Exchange your Resy email + password for an auth token, stored locally (~/.config/reservations-mcp). Password is used once and never saved. Prefer setting RESY_AUTH_TOKEN directly if you can. |
| resy_my_reservationsA | List your upcoming Resy reservations. |
| tock_searchA | Search Tock venues. NOTE: Tock is a best-effort stub in v1 and returns guidance + a direct link rather than live data. |
| statusA | Show which providers are configured (which API keys / tokens are present). |
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 10 tools
Most tools are clearly distinct based on their action in the booking flow (availability, preview, book, list). The main overlap is between resy_search and discover_restaurants, both of which find restaurants but via different data sources; this could cause some confusion for agents.
The majority of tools follow a 'resy_' prefix pattern, but discover_restaurants and status break this convention. The mix of provider-prefixed, standalone, and verb_noun names is somewhat inconsistent.
10 tools is a reasonable size for a reservations-focused server. Each tool targets a specific part of the domain: discovery, availability, booking, account management, and status.
The set covers reservation creation and listing, but misses critical operations like canceling or modifying an existing reservation. Tock support is also only a stub, making the surface incomplete for that provider.