resy-mcp
Manage your own Resy account end-to-end through natural language: find restaurants, book and cancel tables, and manage favorites and Priority Notify alerts.
Account:
resy_get_profile(name, email, phone, booking count) andresy_list_payment_methods(card id/brand/last-4 to use when booking).Discovery:
resy_search_venues(by date + party size, keyword, geo/radius),resy_get_venue(full details),resy_find_slots(bookable time slots and config tokens).Booking:
resy_book— a composite find-slots → details → book flow that targets an exact slot time, seating type and terms; can refuse duplicates and use a chosen payment method.Reservations:
resy_list_reservations(upcoming/past/all, withresy_token) andresy_cancelby that token.Favorites:
resy_list_favorites,resy_add_favorite,resy_remove_favorite.Priority Notify:
resy_list_notify,resy_add_notify(venue/date/party size plus an acceptable time window),resy_remove_notify.Diagnostics:
resy_healthcheckverifies which credential source was used and whether api.resy.com accepted it.Safety: writes (
resy_book,resy_cancel) require confirmation — an elicitation prompt where supported, otherwise a two-step preview +confirmTokenflow; a booking only ever books the exact slot a preview showed.Auth (from README): a pre-obtained
RESY_AUTH_TOKEN, email/password login, or a signed-in browser tab via the ContextMint Bridge — your own account only, personal non-commercial use.
Note: resy_list_payment_methods and resy_healthcheck appear in the schema but not in the README's tool table.
Click on "Deploy 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., "@resy-mcp Find available tables at Carbone in NYC 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.
resy-mcp
Resy reservation management as an MCP server for Claude — search restaurants, book tables, manage reservations, favorites, and Priority Notify via natural language.
⚠️ Resy does not publish an official API. This server uses the same private endpoints the Resy web app calls, with the public web-app
api_keyand one of three user-level auth paths (token override, email + password, or a fetchproxy browser bridge). Use at your own discretion.
Tools
Tool | Purpose |
| Current user profile (name, email, booking count) |
| Search venues with availability for a date + party size |
| List bookable slots at a venue |
| Full venue details |
| Book a reservation (composite: find → details → book) |
| Upcoming / past reservations |
| Cancel by |
| Favorited venues |
| Manage favorites |
| Priority Notify subscriptions |
| Manage Priority Notify |
Related MCP server: Restaurant Reservation MCP Server
Acknowledgement of Terms
By using this MCP server, you acknowledge and agree to the following:
1. This server accesses your own Resy account. Auth happens via your own credentials (email/password) or your own signed-in browser session through the ContextMint Bridge extension. It does not — and cannot — access anyone else's reservations.
2. Resy's Terms of Service govern your use of this server, just as they govern your direct use of resy.com. Resy's ToS prohibits the use of bots and automated booking, enforces rate limits, deploys CAPTCHA, and states that automated booking bots can result in account bans. Reservations are not transferable and may not be resold.
You are agreeing to those terms — read by the maintainer 2026-05-23 — every time you invoke a tool in this server.
3. Personal, non-commercial use only. This project is not affiliated with, endorsed by, sponsored by, or in partnership with Resy or American Express. It is a personal automation tool intended only to help one user manage one person's reservations from the command line. Specifically: do not use it to mass-book, snipe slot-tokens the moment they open, resell tables, or compete with Resy. The booking tools exist so you can book the table you would have booked anyway, faster.
4. Stability is not guaranteed. This server calls the same api.resy.com endpoints the Resy mobile app and web app call, with the same public web-app api_key. Resy may change endpoint shapes, rotate keys, or add new bot detection at any time. It may break.
5. You accept full responsibility for any consequences of using this server in connection with your Resy account — rate limiting, slot-lock rejections, account warnings, suspension, or bans. If Resy objects to your use, stop using this server.
This section is the maintainer's good-faith summary of the terms — it is not legal advice and does not modify or supersede Resy's actual ToS.
Install
npm install
npm run buildConfigure
Pick one of three auth paths. The client tries them in this priority order:
RESY_AUTH_TOKEN— pre-obtainedx-resy-auth-token. Overrides everything; useful for CI or power users who already have a token.RESY_EMAIL+RESY_PASSWORD— the classic flow. POSTs/3/auth/passwordand caches the returned token.fetchproxy fallback — when no env vars are set, the server uses the fetchproxy browser bridge to call
/3/auth/refreshthrough your signed-in resy.com tab. Install the ContextMint Bridge extension once from its releases page (unzip the Chrome build and load it unpacked atchrome://extensions; Safari isn't available yet — it will ship inside the ContextMint app, which has no public download — so use Chrome for now), sign into resy.com, and that's it — no credentials in env.ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README points to it. Its source is public at nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the
.sha256file published beside it (shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256).
Copy .env.example to .env and fill in whichever path you want:
# Path 2: password login (classic)
RESY_EMAIL=you@example.com
RESY_PASSWORD=changeme
# Path 1: direct token (overrides everything)
RESY_AUTH_TOKEN=...
# Opt-out of the fetchproxy fallback (forces 1 or 2)
RESY_DISABLE_FETCHPROXY=1For MCPB / Claude Desktop install, the packaged manifest prompts for all three optional inputs — leave them blank to route through ContextMint Bridge instead.
Environment
Every variable is optional.
variable | default | |
| unset | Auth path 1: a pre-obtained |
| unset | Auth path 2: password login. Only needed on a host with no browser. |
| unset |
|
| on |
|
|
| Token cache path. |
| captured | Pins the web-app api key, beating the key captured from your tab and the built-in default. Rotation is handled without it. |
|
| Api-key cache path (stores the bare key only). |
|
| Seconds to wait for your tab to make an API call the bridge can read the token from. |
|
| Bridge concentrator port. Every fetchproxy MCP on one machine shares it, so move it for all of them or none (local dev, tests, or a hosted registration's bridge port). |
Confirmations
resy_book and resy_cancel ask you to confirm before they change anything. A client that can show a confirmation prompt (Claude Code) shows one, unless MCP_CONFIRM_ELICITATION=off. On a client that cannot, the first call returns a preview and a confirmToken, and only a repeat call with that token goes ahead:
variable | default | |
|
| What a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). |
|
|
|
|
| How long a token stays valid. |
| random per process | Signing key; set it only if tokens must survive a server restart. On mcp-host the host supplies a stable per-child key ( |
resy_book additionally books only the exact slot a preview showed. On a client without prompts the preview itself carries the confirmToken, bound to that slot's time, seating type and terms; once you approve, the model repeats the call with the preview's time as desired_time plus the token. On a client with prompts the call must name the slot (desired_time + slot_type + terms_token) before you are asked. If the slot or its terms changed in between, nothing is booked and a fresh preview is returned.
Run (local stdio)
node dist/bundle.jsTest
npm test # tsc typecheck + unit tests (mocked fetch)
npm run smoke # live endpoint probe — requires real .envNotes
The api key is the public one baked into resy.com's JS bundle. It is captured from your signed-in tab and cached, so a rotation is picked up on its own —
RESY_API_KEYpins a specific key instead, and is only needed when you want to override that.Favorites and Priority Notify endpoint paths are reverse-engineered; if live endpoints differ, run
npm run smokeand adjust.
This project was developed and is maintained by AI (Claude Opus 4.7).
Available Tools
15 toolsresy_add_favoriteB
Add a venue to the user's favorites by venue_id.
Inputs: venue_id (required).
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).
Inputs: date (required), venue_id (required), party_size (required), time_end, +2 more.
resy_bookADestructive
Book a reservation. Composite tool: internally runs find-slots → get booking details → book. It books ONLY the exact slot a preview showed. The first call returns a preview (the Resy account, venue, date, party size, the exact slot time that would be booked, its slot_type, the payment card last-4, and the slot's cancellation_policy / payment_terms — any no-show fee or deposit) 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 (which previews the nearest slot). Omit desired_time to preview the first available slot. Resy can list several slots at one time with different seating types (Dining Room / Bar / Patio) and different fees; pass slot_type to target one. To book: on a client without a confirmation prompt the preview comes back with a confirmToken bound to that exact slot and its terms — after the user approves, call again with the same arguments plus the preview's time as desired_time and the confirmToken. On a client that can prompt, call again with the preview's time as desired_time, its slot_type and its terms_token, and the user is asked to confirm. If that slot is gone, or its seating type or cancellation/payment terms changed since the preview, nothing is booked and a fresh preview is returned. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Before booking, it checks your existing reservations and refuses if you already hold one at this venue on this date (e.g. an earlier call that timed out but went through); pass allow_duplicate:true to book another anyway. Uses the user's default payment method unless payment_method_id is supplied (it must be one of the saved cards from resy_list_payment_methods; the preview names the card by brand and last-4).
Inputs: date (required), venue_id (required), party_size (required), lat, +8 more.
resy_cancelADestructive
Cancel a Resy reservation by its resy_token (the rr://... identifier returned from resy_book or resy_list_reservations). The confirmation preview shows the Resy account, venue, date, time, party size, and any cancellation fee. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Once confirmed, the result carries cancelled (boolean: true only when the cancellation is confirmed) and outcome ("cancelled", "not_cancelled", or "unknown"). On "unknown", cancelled is false but the reservation MAY have been cancelled — check resy_list_reservations before retrying.
Inputs: resy_token (required), confirmToken.
resy_find_slotsARead-only
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.
Inputs: date (required), venue_id (required), party_size (required), lat, +1 more.
resy_get_profileARead-only
Get the authenticated Resy user's profile (name, email, phone, booking count, member-since date). Payment method IDs are not exposed.
Inputs: view.
resy_get_venueARead-only
Get full details for a single Resy venue by id.
Inputs: venue_id (required).
resy_healthcheckVerify credentials and upstream reachabilityARead-onlyIdempotent
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.
Inputs: no named parameters.
resy_list_favoritesBRead-only
List the user's favorited Resy venues ("hit list").
Inputs: view.
resy_list_notifyARead-only
List Priority Notify subscriptions — tables you are waiting for when reservations open up.
Inputs: view.
resy_list_payment_methodsARead-only
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.
Inputs: view.
resy_list_reservationsARead-only
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.
Inputs: view, scope.
resy_remove_favoriteB
Remove a venue from the user's favorites by venue_id.
Inputs: venue_id (required).
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.
Inputs: notify_id (required).
resy_search_venuesARead-only
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.
Inputs: date (required), party_size (required), lat, lng, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 15 tools
Each tool targets a distinct resource and action (search venues, get venue, find slots, book, cancel, favorites, notify, profile, payments). The only mild overlap is resy_search_venues vs resy_find_slots and resy_book, since search can return slot tokens and book internally runs find-slots, but the descriptions clearly delineate when to use each.
All tools use a consistent resy_ prefix with snake_case verb_noun naming (resy_add_favorite, resy_list_reservations, resy_cancel, resy_book). The one minor deviation is resy_healthcheck, which is a noun rather than a verb_noun, but the convention otherwise holds throughout.
15 tools sit right at the top of the well-scoped range, and each one maps to a concrete user-facing operation in the reservation lifecycle. No tool feels redundant or padded; healthcheck earns its place as a diagnostic aid.
The surface covers the full workflow: discover venues, inspect them, find slots, book with confirmation, list and cancel reservations, plus favorites management, Priority Notify subscriptions, profile, and payment methods. The added duplicate-booking guard and healthcheck close common dead ends.
Maintenance
Related MCP Connectors
Find Resy restaurants and request reservations through Scout; the user approves every booking.
Resy MCP server for ChatGPT, Claude and any AI agent: search restaurants, check availability, book a reservation, list reservations, change a reservation, cancel a reservation, set a Notify alert and remove a Notify alert in your own Resy account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Resy yourself; Cotlet does not store your password and you need no Resy API key. About the official Resy API: Resy has no public API (checked 27 Oct 2026). Its official Resy app runs only inside Claude and ChatGPT: in Claude it shows live availability and sends you to Resy to book, in ChatGPT it can also book a table. Setup and FAQ: https://cotlet.dev/integrations/resy-api-mcp-server
Book hard-to-get restaurant reservations on your own Resy, SevenRooms, or OpenTable account.
AI phones restaurants and local businesses to book, move or cancel reservations and appointments.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables restaurant reservation management through SevenRooms API, allowing users to create reservations and query available time slots with guest details and party size information.-
- AlicenseBqualityDmaintenanceEnables users to search, check availability, and book restaurant reservations across Resy and OpenTable platforms. It supports direct booking for Resy and includes an automated reservation 'sniper' for securing high-demand slots the moment they become available.124MIT
- AlicenseAqualityAmaintenanceManage OpenTable reservations via natural language — find slots, book, cancel, manage favorites, and read your dashboard using your own browser session.15421 npm2MIT
- AlicenseAqualityDmaintenanceEnables AI agents to search restaurants, check availability, and book reservations on OpenTable, including managing booking history and handling multi-factor authentication.9MIT