Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas

Resy MCP

de chrischallversión 1.4.1i★ –iSe ejecuta en tu computadora
Nombre en el registroio.github.chrischall/resy-mcp

Instalar

Resumen

Descripción del creador (original en inglés)

Resy reservation management — search, book, cancel, favorites, and Priority Notify for Claude

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Se ejecuta en tu computadora
  • Transporte: stdio
  • Categoría: Búsqueda y memoria de IA
  • Debes completar: RESY_PASSWORD, RESY_AUTH_TOKEN

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

  • Revisiones básicas: 1 de 1 superadas
  • Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
  • Debes completar tú: RESY_EMAIL, RESY_PASSWORD, RESY_AUTH_TOKEN, RESY_DISABLE_FETCHPROXY, RESY_API_KEY, RESY_TOKEN_CACHE, RESY_TOKEN_FILE, RESY_API_KEY_FILE, RESY_CAPTURE_TIMEOUT, RESY_WS_PORT

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

Necesitas

  • npmNode.js instalado (para el comando npx)

¿Qué app usas?

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json

{
  "mcpServers": {
    "resy": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ],
      "env": {
        "RESY_EMAIL": "your-value",
        "RESY_PASSWORD": "your-value",
        "RESY_AUTH_TOKEN": "your-value",
        "RESY_DISABLE_FETCHPROXY": "your-value",
        "RESY_API_KEY": "your-value",
        "RESY_TOKEN_CACHE": "your-value",
        "RESY_TOKEN_FILE": "your-value",
        "RESY_API_KEY_FILE": "your-value",
        "RESY_CAPTURE_TIMEOUT": "your-value",
        "RESY_WS_PORT": "your-value"
      }
    }
  }
}

Ejecuta esto en tu terminal

