Claude + Resy: What the Integration Can (and Can't) Do in 2026
No — there’s no official Claude Resy connector, and unlike a lot of restaurant tools, Resy has no self-serve API to build one against. Resy isn’t in Anthropic’s connectors directory, ships no first-party MCP server, and its restaurant-facing platform (Resy OS) exposes only a partner-only REST API — access is granted through Resy’s partnerships team to approved POS, CRM, and loyalty vendors, not to individual restaurants. There’s no developer portal where an operator generates a key.
One thing to clear up first, because it causes confusion: the Resy most people know is the consumer app where Amex Platinum cardholders book tables and use their dining credit. That’s a different surface from Resy OS, the reservation-and-guest system your host stand runs. This guide is about the operator side — and on that side, the honest answer is there’s no key to hand Claude.
Why “just connect Claude to Resy” doesn’t work
Resy is owned by American Express, and it treats reservation and guest data as a closed, partner-governed system. Its API for reservations, availability, and guest metadata is issued only to companies Resy approves through a direct partnership agreement — that’s how integrations with POS systems like Toast, Square, and Lightspeed exist. A restaurant using Resy OS can benefit from those partner integrations, but it can’t self-provision its own credentials.
That single fact shapes everything about Claude and Resy:
- There’s no directory connector to toggle on.
- There’s no vendor MCP server Resy publishes (an “MCP server” is the small connector a technical person builds and runs — but there’s no self-serve credential to feed it in the first place).
- Even a developer willing to build a connector has nothing to authenticate with unless they’re an approved Resy partner. And Resy isn’t on Zapier either, so the usual no-code shortcut isn’t there.
So the honest starting point: for an operator, there is no Resy key to give Claude at all.
A 2026 note worth flagging: Amex is folding Tock’s inventory into Resy over summer 2026, and has told restaurants to expect a unified restaurant-facing platform (“the best of both”) landing around 2027. So the operator tooling and any partner-integration surface is actively in flux — another reason not to bank on a stable self-serve hook appearing soon.
What Claude can do around Resy today
Because there’s no operator API, Claude works on the seams around Resy, not inside it:
- Paste an exported Resy guest or covers report and ask Claude to summarize it, spot your regulars, or draft VIP notes for the floor.
- Have Claude draft the confirmation, reminder, or apology emails you send guests, and the shift briefings you write from the reservation book.
- Use Claude to reason about pacing, no-show patterns, or large-party policy from figures you copy in.
None of that is a live connection — it’s Claude working on data you bring it, inside a chat you’re actively driving.
The limits that actually matter
Two limits define it, and the first is unusually hard here:
- There’s no operator credential at all. With Toast or Olo you at least could connect if you became a partner. On the Resy operator side, the API simply isn’t handed to restaurants — so there’s nothing for a connector to authenticate with. Claude stays on exports and email.
- No triggers, no monitoring — and no sending. Even on the data you paste in, Claude only runs inside a conversation you start. There’s no “when a VIP books, brief the floor” or “when a big party no-shows, email them.” And Claude’s built-in email drafts in both Gmail and Outlook but doesn’t send — you still hit send yourself. The closest thing to running on its own is a scheduled task that fires only while your laptop is awake and the app is open.
So Claude around Resy is a reasoning-and-drafting helper on data you carry over — genuinely useful, but not a live line into your book.
If you want Resy work that runs on its own: Carly
The moment you want something to happen around your reservations without you in the chat — a VIP-arrival brief to the floor, a same-day confirmation to a large party, a follow-up after a no-show — you’ve crossed past what Claude can do.
Here’s where the honesty ladder matters most. Claude dead-ends at Resy’s closed operator gate: no self-serve key, no Zapier, no acting on events. Carly doesn’t pretend a Resy key exists either — instead it works the email and calendar seams around the book, which for reservations is where most of the guest communication actually lives:
- When a large-party or event reservation lands in your inbox, Carly drafts and sends the confirmation and puts it on the calendar with the party details.
- When a booking hits your reservation email the day before, Carly sends the guest a reminder and flags any special requests to the floor.
- When a guest no-shows on a held reservation, Carly emails a warm follow-up to try to rebook them.
- Every morning, Carly emails the front-of-house team the day’s confirmed large parties and VIP notes from the reservation emails and calendar.
And if you do work with a Resy partner integration that exposes credentials to you, Carly can use your own API key — you paste it on carlyassistant.com/integrations. Either way, Carly drafts and sends across Gmail and Outlook, updates records, and manages tasks. AI agents start at $35/month.
Claude vs Carly for Resy
| Claude | Carly | |
|---|---|---|
| Live connection to Resy OS | No (no operator API) | No direct API; works the email/calendar seams |
| Summarize guest/covers reports you paste in | Yes | Yes |
| Acts on triggers / events | No | Yes (via inbox & calendar) |
| Sends guest confirmations & reminders on its own | No | Yes |
| Keeps working when your laptop is closed | No | Yes (cloud) |
| Sends the emails itself, not just drafts | No — drafts only | Yes |
| What it takes to set up | Nothing to connect — paste exports manually | Connect your reservation inbox & calendar |
| Pricing | Claude Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude around Resy is a drafting helper on data you carry over by hand. Carly is a teammate that runs the guest communication around the book — confirmations, reminders, VIP briefs — even though Resy hands out no operator key.
Frequently Asked Questions
Does Claude work with Resy?
Not through an official connector, and not through a self-serve API either. Resy isn’t in Anthropic’s directory, ships no MCP server, and its restaurant API is partner-only — granted to approved POS and CRM vendors, not to individual restaurants. Claude can work on Resy data you paste in, but it can’t connect to your book live.
Can a restaurant self-provision a Resy API key for Claude?
No. Resy’s operator platform (Resy OS) doesn’t offer a self-serve developer key. Access to Resy’s reservation API is issued only to companies approved through its partnerships team. Note this is separate from the consumer Resy app where Amex cardholders book tables and use dining credits.
Can Claude send my guests confirmations or reminders automatically?
No. Claude’s built-in email drafts messages (in both Gmail and Outlook) but doesn’t send them, and it only works while you’re in the chat — so it can’t confirm a booking or remind a guest on its own. That automatic guest communication is what Carly is built for, working through your reservation inbox and calendar.
Is Resy’s operator platform changing in 2026?
Yes — Amex is bringing Tock’s inventory under Resy over summer 2026 and has said a unified restaurant-facing platform will arrive around 2027. So Resy’s operator tooling and partner-integration surface are actively shifting, which is one more reason not to count on a self-serve hook appearing soon.
More: Claude connectors · Claude + Toast POS · Claude + TouchBistro · Best AI tools for restaurants · Can Claude send emails · Claude vs Carly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
