Opentable Mcp

Manage OpenTable reservations via MCP — search restaurants, check slot availability, book tables, list/cancel reservations, and manage favorites. Triggers on...

This package does what it says — it bridges a local MCP process to your signed-in OpenTable tab using a side-loaded Chrome extension. Before installing or running it: - Review the extension code (extension/*.js) yourself (or with someone you trust). The extension injects content scripts into opentable.com and relays request/response bodies to the local MCP server; that is necessary but means page data and cookies are accessible to the local process. - Do NOT run the probe scripts (scripts/probe-book-cancel.ts, scripts/probe-book-cc-cancel.ts) unless you knowingly want to create and cancel real reservations on your account. They will interact with OpenTable write endpoints. - The repo's docs include instructions to capture raw XHR output (window.__otMcpCaptures) and even to paste it into chat for persisted-query extraction; do not paste raw capture JSON into any chat or public place because it can include CSRF tokens, request bodies, or personal/profile data. Redact or inspect captures locally and only share the minimal fields needed (e.g., persisted-query hashes) with redaction. - Prefer running the MCP server and extension in a disposable browser profile if you want to test (create a separate Chrome profile for the extension and OpenTable sign-in). - Check the npm package and the GitHub repo owner/commit history if you plan to install via npx. If you clone and build, inspect package.json scripts and background.js for any network endpoints beyond 127.0.0.1 or github/npm. If you trust the author and understand the above risks, the package is coherent for its purpose. If you are unsure, avoid running probes that perform writes and avoid pasting capture logs into any external chat or service.