6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Resy
Check live restaurant reservation availability from an AI agent.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
What the Resy connector does
The Resy MCP server connects Resy — American Express's restaurant reservation platform — to Claude, ChatGPT and any MCP-compatible agent. It retrieves live availability for a named restaurant, date and party size, then links you out to the Resy app or website to finish booking. It reads open tables. It does not take them.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Resy tools (1)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Anthropic's directory publishes no tool names for this server. The
tool_namesarray is empty. There is no second enumeration to diff Resy's documentation against, so we cannot report a clean listing — only that nothing exists to check it with. This is the weakest evidence case on this catalogue, and it is weaker than DevRev's, where at least the directory supplied 14 names. - The one documented tool has no known wire name. Resy publishes a prose label. Any programmatic identifier would be a guess, and we have not made one.
- We could not read tool schemas or safety annotations. The endpoint returned 401 on 2026-08-23, so no parameter-level detail, tool count, or annotation is published here.
- The single scope names no verb.
600003928_DINING_RESY_MCP_APPSis an entitlement ID for an application. It cannot separate reading availability from any other operation the dining server might implement, and it offers no consent-time choice. - It cannot book, and availability is not a hold. Open slots reflect a moment. Resy warns inventory changes quickly, and a reservation is confirmed only after you finish the flow on Resy's app or website and receive an email.
- US-based users only at initial launch, per Resy's documentation. Coverage outside the US, and in US areas without participating venues, may be empty.
- Amex publishes no data inventory for this connector. Resy asserts that no sensitive personal data is shared with Claude, but that is a vendor statement in a two-page PDF, not an audit. We found no document describing what the Amex gateway logs or retains.
- The vendor's entire documentation is two pages. The nominated documentation URL is a PDF last modified 2026-05-08. There is no developer reference, no tool schema, and no changelog, so a future change to the surface would be invisible from outside.
- Resy's own website could not be used as a source.
resy.comreturns HTTP 200 with the same Angular shell for every path — including paths that do not exist — so its help and privacy pages yielded no readable text and no status there is meaningful.
Frequently asked questions
Can the Resy connector actually book a restaurant reservation?
No. Resy's documentation states the connector checks availability and then takes you to the Resy mobile app or website to complete your booking. Its troubleshooting section calls being redirected out of Claude expected behavior, and warns that if you exit the journey early the reservation is not confirmed. The agent reads open tables; a human finishes the booking.
Does the Resy MCP server touch my American Express card or account data?
Nothing we found indicates it does. The endpoint sits on an Amex API gateway, but its single OAuth scope is a dining entitlement and Resy states no sensitive personal data is shared with Claude. Amex publishes no data inventory for this connector, so treat card isolation as undocumented rather than as an audited guarantee.
How many tools does the Resy MCP server have?
Anthropic's directory lists zero tool names, and Resy's documentation describes exactly one: a Restaurant Availability tool returning time slots for a date and party size. One is therefore a documented floor with no independent list to check it against. The endpoint requires authentication, so we could not enumerate the real surface ourselves.
Do I need to sign in to Resy to connect it to Claude?
Not during setup. Resy's documentation states you do not need to sign into Resy when you add the connector, and that sign-in happens later when you book. Because booking happens on Resy's own site or app, that sign-in occurs outside Claude entirely, in Resy's environment rather than through the connector.
Will an AI agent using Resy commit me to a cancellation fee?
Not on its own, because it cannot complete a booking. Many Resy restaurants charge for cancellations and no-shows, but the connector stops at availability and links out, so a human passes through Resy's own confirmation screens. The financial commitment is made in Resy's app, not by the agent.
Why does Claude show no Resy availability for my area?
Most likely geography or inventory. Resy states the initial launch supports US-based users only, and that there may not be Resy venues in your area with availability. Its documentation also asks you to include a date, a time or time range, and a party size, and notes inventory can change quickly between queries.
What OAuth permissions does the Resy MCP server request?
One scope, named 600003928_DINING_RESY_MCP_APPS. Both the server's RFC 9728 descriptor and its authorization server metadata advertise that single value, verified on 2026-08-23. It is an Amex entitlement identifier naming an application rather than a verb, so it grants whatever the dining server implements and separates no operation from another.
Is the Resy connector read-only?
Anthropic's directory labels its permissions Read Only, and Resy's documentation describes only availability retrieval. Uniquely among 1,897 directory entries, Resy also ships an allowed_link_domains allow-list of four Resy domains, which constrains where the connector may send you. We could not verify the tool surface directly because the endpoint requires authentication.
Sources
- Resy MCP App guide for Claude (PDF, 2 pages, last modified 2026-05-08) (retrieved 2026-08-23). The documentation URL Anthropic's directory nominates for this connector, and the only enumeration of its tools. · retrieved 2026-05-08
- Live authentication check — an anonymous initialize request to
https://apigw.americanexpress.com/dining/v1/mcpreturned HTTP 401 with awww-authenticateBearer challenge naming its own resource metadata document (2026-08-23) · retrieved 2026-08-23 - RFC 9728 protected-resource metadata (retrieved 2026-08-23). Declares one scope; three sibling well-known paths returned 404, confirming the 200 is genuine rather than a catch-all. · retrieved 2026-08-23
- Authorization server metadata (retrieved 2026-08-23). Advertises the same single scope, delegating authorization to
resygateway.americanexpress.com. · retrieved 2026-08-23 - American Express robots.txt (retrieved 2026-08-23). Permits the documentation path; carries no
Content-Signaldirective. · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Resy help — · Privacy (both returned an Angular application shell rather than readable content on 2026-08-23) · retrieved 2026-08-23
More Productivity connectors
Adobe Experience Manager
Create, edit, publish and delete AEM pages, content fragments and assets from an agent.
Adobe Workfront
Find, create, update and delete Workfront work items from an AI agent.
Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.
Use it in an agent
Put Resy to work.
Connect Resy once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.