resy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RESY_EMAIL | No | Email for password login. | |
| RESY_API_KEY | No | Override the public Resy API key. | |
| RESY_PASSWORD | No | Password for password login. | |
| RESY_AUTH_TOKEN | No | Pre-obtained x-resy-auth-token. Overrides everything. | |
| RESY_DISABLE_FETCHPROXY | No | Set to 1 to disable fetchproxy fallback. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resy_get_profileA | Get the authenticated Resy user's profile (name, email, phone, booking count, member-since date). Payment method IDs are not exposed. |
| resy_list_payment_methodsA | List the user's saved payment methods on Resy. Returns id, brand, last four digits, expiry, and is_default. The id can be passed as payment_method_id to resy_book. |
| resy_healthcheckA | Resolves the credential the way real tools do, then makes one authenticated request to api.resy.com. Reports which source supplied the credential, whether api.resy.com accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a api.resy.com-side problem'. Read-only; never returns the credential itself. Call this when a real tool fails and you want to know which hop broke. |
| resy_search_venuesA | Search Resy for restaurants with availability. Returns venues including any bookable slot tokens for the requested date + party size. Defaults to NYC geo if lat/lng omitted. |
| resy_find_slotsA | List available reservation slots at a specific venue for a date + party size. Returns slot config_tokens suitable for booking. Tokens expire quickly; book soon after fetching. |
| resy_get_venueB | Get full details for a single Resy venue by id. |
| resy_list_reservationsA | List the user's Resy reservations. Defaults to upcoming; pass scope="past" or "all" to broaden. Each result includes the resy_token needed for cancellation, plus occasion/special_request/cancellability. |
| resy_cancelA | Cancel a Resy reservation by its resy_token (the rr://... identifier returned from resy_book or resy_list_reservations). Confirm-gated: without confirm:true this returns a dry-run preview (venue, date, time, party size, and any cancellation fee) and cancels nothing. |
| resy_bookA | Book a reservation. Composite tool: internally runs find-slots → get booking details → book. Confirm-gated: without confirm:true this returns a dry-run preview (venue, date, party size, the exact slot time that would be booked, and the payment card last-4) and books nothing. Pass desired_time (HH:MM, 24-hour) to target a specific slot. If your exact desired_time is not available the tool does NOT auto-book a different time — it returns the available times so you can pick, unless you pass allow_closest_time:true. Omit desired_time to take the first available slot. Uses the user's default payment method unless payment_method_id is supplied. |
| resy_list_favoritesA | List the user's favorited Resy venues ("hit list"). |
| resy_add_favoriteA | Add a venue to the user's favorites by venue_id. |
| resy_remove_favoriteB | Remove a venue from the user's favorites by venue_id. |
| resy_list_notifyA | List Priority Notify subscriptions — tables you are waiting for when reservations open up. |
| resy_add_notifyA | Subscribe to Priority Notify for a venue/date/party size. Resy emails you when a matching slot opens. time_start / time_end bound the window you're willing to accept (HH:MM, 24h). Resy's notify booking window only accepts near-term dates (~30 days out). |
| resy_remove_notifyA | Cancel a Priority Notify subscription by notify_id. The tool looks up the full spec from resy_list_notify internally — no other input needed. |
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 15 tools
Each tool targets a distinct resource-action pair: reservations, profile, payment methods, venue search, slots, booking, cancellation, favorites, and notify. The only related pair is search_venues vs find_slots, but the former is venue discovery and the latter is slot-level lookup at a specific venue, so an agent can select correctly.
All tools share a clear resy_ prefix and snake_case, with a dominant verb_noun pattern (list_reservations, add_favorite, remove_notify). Minor deviations are resy_book and resy_cancel without an explicit object, plus resy_healthcheck as a non-verb_noun name, but these are still predictable and readable.
15 tools sits at the upper edge of a well-scoped server but every tool maps to a distinct, useful Resy workflow: reservation lifecycle, venue discovery, favorites, notify, payment methods, profile, and diagnostics. No tool feels redundant or filler.
The surface covers booking, listing, and cancelling reservations; venue search and detail lookup; favorite list/add/remove; notify subscribe/unsubscribe; and the necessary context of payment methods and profile. Favorites and notify have full lifecycle coverage, and reservations have the primary create/list/delete cycle with no dead ends.