opentable

opentable-mcp

MCP server for OpenTable — natural-language restaurant reservation management. Every request is relayed through the user's signed-in browser tab via the ContextMint Bridge extension, so there's no cookie paste, no bot-wall dance, and no password handling.

• npm: npmjs.com/package/opentable-mcp
• Source: github.com/chrischall/opentable-mcp

OpenTable does not publish an official API. This server calls the same endpoints the opentable.com web app uses. Auth lives in the user's browser (OpenTable's passwordless email-OTP session). Use at your own discretion.

Setup

The MCP server is half of the picture — the other half is the ContextMint Bridge browser extension that actually talks to OpenTable from your signed-in tab. Both are required.

1. Install the MCP server

Option A — npx (recommended)

Add to .mcp.json in your project or ~/.claude/mcp.json:

{
  "mcpServers": {
    "opentable": {
      "command": "npx",
      "args": ["-y", "opentable-mcp"]
    }
  }
}

Option B — from source

git clone https://github.com/chrischall/opentable-mcp
cd opentable-mcp
npm install && npm run build

Then add to .mcp.json:

{
  "mcpServers": {
    "opentable": {
      "command": "node",
      "args": ["/path/to/opentable-mcp/dist/bundle.js"]
    }
  }
}

2. Install ContextMint Bridge

opentable-mcp shares a single browser extension, ContextMint Bridge, with every other fetchproxy-based MCP. Install it once from its releases page:

ContextMint Bridge is the fetchproxy browser extension renamed, same maintainer (fetchproxy's README points to it); its source is public at https://github.com/nullnet-app/contextmint-bridge — build it yourself or verify a release zip with shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256.