claude mcp add resy --env RESY_EMAIL=your-value --env RESY_PASSWORD=your-value --env RESY_AUTH_TOKEN=your-value --env RESY_DISABLE_FETCHPROXY=your-value --env RESY_API_KEY=your-value --env RESY_TOKEN_CACHE=your-value --env RESY_TOKEN_FILE=your-value --env RESY_API_KEY_FILE=your-value --env RESY_CAPTURE_TIMEOUT=your-value --env RESY_WS_PORT=your-value -- npx -y resy-mcp

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "resy": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ],
      "env": {
        "RESY_EMAIL": "your-value",
        "RESY_PASSWORD": "your-value",
        "RESY_AUTH_TOKEN": "your-value",
        "RESY_DISABLE_FETCHPROXY": "your-value",
        "RESY_API_KEY": "your-value",
        "RESY_TOKEN_CACHE": "your-value",
        "RESY_TOKEN_FILE": "your-value",
        "RESY_API_KEY_FILE": "your-value",
        "RESY_CAPTURE_TIMEOUT": "your-value",
        "RESY_WS_PORT": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "resy": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ],
      "env": {
        "RESY_EMAIL": "your-value",
        "RESY_PASSWORD": "your-value",
        "RESY_AUTH_TOKEN": "your-value",
        "RESY_DISABLE_FETCHPROXY": "your-value",
        "RESY_API_KEY": "your-value",
        "RESY_TOKEN_CACHE": "your-value",
        "RESY_TOKEN_FILE": "your-value",
        "RESY_API_KEY_FILE": "your-value",
        "RESY_CAPTURE_TIMEOUT": "your-value",
        "RESY_WS_PORT": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

  • RESY_EMAIL env
    Your Resy account email. Optional — leave unset to use the ContextMint Bridge browser extension instead.
  • RESY_PASSWORD secreto env
    Your Resy account password. Optional — leave unset to use the ContextMint Bridge browser extension instead.
  • RESY_AUTH_TOKEN secreto env
    Pre-obtained x-resy-auth-token. Overrides email/password and the ContextMint Bridge path. Power users / CI only.
  • RESY_DISABLE_FETCHPROXY env
    Set to '1' to disable the fetchproxy fallback (forces RESY_EMAIL+PASSWORD or RESY_AUTH_TOKEN).
  • RESY_API_KEY env
    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 env
    Set to false to disable the on-disk token cache and re-authenticate on every process start. Defaults to enabled.
  • RESY_TOKEN_FILE env
    Absolute path for the token cache file. Defaults to $MCP_DATA_DIR/.resy-mcp/token.json.
  • RESY_API_KEY_FILE env
    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 env
    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…
  • RESY_WS_PORT env
    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 — th…

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub chrischall, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • – No aplica

    El endpoint responde

    Este se ejecuta en tu computadora; no hay endpoint en internet

  • – No aplica

    Inicio de sesión con OAuth

    Se ejecuta en tu computadora y usa ajustes locales en su lugar

  • … Aún sin revisar

    Sin instrucciones ocultas en las descripciones de herramientas

    Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet

Comparado con otros en Búsqueda y memoria de IAi

  • Más estrellas que el 0% de los otros 7277 servidores de esta categoría
  • Publicado en el registro más recientemente que el 93% de los otros 7277 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 7277 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Resy MCP?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: RESY_PASSWORD, RESY_AUTH_TOKEN

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (1.4.1) llegó al registro hace 3 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.

¿Qué puedo usar en su lugar?

En la misma categoría: Context7, Codebase Memory, Exa

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Context7

de upstash

Up-to-date docs for AI agents

Computadora o nube★ 64.224MITActualizado ayer
Instalar

Codebase Memory

de DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Se ejecuta en tu computadora★ 48.148MITActualizado hace 21 días
Instalar

Exa

de exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Se ejecuta en la nube★ 5213MITActualizado el mes pasado
Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

resy-mcp

Resy reservation management as an MCP server for Claude — search restaurants, book tables, manage reservations, favorites, and Priority Notify via natural language.

⚠️ Resy does not publish an official API. This server uses the same private endpoints the Resy web app calls, with the public web-app api_key and one of three user-level auth paths (token override, email + password, or a fetchproxy browser bridge). Use at your own discretion.

Tools

ToolPurpose
resy_get_profileCurrent user profile (name, email, booking count)
resy_search_venuesSearch venues with availability for a date + party size
resy_find_slotsList bookable slots at a venue
resy_get_venueFull venue details
resy_bookBook a reservation (composite: find → details → book)
resy_list_reservationsUpcoming / past reservations
resy_cancelCancel by resy_token
resy_list_favoritesFavorited venues
resy_add_favorite / resy_remove_favoriteManage favorites
resy_list_notifyPriority Notify subscriptions
resy_add_notify / resy_remove_notifyManage Priority Notify

Acknowledgement of Terms

By using this MCP server, you acknowledge and agree to the following:

1. This server accesses your own Resy account. Auth happens via your own credentials (email/password) or your own signed-in browser session through the ContextMint Bridge extension. It does not — and cannot — access anyone else's reservations.

2. [Resy's Terms of Service](https://resy.com/terms) govern your use of this server, just as they govern your direct use of resy.com. Resy's ToS prohibits the use of bots and automated booking, enforces rate limits, deploys CAPTCHA, and states that automated booking bots can result in account bans. Reservations are not transferable and may not be resold.

You are agreeing to those terms — read by the maintainer 2026-05-23 — every time you invoke a tool in this server.

3. Personal, non-commercial use only. This project is not affiliated with, endorsed by, sponsored by, or in partnership with Resy or American Express. It is a personal automation tool intended only to help one user manage one person's reservations from the command line. Specifically: do not use it to mass-book, snipe slot-tokens the moment they open, resell tables, or compete with Resy. The booking tools exist so you can book the table you would have booked anyway, faster.

4. Stability is not guaranteed. This server calls the same api.resy.com endpoints the Resy mobile app and web app call, with the same public web-app api_key. Resy may change endpoint shapes, rotate keys, or add new bot detection at any time. It may break.

5. You accept full responsibility for any consequences of using this server in connection with your Resy account — rate limiting, slot-lock rejections, account warnings, suspension, or bans. If Resy objects to your use, stop using this server.

This section is the maintainer's good-faith summary of the terms — it is not legal advice and does not modify or supersede Resy's actual ToS.

Install

npm install

npm run build

Configure

Pick one of three auth paths. The client tries them in this priority order:

  1. `RESY_AUTH_TOKEN` — pre-obtained x-resy-auth-token. Overrides everything; useful for CI or power users who already have a token.
  2. `RESY_EMAIL` + `RESY_PASSWORD` — the classic flow. POSTs /3/auth/password and caches the returned token.
  3. fetchproxy fallback — when no env vars are set, the server uses the fetchproxy browser bridge to call /3/auth/refresh through your signed-in resy.com tab. Install the ContextMint Bridge extension once from its releases page (unzip the Chrome build and load it unpacked at chrome://extensions; Safari isn't available yet — it will ship inside the ContextMint app, which has no public download — so use Chrome for now), sign into resy.com, and that's it — no credentials in env.

ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README points to it. Its source is public at nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the .sha256 file published beside it (shasum -a 256 -c contextmint-bridge-chrome- .zip.sha256).

Copy .env.example to .env and fill in whichever path you want:

# Path 2: password login (classic)

RESY_EMAIL=you@example.com RESY_PASSWORD=changeme

Path 1: direct token (overrides everything)

RESY_AUTH_TOKEN=...

Opt-out of the fetchproxy fallback (forces 1 or 2)

RESY_DISABLE_FETCHPROXY=1

For MCPB / Claude Desktop install, the packaged manifest prompts for all three optional inputs — leave them blank to route through ContextMint Bridge instead.

Environment

Every variable is optional.

variabledefault
RESY_AUTH_TOKENunsetAuth path 1: a pre-obtained x-resy-auth-token, used verbatim. Overrides everything.
RESY_EMAIL / RESY_PASSWORDunsetAuth path 2: password login. Only needed on a host with no browser.
RESY_DISABLE_FETCHPROXYunset1 turns off the ContextMint Bridge path (path 3).
RESY_TOKEN_CACHEonfalse disables the on-disk token cache. A bridge-minted token is cached for at most 24 hours.
RESY_TOKEN_FILE$MCP_DATA_DIR/.resy-mcp/token.jsonToken cache path.
RESY_API_KEYcapturedPins the web-app api key, beating the key captured from your tab and the built-in default. Rotation is handled without it.
RESY_API_KEY_FILE$MCP_DATA_DIR/.resy-mcp/api-key.jsonApi-key cache path (stores the bare key only).
RESY_CAPTURE_TIMEOUT30Seconds to wait for your tab to make an API call the bridge can read the token from.
RESY_WS_PORT37149Bridge concentrator port. Every fetchproxy MCP on one machine shares it, so move it for all of them or none (local dev, tests, or a hosted registration's bridge port).

Confirmations

resy_book and resy_cancel ask you to confirm before they change anything. A client that can show a confirmation prompt (Claude Code) shows one, unless MCP_CONFIRM_ELICITATION=off. On a client that cannot, the first call returns a preview and a confirmToken, and only a repeat call with that token goes ahead:

variabledefault
MCP_CONFIRM_MODEask-userWhat a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). ask-user: two steps — the first call does nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. auto: the same two steps, but the model may use the token after reviewing the preview itself. refuse: writes are refused on such clients. A client that can show prompts (Claude Code) always gets the real prompt, unless MCP_CONFIRM_ELICITATION=off. An unrecognised value is treated as refuse.
MCP_CONFIRM_ELICITATIONonoff never shows a confirmation prompt, so every client gets the MCP_CONFIRM_MODE path. Set it for a client that claims to support prompts but never shows one (the write hangs — opencode 2.0.x). Any other value stays on, with a warning on stderr.
MCP_CONFIRM_TTL_SECONDS600How long a token stays valid.
MCP_CONFIRM_SECRETrandom per processSigning key; set it only if tokens must survive a server restart. On mcp-host the host supplies a stable per-child key (MCP_HOST_CONFIRM_SECRET) and spent tokens are recorded under MCP_DATA_DIR, so an approval survives an idle restart.

resy_book additionally books only the exact slot a preview showed. On a client without prompts the preview itself carries the confirmToken, bound to that slot's time, seating type and terms; once you approve, the model repeats the call with the preview's time as desired_time plus the token. On a client with prompts the call must name the slot (desired_time + slot_type + terms_token) before you are asked. If the slot or its terms changed in between, nothing is booked and a fresh preview is returned.

Run (local stdio)

node dist/bundle.js

Test

npm test             # tsc typecheck + unit tests (mocked fetch)

npm run smoke # live endpoint probe — requires real .env

Notes

  • The api key is the public one baked into resy.com's JS bundle. It is captured from your signed-in tab and cached, so a rotation is picked up on its own — RESY_API_KEY pins a specific key instead, and is only needed when you want to override that.
  • Favorites and Priority Notify endpoint paths are reverse-engineered; if live endpoints differ, run npm run smoke and adjust.

This project was developed and is maintained by AI (Claude Opus 4.7).

Pregunta a PopNx