AgentHubAgentHub

resy MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.chrischall/resy-mcp · v1.3.0

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

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

Resy reservation management — search, book, cancel, favorites, and Priority Notify for Claude resy-mcp is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-04
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

secret
secret
Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.
Click to copy snippet
{
  "mcpServers": {
    "resy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ]
    }
  }
}

Setup tutorial

  1. Open the resy-mcp page and confirm this MCP Server (source: MCP Registry).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

  1. Install Claude Code CLI
  2. Copy the command below, replace <placeholders> with real env values, then run in terminal
  3. See Environment variables below if listed
claude mcp add resy-mcp -- npx -y resy-mcp

Cursor — .cursor/mcp.json (local)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
{
  "mcpServers": {
    "resy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ]
    }
  }
}

VS Code — .vscode/mcp.json (local)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Replace <placeholders> in env with real secrets
  5. Save and Developer: Reload Window
{
  "mcpServers": {
    "resy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ]
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

  1. Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
  2. Click Copy config and merge under mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "resy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ]
    }
  }
}

Trae — .trae/mcp.json (local)

  1. Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Save and reload Trae
{
  "mcpServers": {
    "resy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ]
    }
  }
}

Cherry Studio — MCP settings (local)

  1. Cherry Studio → Settings → MCP Servers → Add (STDIO)
  2. Or import JSON: click Copy config and merge mcpServers
  3. Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
  4. Enable the server and check tools load
{
  "mcpServers": {
    "resy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ]
    }
  }
}

Tongyi Lingma — MCP config (local)

  1. Lingma Settings → MCP → + → STDIO or config file
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
  4. Confirm connected before using tools in agent chat
{
  "mcpServers": {
    "resy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ]
    }
  }
}

Windsurf — mcp_config.json (local)

  1. Edit ~/.codeium/windsurf/mcp_config.json
  2. Click Copy config and merge mcpServers (stdio same as Cursor)
  3. Replace <placeholders> in env, save, refresh Cascade
{
  "mcpServers": {
    "resy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ]
    }
  }
}

Cline — MCP Servers (local)

  1. Cline panel → Settings → MCP Servers
  2. Click Copy config and merge
  3. Replace <placeholders> in env, then save
{
  "mcpServers": {
    "resy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ]
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

  1. Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
  2. Or Plugins → MCP Servers → Configure MCP and paste the JSON below
  3. Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
  4. Save, restart WorkBuddy, confirm connector status is green
{
  "mcpServers": {
    "resy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resy-mcp"
      ]
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for resy-mcp

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for resy-mcp?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

resy-mcp requires environment variables (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). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet
// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "API_KEY": "your_actual_key_here"
  }
}

Tool Mock Playground

Sandbox

resy-mcp Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: resy_mcpExecute the core tool interface of resy-mcp
Request ArgumentsJSON Schema
{
  "target": "resy-mcp",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

resy-mcp + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: resy-mcp
HTML
<a href="https://myagenthub.cn/p/io.github.chrischall/resy-mcp" title="Listed on AgentHub: resy-mcp" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.chrischall/resy-mcp?lang=en" alt="Listed on AgentHub: resy-mcp" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: resy-mcp](https://myagenthub.cn/badge/io.github.chrischall/resy-mcp?lang=en)](https://myagenthub.cn/p/io.github.chrischall/resy-mcp)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.chrischall/resy-mcp",
  "type": "mcp-server",
  "version": "1.3.0",
  "displayName": "resy-mcp",
  "description": "Resy reservation management — search, book, cancel, favorites, and Priority Notify for Claude",
  "repository": {
    "url": "https://github.com/chrischall/resy-mcp",
    "source": "github"
  },
  "distribution": {
    "packages": [
      {
        "registryType": "npm",
        "identifier": "resy-mcp",
        "version": "1.3.0",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "RESY_EMAIL",
            "description": "Your Resy account email. Optional — leave unset to use the ContextMint Bridge browser extension instead."
          },
          {
            "name": "RESY_PASSWORD",
            "description": "Your Resy account password. Optional — leave unset to use the ContextMint Bridge browser extension instead.",
            "isSecret": true
          },
          {
            "name": "RESY_AUTH_TOKEN",
            "description": "Pre-obtained x-resy-auth-token. Overrides email/password and the ContextMint Bridge path. Power users / CI only.",
            "isSecret": true
          },
          {
            "name": "RESY_DISABLE_FETCHPROXY",
            "description": "Set to '1' to disable the fetchproxy fallback (forces RESY_EMAIL+PASSWORD or RESY_AUTH_TOKEN)."
          },
          {
            "name": "RESY_API_KEY",
            "description": "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."
          },
          {
            "name": "RESY_TOKEN_CACHE",
            "description": "Set to false to disable the on-disk token cache and re-authenticate on every process start. Defaults to enabled."
          },
          {
            "name": "RESY_TOKEN_FILE",
            "description": "Absolute path for the token cache file. Defaults to $MCP_DATA_DIR/.resy-mcp/token.json."
          },
          {
            "name": "RESY_API_KEY_FILE",
            "description": "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."
          },
          {
            "name": "RESY_CAPTURE_TIMEOUT",
            "description": "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."
          },
          {
            "name": "RESY_WS_PORT",
            "description": "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."
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.chrischall/resy-mcp",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.chrischall%2Fresy-mcp/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}