BondSeat MCP server

BondSeat connector

Snag hard-to-get tables on Resy. BondSeat watches for cancellations or tries to book right when reservations open, then automatically books a table that matches your preferences.

BondSeat carefully manages your credentials and paces availability checks, keeping routine monitoring separate from your personal Resy account.

The agent uses booking tools. The connector keeps the access token, setup codes, retry identifiers and polling state private. The diner only opens a setup link. No token needs to be copied into chat or remembered by the agent.

This is an MCP server using the official TypeScript SDK and local stdio transport. It works with clients that can launch a local MCP process. It is not a hosted HTTP MCP endpoint. The underlying REST API also remains available to custom runtimes.

Install

Requires Node.js 22 or newer. Configure an MCP client that supports local stdio:

{
  "mcpServers": {
    "bondseat": {
      "command": "npx",
      "args": ["--yes", "@bondseat/mcp@0.1.2"]
    }
  }
}

The default connects to the production BondSeat API. There is no API key to copy: when setup is needed, the diner opens a link to connect Resy and authorize the $10 USD success fee. Unsuccessful requests incur no fee. The account-free flow supports Resy; the diner needs a saved card in Resy for restaurant charges and separately authorizes BondSeat's fee through Stripe.

The executable starts MCP when called without arguments. A CLI is also available:

npx --yes @bondseat/mcp@0.1.2 --help
npx --yes @bondseat/mcp@0.1.2 schema request
npx --yes @bondseat/mcp@0.1.2 restaurants <<'BONDSEAT_INPUT'
{"q":"La Vara","city":"Brooklyn"}
BONDSEAT_INPUT

Commands: restaurants, request, status, requests, stop, resume, connect. Pass JSON through stdin. schema prints the MCP tool's input schema without contacting the API. CLI exits: 0 for a result (including pending setup), 1 for an action-required result or runtime error, 2 for invalid input. Read JSON results even on exit 1. Diagnostics never include raw inputs or stored credentials.

The BondSeat skill provides the workflow for OpenClaw and other skill-capable agents. It can use either connected MCP tools or the CLI. Installing the skill does not by itself configure an MCP connection.

Runtime configuration

A multi-user host must isolate each diner's state. The same file must remain available to subsequent CLI calls and scheduled follow-ups. If a client executes in a sandbox, configure Node, network access and persistent storage there.

For QA development, explicitly configure both variables:

{
  "BONDSEAT_API_URL": "https://31clusup32.execute-api.us-east-1.amazonaws.com/agent/v1",
  "BONDSEAT_STATE_FILE": "/absolute/private/path/bondseat/qa.json"
}

Local source development can launch node server.mjs or node cli.mjs from this package after installing dependencies. Remote-only clients need a hosted adapter; this package does not expose an HTTP MCP endpoint.

Agent workflow

Shortened. The full README is on GitHub.