Resy-mcp Server

Resy-mcp is an MCP integration. Resy reservation management — search, book, cancel, favorites, and Priority Notify for Claude.

Packages and local setup

The published npm package is resy-mcp, version 1.3.2. Its declared MCP transport is stdio.

The package declares RESY_EMAIL: Your Resy account email. Optional — leave unset to use the ContextMint Bridge browser extension instead.; RESY_PASSWORD: Your Resy account password. Optional — leave unset to use the ContextMint Bridge browser extension instead.; RESY_AUTH_TOKEN: Pre-obtained x-resy-auth-token. Overrides email/password and the ContextMint Bridge path. Power users / CI only.; RESY_DISABLE_FETCHPROXY: Set to '1' to disable the fetchproxy fallback (forces RESY_EMAIL+PASSWORD or RESY_AUTH_TOKEN).; RESY_API_KEY: Pin the api key, beating both the key captured from the live site and the compiled-in default. Rotation does not require it: the key is captured and cached automatically.; RESY_TOKEN_CACHE: Set to false to disable the on-disk token cache and re-authenticate on every process start. Defaults to enabled.; RESY_TOKEN_FILE: Absolute path for the token cache file. Defaults to $MCP_DATA_DIR/.resy-mcp/token.json.; RESY_API_KEY_FILE: Absolute path for the api-key cache file. Defaults to $MCP_DATA_DIR/.resy-mcp/api-key.json. Holds the bare key captured from the live site, which takes precedence over the compiled-in default.; RESY_CAPTURE_TIMEOUT: Seconds to wait for the signed-in page to make an API call the bridge can read the auth token from. Defaults to 30. Capture resolves on the next matching request, so an idle tab needs a longer window than a busy one.; RESY_WS_PORT: Port for the fetchproxy bridge. The whole fleet shares 37149 (the ContextMint Bridge extension dials it), so override only for local development, test isolation, or a hosted bridged registration — this is the variable to name in the registration's bridgePortEnv..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 1.3.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.