Opentable MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add opentable-mcp -- npx -y opentable-mcp

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

[mcp_servers.opentable-mcp]
command = "npx"
args = ["-y", "opentable-mcp"]

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

{
  "servers": {
    "opentable-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "opentable-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: OT_BRIDGE (Which browser transport to use: "websocket" (default, the fetchproxy bridge) or "mcp-chrome"), OT_MCP_CHROME_URL (URL of the mcp-chrome bridge (default http://127.0.0.1:12306/mcp). Only used when OT_BRIDGE=mcp-chrome), OT_WS_PORT (Overrides the fetchproxy WebSocket port (default 37149, the fleet-shared port)), FETCHPROXY_WS_HOST (Bridge bind interface, a literal IP only (anything else is ignored); default 127.0.0.1. Keep on loopback — it exists for a hosted child in its own network namespace), FETCHPROXY_IDENTITY_DIR (Where to store the long-term bridge identity keypair, an absolute path only (anything else is ignored); default ~/.fetchproxy/identity/. Exists for a host that runs a separate child per caller).