Log inSubmit server
Resy MCP logo

Resy MCP

Manage Resy profiles, restaurant searches, reservations, favorites, and Priority Notify through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Resy MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "resy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ],
      "env": {
        "RESY_AUTH_TOKEN": "YOUR_VALUE_HERE",
        "RESY_EMAIL": "YOUR_VALUE_HERE",
        "RESY_PASSWORD": "YOUR_VALUE_HERE",
        "RESY_DISABLE_FETCHPROXY": "YOUR_VALUE_HERE",
        "RESY_TOKEN_CACHE": "YOUR_VALUE_HERE",
        "RESY_TOKEN_FILE": "YOUR_VALUE_HERE",
        "RESY_API_KEY": "YOUR_VALUE_HERE",
        "RESY_API_KEY_FILE": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 15 tools correctly (Today).

Overview

The resy-mcp MCP server connects an MCP client to Resy reservation functions for searching venues, finding available tables, booking and canceling reservations, and managing favorites and Priority Notify. It authenticates with a supplied Resy token, email and password, or a signed-in browser session through the ContextMint Bridge. Booking and cancellation include confirmation safeguards, including previews and confirmation tokens where client prompts are unavailable. Reach for it when an agent needs to manage one user's Resy reservations, while accounting for Resy's private endpoints, automation restrictions, and possible API changes.

Use cases

  • Search restaurants for available tables by date and party size
  • Book a selected Resy reservation after confirmation
  • Review or cancel upcoming and past reservations
  • Manage favorited venues
  • Subscribe to or remove Priority Notify alerts

Key features

  • Resy venue and availability search
  • Reservation booking and cancellation
  • Profile and reservation history access
  • Favorites management
  • Priority Notify management
  • Confirmation previews for write operations

Tools15

What Resy MCP lets your agent do. Expand a tool for its parameters.

Verified live~3.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

6/6 checks healthy over the last 51d

What it can do

From the 15 tools this server returned when we ran it; 15 declare their own safety hints.

Can delete or modify data · 4Handles credentials · 5Makes network requests · 15Read-only tools · 11
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age191 days
Maintainers1

Observed 2026-10-28 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · resy-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads3.5kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed15Callable tools this server registers over MCP.

How Resy MCP works

What resy-mcp does

The resy-mcp MCP server exposes Resy account and reservation operations to MCP-compatible clients. It can retrieve the current profile, search venues by date and party size, inspect venue details, and list bookable slots. Reservation management includes viewing upcoming or past bookings, booking a specific table, and canceling a reservation by its Resy token.

The server also covers two account-management areas: favorited venues and Priority Notify subscriptions. Adding and removing favorites or notify subscriptions is available through dedicated tools. The intended use is personal management of one user's own Resy account, not bulk booking, table resale, or automated competition for newly released slots.

How it works

The resy-mcp MCP server calls the private endpoints used by the Resy web and mobile applications. Resy does not publish an official API, so endpoint behavior, API keys, rate limits, and bot detection may change without notice. Use of the server remains subject to Resy's Terms of Service, which the project notes may prohibit bots and automated booking and may lead to account restrictions.

Authentication follows a priority order. A pre-obtained RESY_AUTH_TOKEN takes precedence, followed by email-and-password authentication. If neither is configured, the server can use the fetchproxy browser bridge through a signed-in resy.com tab and the ContextMint Bridge extension. Tokens and API-key data may be cached on disk according to the configured settings.

Writes are guarded by confirmations. resy_book and resy_cancel can request an interactive prompt. On clients without prompt support, the initial call returns a preview and confirmation token, and a later call must provide the approval token. Booking is tied to the exact previewed slot, including its time, seating type, and terms; changed slot data results in a new preview instead of a booking.

Setup and configuration

Install dependencies and build the package with npm install followed by npm run build. Run the local stdio server with node dist/bundle.js.

Configuration is optional because the browser-bridge path can provide authentication. Supported settings include:

  • RESY_AUTH_TOKEN for a directly supplied Resy token.
  • RESY_EMAIL and RESY_PASSWORD for password login.
  • RESY_DISABLE_FETCHPROXY=1 to disable browser-bridge authentication.
  • RESY_TOKEN_CACHE and RESY_TOKEN_FILE to control token caching.
  • RESY_API_KEY and RESY_API_KEY_FILE to provide or store the web-app API key.
  • RESY_CAPTURE_TIMEOUT and RESY_WS_PORT to configure bridge behavior.

Confirmation behavior can be adjusted with MCP_CONFIRM_MODE, MCP_CONFIRM_ELICITATION, MCP_CONFIRM_TTL_SECONDS, and MCP_CONFIRM_SECRET. The project also documents MCPB and Claude Desktop installation, with optional authentication fields that can be left blank when using the bridge.

Tools and capabilities

The resy-mcp MCP server provides tools for:

  • Reading the account profile.
  • Searching venues and inspecting availability.
  • Finding slots and retrieving venue details.
  • Booking and canceling reservations.
  • Listing upcoming and past reservations.
  • Listing, adding, and removing favorites.
  • Listing, adding, and removing Priority Notify subscriptions.

The composite booking operation finds a venue slot, retrieves its details, and submits the booking request after the required confirmation flow.

Limitations and notes

This integration is unaffiliated with Resy or American Express and is intended for personal, non-commercial use. The maintainer warns that Resy may rotate keys, alter endpoint formats, introduce additional bot detection, enforce rate limits, reject slot locks, or suspend accounts. Users accept responsibility for consequences associated with their account and should stop using the server if Resy objects to the activity.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Resy MCP

resy-mcp is an MCP server that connects AI clients to a user's Resy account through private web-app endpoints. Its main tools search venues and slots, retrieve venue details, book or cancel reservations, list bookings, manage favorites, and manage Priority Notify subscriptions with token, password, or browser-bridge authentication.

Install it with `npm install`, build it with `npm run build`, and run `node dist/bundle.js` for a local stdio server. The project also documents MCPB and Claude Desktop installation.

It authenticates first with `RESY_AUTH_TOKEN`, then with `RESY_EMAIL` and `RESY_PASSWORD`, or otherwise through a signed-in resy.com tab using the ContextMint Bridge browser extension. All environment variables are optional when the browser bridge is available.

Yes, the project documents an MCPB and Claude Desktop installation path. Its packaged manifest prompts for optional authentication values, which can be left blank when authentication is routed through ContextMint Bridge.

Yes, `resy_book` and `resy_cancel` use confirmation safeguards. Clients with prompt support can display a confirmation request; other clients receive a preview and confirmation token that must be used in a subsequent call.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewResy MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/resy-mcp?style=directory)](https://allmcps.com/mcp/resy-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/resy-mcp"><img src="https://allmcps.com/api/badge/resy-mcp?style=directory" alt="Resy MCP on AllMCPs" /></a>