AI agents

Use SeatSwiper from Claude

Connect your AI assistant to your SeatSwiper account and book hard-to-get reservations by chatting. Works with Claude, ChatGPT, and any assistant that supports MCP connectors.

What it does

The connector gives your assistant the same booking abilities as the SeatSwiper dashboard, on your account and with the same safeguards: it can find restaurants, tell you when a date releases, set up a drop race or a cancellation watch, and report results. It races the moment a venue releases its tables across Resy, SevenRooms, and OpenTable — no tab-refreshing at midnight.

Things you can ask once connected:

“Get me a table for 2 at Don Angie the moment reservations open.”
“When do reservations for 4 Charles Prime Rib drop, and can you race the next one?”
“Watch Semma for cancellations this Saturday, party of 4.”
“What’s my SeatSwiper setup missing before I can book?”
“List my bookings and cancel the Tatiana one.”

How to connect

From your dashboard (easiest). Sign in at seatswiper.com/dashboard, open the AI agents card, and click Add to Claude. Review the pre-filled connector and confirm.
Manually, in Claude. Settings → Connectors → Add custom connector → paste https://www.seatswiper.com/api/mcp → Add → Connect. (In ChatGPT: Settings → Connectors → Advanced → Developer mode → Add.)
Approve access. Your browser opens a SeatSwiper consent page — sign in if asked, review what the assistant will be able to do, and click Allow. You can disconnect at any time (see below).

First time here? You’ll also want the usual SeatSwiper setup — a payment card on file plus the reservation platform for your venue connected. Ask the assistant to check your account setup and it will tell you exactly what’s missing.

What the assistant can do

Check account setup. Which prerequisites (card, Resy / OpenTable / SevenRooms links) are missing, free bookings remaining, and your active-booking count.
Search restaurants. Find a venue by name across Resy, SevenRooms, and OpenTable.
Check when reservations release. When a date "drops" for a venue, and whether SeatSwiper would race the drop or watch for a cancellation.
Check live availability. Open tables on an already-released date.
Create a booking. Set up and arm a drop race or cancellation watch — always after confirming the details and the fee with you.
Arm a draft booking. Arm a saved draft once you have fixed a setup issue (for example, added a card).
List bookings. Your bookings with their state and latest result.
List saved Resy cards. The cards on your Resy account, so a booking can charge a specific one.
Cancel a booking. Cancel by booking id.

Fees and safeguards

Same fees as the dashboard, never more. A drop race costs $5 only when SeatSwiper lands your table (nothing on a miss); a cancellation watch costs $1 to start plus the $5 on success. Your first successful booking’s $5 is free.
Nothing books without your say-so. The booking tool refuses to run until the assistant has confirmed the venue, date, party size, time window, and the fee with you.
Every safeguard still applies. The connector uses the exact same booking engine as the dashboard — card required before arming, the 5-watch limit, and all platform checks.
Your credentials stay ours to guard. The assistant never sees your Resy/OpenTable/SevenRooms tokens or your card number — it only gets an access token to your SeatSwiper account, which we store as a one-way hash. We never receive or store your conversations with the assistant.

Disconnecting

Remove the connector in your assistant’s settings, or from the SeatSwiper dashboard’s AI agents card — the dashboard’s Disconnect cuts off that assistant’s access immediately. Reconnecting always takes a fresh consent.

Troubleshooting

The connect flow fails or loops. Sign in to SeatSwiper first at seatswiper.com/signin, then retry the connection. If it still fails, wait a minute and try again.
A tool reports a setup problem. Messages like “no payment card on file” or “Resy account not connected” are fixed on your dashboard; the draft booking is saved, and the assistant can arm it once you’ve fixed the issue.
Use the www address. If you paste the connector URL manually, use https://www.seatswiper.com/api/mcp exactly — including the www.
Anything else — email support@seatswiper.com and we’ll dig in.

Booking success is never guaranteed. Races run at the drop against everyone else trying for the same tables. What the connector guarantees is the same split-second attempt the dashboard makes — and no fee when we miss.

See also our Privacy Policy and Terms of Service.