Resy MCP Server

Official Resy connector for Claude. Discover U.S. restaurants, check real-time table availability, and start reservation flows from chat.

Travel by Resy (American Express) OAuth2 active

Connect (Remote Server) Docs

Overview

Resy is an American Express owned restaurant reservation platform. The official Resy connector, launched April 23, 2026, brings live Resy availability data into Claude using the Model Context Protocol. When users ask Claude where to eat, Claude can surface recommendations from Resy's U.S. inventory, show real bookable timeslots, and hand off to the Resy app or Resy.com to complete the booking.

The connector is provider-hosted by Resy and listed in Claude's Connectors Directory. There is no self-hosted server to run and no GitHub repo to clone. Users add it in Claude's settings under Connectors. Authentication to Resy is not required to browse availability, only when a user actually books a table or sets a Notify alert, at which point the standard Resy sign-in is invoked.

Coverage is currently limited to U.S. Resy restaurants. Capabilities documented by Resy and Anthropic include browsing restaurants and collections, viewing real time table availability, setting Notify alerts for sold-out times, and beginning the booking flow which is finalized on Resy.com or the Resy mobile app.

Tools

Tool	Description
`search_restaurants`	Find U.S. restaurants on Resy by location, cuisine, date, time, and party size. (Capability described in Resy and Anthropic announcements; exact tool name is not publicly documented.)
`check_availability`	Return real-time bookable timeslots for a specific Resy restaurant, date, and party size.
`get_restaurant_details`	Return Resy venue information such as cuisine, neighborhood, price, and editorial content.
`browse_collections`	Surface curated Resy collections (e.g. lists, neighborhoods, occasions) for discovery.
`set_notify_alert`	Create a Resy Notify alert for a restaurant, date, and party size so the user is pinged when a table opens up. Requires sign-in to Resy.
`start_booking`	Begin the reservation flow for a selected timeslot. Final confirmation is completed by the user on Resy.com or the Resy mobile app.

Setup Guide

The Resy connector is provider-hosted by Resy and distributed through Claude's Connectors Directory. There is no command to install and no JSON config to edit.

Requirements

A Claude account (claude.ai, Claude Desktop, or Claude mobile)
A Resy account is only needed when you book a table or set a Notify alert

Enable the connector

Open Claude and go to Settings > Connectors (or Customize > Connectors)
Search for Resy
Click Connect
You do not need to sign into Resy during setup; sign-in happens later when you book

Directory listing

https://claude.ai/directory/connectors/resy

Coverage

U.S. restaurants only at launch (April 23, 2026)

Notes

Final reservation confirmation happens on Resy.com or the Resy mobile app, not inside Claude
For Claude API or third-party MCP clients, this connector is accessed via Claude's hosted connectors infrastructure rather than a public MCP server URL you can wire into other tools

Use Cases

Plan a dinner from chat: ask Claude for romantic spots in the West Village next Friday at 8pm for two and get live, bookable Resy times
Combine itinerary research and reservations in one thread, then hand off to Resy.com to confirm the actual booking
Track hard-to-get tables by having Claude set a Resy Notify alert when a sold-out time opens up
Compare a shortlist of restaurants by cuisine, neighborhood, and current availability before committing to one
Explore curated Resy collections (e.g. "new openings", "outdoor dining") from inside a Claude conversation

Example Prompts

"Find me a Resy reservation for 4 people this Saturday at 7:30pm in Brooklyn, Italian or Mediterranean."
"What are the top Resy restaurants in San Francisco for a birthday dinner next month?"
"Check if Carbone has any tables for two on Thursday between 6 and 9pm."
"Set a Resy Notify alert for Tatiana the next 3 Fridays at 8pm, party of 2."
"Show me Resy's newest restaurant collections in Los Angeles."

Pros

Official integration from Resy and American Express, using live Resy availability instead of stale or scraped data
Zero setup: enable from Claude's Connectors Directory, no server to run or config to edit
No Resy sign-in required just to browse or check availability; auth only kicks in at booking
Works across Claude.ai, Claude Desktop, and Claude mobile via Anthropic's hosted connector infrastructure

Limitations

U.S. restaurants only at launch; international Resy inventory is not yet covered
Booking is not fully completed inside Claude; users are redirected to Resy.com or the Resy app to confirm
Resy does not publish a developer-facing MCP server URL or tool schema, so the connector cannot be wired into arbitrary third-party MCP clients today

Alternatives

OpenTable: no official MCP server as of May 2026; community projects such as jrklein343-svg/restaurant-mcp wrap both Resy and OpenTable but are unofficial
Community Resy MCP servers like Jpc54066/resy-mcp that wrap Resy's public web APIs, useful if you need a self-hosted option but unsupported by Resy
Booking.com or other travel MCP servers for broader hotel and restaurant booking scenarios