Resy MCP

Name: Resy MCP
Author: chrischall

by chrischallversion 1.4.1i★ –iRuns on your computer

Registry nameio.github.chrischall/resy-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory
You need to fill in: RESY_PASSWORD, RESY_AUTH_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: 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

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "resy": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ],
      "env": {
        "RESY_EMAIL": "your-value",
        "RESY_PASSWORD": "your-value",
        "RESY_AUTH_TOKEN": "your-value",
        "RESY_DISABLE_FETCHPROXY": "your-value",
        "RESY_API_KEY": "your-value",
        "RESY_TOKEN_CACHE": "your-value",
        "RESY_TOKEN_FILE": "your-value",
        "RESY_API_KEY_FILE": "your-value",
        "RESY_CAPTURE_TIMEOUT": "your-value",
        "RESY_WS_PORT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add resy --env RESY_EMAIL=your-value --env RESY_PASSWORD=your-value --env RESY_AUTH_TOKEN=your-value --env RESY_DISABLE_FETCHPROXY=your-value --env RESY_API_KEY=your-value --env RESY_TOKEN_CACHE=your-value --env RESY_TOKEN_FILE=your-value --env RESY_API_KEY_FILE=your-value --env RESY_CAPTURE_TIMEOUT=your-value --env RESY_WS_PORT=your-value -- npx -y resy-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "resy": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ],
      "env": {
        "RESY_EMAIL": "your-value",
        "RESY_PASSWORD": "your-value",
        "RESY_AUTH_TOKEN": "your-value",
        "RESY_DISABLE_FETCHPROXY": "your-value",
        "RESY_API_KEY": "your-value",
        "RESY_TOKEN_CACHE": "your-value",
        "RESY_TOKEN_FILE": "your-value",
        "RESY_API_KEY_FILE": "your-value",
        "RESY_CAPTURE_TIMEOUT": "your-value",
        "RESY_WS_PORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "resy": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ],
      "env": {
        "RESY_EMAIL": "your-value",
        "RESY_PASSWORD": "your-value",
        "RESY_AUTH_TOKEN": "your-value",
        "RESY_DISABLE_FETCHPROXY": "your-value",
        "RESY_API_KEY": "your-value",
        "RESY_TOKEN_CACHE": "your-value",
        "RESY_TOKEN_FILE": "your-value",
        "RESY_API_KEY_FILE": "your-value",
        "RESY_CAPTURE_TIMEOUT": "your-value",
        "RESY_WS_PORT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

RESY_EMAIL env
Your Resy account email. Optional — leave unset to use the ContextMint Bridge browser extension instead.
RESY_PASSWORD secret env
Your Resy account password. Optional — leave unset to use the ContextMint Bridge browser extension instead.
RESY_AUTH_TOKEN secret env
Pre-obtained x-resy-auth-token. Overrides email/password and the ContextMint Bridge path. Power users / CI only.
RESY_DISABLE_FETCHPROXY env
Set to '1' to disable the fetchproxy fallback (forces RESY_EMAIL+PASSWORD or RESY_AUTH_TOKEN).
RESY_API_KEY env
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.
RESY_TOKEN_CACHE env
Set to false to disable the on-disk token cache and re-authenticate on every process start. Defaults to enabled.
RESY_TOKEN_FILE env
Absolute path for the token cache file. Defaults to $MCP_DATA_DIR/.resy-mcp/token.json.
RESY_API_KEY_FILE env
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.
RESY_CAPTURE_TIMEOUT env
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…
RESY_WS_PORT env
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 — th…

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account chrischall, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 5654 servers in this category
Published to the registry more recently than 93% of the other 5654 servers in this category
Basic checks equal to or better than 100% of the other 5654 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Resy MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: RESY_PASSWORD, RESY_AUTH_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.4.1) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 2 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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](https://resy.com/terms) 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- .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).

Resy MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

resy-mcp

Tools

Acknowledgement of Terms

Install

Configure

Path 1: direct token (overrides everything)

Opt-out of the fetchproxy fallback (forces 1 or 2)

Environment

Confirmations

Run (local stdio)

Test

Notes