Hosted MCP server/Other Official

Official Resy MCP server

Hosted at apigw.americanexpress.com·Streamable HTTP

Resy helps users find and book restaurants. Its connector brings restaurant availability, dining preferences, and booking context into an assistant for planning meals and comparing options. The provider page states that sign-in is required. The MCP connection itself was not tested here, so treat the tool list as unpublished until you connect.

apigw.americanexpress.com Streamable HTTP Required (sign-in) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Diners who need restaurant availability and booking context inside an assistant for meal planning and comparing options.

  • Find restaurant availability for a meal.
  • Compare dining options before booking.
  • Book a restaurant through the assistant.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Resy as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http resy https://apigw.americanexpress.com/dining/v1/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://apigw.americanexpress.com/dining/v1/mcp
Host
apigw.americanexpress.com · /dining/v1/mcp
Transport
Streamable HTTP
Authentication
Required (sign-in)
Server name
resy
Listing type
Official provider listing

The installer uses the server name resy. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that resy appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Find restaurant availability for a meal. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Resy documentationhttps://claude.com/connectors/resy