How do I install Resy?

Resy is a local plugin. Install it using npm package: resy-mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Yes. Resy passed MCP Marketplace's automated security scan with a score of 10/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Resy need?

Resy requires the following credentials or environment variables: RESY_EMAIL, RESY_PASSWORD, RESY_AUTH_TOKEN, RESY_DISABLE_FETCHPROXY, RESY_API_KEY, RESY_TOKEN_CACHE, RESY_TOKEN_FILE, RESY_API_KEY_FILE, RESY_CAPTURE_TIMEOUT, RESY_WS_PORT. You can find setup instructions on the server detail page.

What AI apps work with Resy?

Resy uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Resy MCP Server

by Chris Hall

Developer ToolsLow Risk10.0Local

Free

Resy reservation management — search, book, cancel, favorites, and Priority Notify for Claude

About

Resy reservation management — search, book, cancel, favorites, and Priority Notify for Claude

Security Report

10.0

Low Risk10.0Low Risk

Valid MCP server (2 strong, 1 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (83/85 approved); 5 highly-trusted packages.

4 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

What You'll Need

Set these up before or after installing:

Your Resy account email. Optional — leave unset to use the ContextMint Bridge browser extension instead.Optional

Environment variable: RESY_EMAIL

Your Resy account password. Optional — leave unset to use the ContextMint Bridge browser extension instead.Required

Environment variable: RESY_PASSWORD

Pre-obtained x-resy-auth-token. Overrides email/password and the ContextMint Bridge path. Power users / CI only.Required

Environment variable: RESY_AUTH_TOKEN

Set to '1' to disable the fetchproxy fallback (forces RESY_EMAIL+PASSWORD or RESY_AUTH_TOKEN).Optional

Environment variable: RESY_DISABLE_FETCHPROXY

Pin the api key, beating both the key captured from the live site and the compiled-in default. Rotation does not require it: the key is captured and cached automatically.Optional

Environment variable: RESY_API_KEY

Set to false to disable the on-disk token cache and re-authenticate on every process start. Defaults to enabled.Optional

Environment variable: RESY_TOKEN_CACHE

Absolute path for the token cache file. Defaults to $MCP_DATA_DIR/.resy-mcp/token.json.Optional

Environment variable: RESY_TOKEN_FILE

Absolute path for the api-key cache file. Defaults to $MCP_DATA_DIR/.resy-mcp/api-key.json. Holds the bare key captured from the live site, which takes precedence over the compiled-in default.Optional

Environment variable: RESY_API_KEY_FILE

Seconds to wait for the signed-in page to make an API call the bridge can read the auth token from. Defaults to 30. Capture resolves on the next matching request, so an idle tab needs a longer window than a busy one.Optional

Environment variable: RESY_CAPTURE_TIMEOUT

Port for the fetchproxy bridge. The whole fleet shares 37149 (the ContextMint Bridge extension dials it), so override only for local development, test isolation, or a hosted bridged registration — this is the variable to name in the registration's bridgePortEnv.Optional

Environment variable: RESY_WS_PORT

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-chrischall-resy-mcp": {
      "env": {
        "RESY_EMAIL": "your-resy-email-here",
        "RESY_API_KEY": "your-resy-api-key-here",
        "RESY_PASSWORD": "your-resy-password-here",
        "RESY_AUTH_TOKEN": "your-resy-auth-token-here",
        "RESY_DISABLE_FETCHPROXY": "your-resy-disable-fetchproxy-here"
      },
      "args": [
        "-y",
        "resy-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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_key and one of three user-level auth paths (token override, email + password, or a fetchproxy browser bridge). Use at your own discretion.

Tools

Tool	Purpose
`resy_get_profile`	Current user profile (name, email, booking count)
`resy_search_venues`	Search venues with availability for a date + party size
`resy_find_slots`	List bookable slots at a venue
`resy_get_venue`	Full venue details
`resy_book`	Book a reservation (composite: find → details → book)
`resy_list_reservations`	Upcoming / past reservations
`resy_cancel`	Cancel by `resy_token`
`resy_list_favorites`	Favorited venues
`resy_add_favorite` / `resy_remove_favorite`	Manage favorites
`resy_list_notify`	Priority Notify subscriptions
`resy_add_notify` / `resy_remove_notify`	Manage Priority Notify

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 build

Configure

Pick one of three auth paths. The client tries them in this priority order:

RESY_AUTH_TOKEN — pre-obtained x-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/password and caches the returned token.
fetchproxy fallback — when no env vars are set, the server uses the fetchproxy browser bridge to call /3/auth/refresh through your signed-in resy.com tab. Install the ContextMint Bridge extension once from its releases page (unzip the Chrome build and load it unpacked at chrome://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 .sha256 file 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=1

For 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
`RESY_AUTH_TOKEN`	unset	Auth path 1: a pre-obtained `x-resy-auth-token`, used verbatim. Overrides everything.
`RESY_EMAIL` / `RESY_PASSWORD`	unset	Auth path 2: password login. Only needed on a host with no browser.
`RESY_DISABLE_FETCHPROXY`	unset	`1` turns off the ContextMint Bridge path (path 3).
`RESY_TOKEN_CACHE`	on	`false` disables the on-disk token cache. A bridge-minted token is cached for at most 24 hours.
`RESY_TOKEN_FILE`	`$MCP_DATA_DIR/.resy-mcp/token.json`	Token cache path.
`RESY_API_KEY`	captured	Pins the web-app api key, beating the key captured from your tab and the built-in default. Rotation is handled without it.
`RESY_API_KEY_FILE`	`$MCP_DATA_DIR/.resy-mcp/api-key.json`	Api-key cache path (stores the bare key only).
`RESY_CAPTURE_TIMEOUT`	`30`	Seconds to wait for your tab to make an API call the bridge can read the token from.
`RESY_WS_PORT`	`37149`	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
`MCP_CONFIRM_MODE`	`ask-user`	What a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). `ask-user`: two steps — the first call does nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. `auto`: the same two steps, but the model may use the token after reviewing the preview itself. `refuse`: writes are refused on such clients. A client that can show prompts (Claude Code) always gets the real prompt, unless `MCP_CONFIRM_ELICITATION=off`. An unrecognised value is treated as `refuse`.
`MCP_CONFIRM_ELICITATION`	`on`	`off` never shows a confirmation prompt, so every client gets the `MCP_CONFIRM_MODE` path. Set it for a client that claims to support prompts but never shows one (the write hangs — opencode 2.0.x). Any other value stays `on`, with a warning on stderr.
`MCP_CONFIRM_TTL_SECONDS`	`600`	How long a token stays valid.
`MCP_CONFIRM_SECRET`	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 (`MCP_HOST_CONFIRM_SECRET`) and spent tokens are recorded under `MCP_DATA_DIR`, so an approval survives an idle restart.

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.js

Test

npm test             # tsc typecheck + unit tests (mocked fetch)
npm run smoke        # live endpoint probe — requires real .env

Notes

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_KEY pins 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 smoke and adjust.

This project was developed and is maintained by AI (Claude Opus 4.7).