io.github.chrischallPublished by GitHub account chrischallv1.4.1Updated Nov 7, 2026
OpenTable reservation management: find slots, book, cancel, list reservations, manage favorites.
Manages OpenTable reservations through your signed-in Chrome tab: search restaurants, check slots, book, modify, cancel and manage favorites.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
OpenTable reservation manager as an MCP server for Claude — find slots, book, cancel, manage favorites, and read your dashboard via natural language.
v0.3.0-alpha status: Chrome-extension bridge, 10 tools, read + write. Every OpenTable request is relayed through your signed-in Chrome tab over a localhost WebSocket — each request rides your existing session and reaches OpenTable as if you'd clicked it yourself.
OpenTable's edge (Akamai Bot Manager) enforces a behavioral challenge on /, /s, /r/…, /dapi/…, and /booking/…. Tooling that builds its own HTTP client — cycletls, impersonated curl, headless Chrome — invents a separate identity and gets a 403 or JS interstitial. opentable-mcp does the opposite: it uses your own browser session as-is, with the cookies and TLS context it already has.
So instead of standing in for the browser, this MCP server:
127.0.0.1:37149 via @fetchproxy/server.fetch(..., { credentials: 'include' }) — your TLS, your cookies, your already-solved _abck./user/*) into tool-shaped output.No cookie-pasting. No cycletls. No Playwright. Just your own browser, acting on its own behalf — the MCP server only picks what to ask for.
opentable_get_menu accepts the same restaurant ID, slug, path, or exact URL
as opentable_get_restaurant. Omit menu_name to return all published menus,
or pass an exact title such as "Dinner" (case-insensitive) to select one:
The response includes restaurant identity and source url, available_menus,
menus, and an optional external menu_url. Each published menu retains
OpenTable's sections/items, price strings, variationGroups, currency,
provider, and updated timestamp. view defaults to compact (media URLs
removed); full retains media URLs too. Published prices may differ from the
restaurant's current menu, so keep the source and update timestamp when quoting.
Large menus come back as pages of whole items, so a reply never stops halfway
through a dish. Without paging arguments a menu that fits is returned as-is;
a larger one returns its first page. Each page carries available_sections and
pagination:
To continue, call again with offset set to next_offset and the same
menu_name/section_name; next_offset is null on the last page. Optional
paging inputs:
section_name — an exact section title (case-insensitive); the reply adds
section_found.offset — the item to start from (default 0).limit — at most this many items per page (1–50, default 20). A page may
return fewer to stay within the response budget.view: "full" with no paging inputs returns the whole menu uncapped, for
clients without an output limit. A single item too large for a page is an
error, never a truncated description.
status distinguishes available, menu_not_found (check available_menus),
external_only, and not_available. An absent menu is not an HTTP/bridge or
parsing error: those failures remain errors. External links are returned
without fetching other hosts or parsing PDFs. This tool only reads the same
restaurant page through the existing browser bridge; it never holds a table.
By using this MCP server, you acknowledge and agree to the following:
1. This server accesses your own OpenTable account. Every request is dispatched through your own signed-in browser tab via the ContextMint Bridge browser extension (or hangwin/mcp-chrome). It does not — and cannot — access anyone else's reservations.
2. OpenTable's Terms of Use govern your use of this server, just as they govern your direct use of opentable.com. The clauses most relevant here:
You may not use any deep-link, robot, spider, scraper, generative AI or other AI technology including, but not limited to, those that operate by interacting with or otherwise making use of your browser, such as automated assistants or other automatic or manual device, process, or means to access, copy, search, or monitor any portion of the Services or OpenTable Content, except as expressly authorized by OpenTable.
And, critically: "Actions of AI agents are acknowledged as actions of the User that is using them, and the User is responsible for checking and verifying the action…"
You are agreeing to those terms — read by the maintainer 2026-05-23 — every time you invoke a tool in this server. OpenTable's ToU explicitly enumerates AI/automated-assistant access among the things they have not authorized; they also explicitly impute AI-agent actions back to you.
3. Personal, non-commercial use only. This project is not affiliated with, endorsed by, sponsored by, or in partnership with OpenTable, Inc. It is a personal automation tool that drives the same /dapi/... and /booking/... endpoints opentable.com uses. Do not use it to mass-book, sweep CC-required tables, resell reservations, or for any commercial purpose. The book/cancel/modify tools exist so you can manage one reservation as if you were sitting at your browser.
4. Stability is not guaranteed. This server depends on internal OpenTable persisted-GraphQL query hashes that OpenTable rotates between deployments. When they rotate, tools break and we re-capture them. Your own use is at the mercy of OpenTable's release cadence.
5. You accept full responsibility for any consequences of using this server in connection with your OpenTable account — rate limiting, slot-lock rejections, no-show penalties for runaway bookings, account warnings, suspension, or any enforcement action. Per OpenTable's ToU, the AI agent's actions are your actions — review every book/cancel before you confirm. If OpenTable objects to your use, stop using this server.
This section is the maintainer's good-faith summary of the terms — it is not legal advice and does not modify or supersede OpenTable's actual ToU.
opentable-mcp shares one browser extension, ContextMint Bridge, with every other fetchproxy-based MCP. Install it once from https://github.com/nullnet-app/contextmint-bridge/releases:
ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README (https://github.com/chrischall/fetchproxy#extension) points to it. Its source is public at https://github.com/nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the .sha256 file published beside it (shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256).
chrome://extensions → Developer mode → Load unpacked). Safari isn't available yet — it will ship inside the ContextMint app, which has no public download — so use Chrome for now.https://www.opentable.com/ in that same browser profile.After that, any MCP client that launches node dist/bundle.js will reach OpenTable through your signed-in tab.
Full setup + troubleshooting guide: see the ContextMint Bridge repo for the status-dot reference, WS protocol, and request lifecycle. Persisted-query hash capture for OpenTable redeploys is documented in CLAUDE.md here.
No env vars required by default — auth lives in the browser, not the MCP process.
If you've installed hangwin/mcp-chrome for browser automation, opentable-mcp can route its OpenTable fetches through it instead of ContextMint Bridge:
In that mode you don't need ContextMint Bridge. Every OpenTable request becomes a chrome_network_request call against your existing mcp-chrome install, pinned via tabUrl to an opentable.com tab.
This mode is read-only. Booking, modifying, cancelling and favorites are refused with a clear error — OpenTable's write endpoints need a CSRF token from a restaurant/booking/account page, which this transport can't supply — and opentable_find_slots is unavailable. Use the default ContextMint Bridge transport for those.
Note: this path requires mcp-chrome ≥ the release containing PR #348 (tabUrl parameter on chrome_network_request). Pre-#348 mcp-chrome versions are active-tab-only and will misbehave for cross-origin fetches. Live-verification of this path is pending the upstream merge.
Other env vars: OT_WS_PORT (default 37149) overrides the fetchproxy WebSocket port; OT_MCP_CHROME_URL (default http://127.0.0.1:12306/mcp) overrides the mcp-chrome endpoint.
opentable_book, opentable_modify and opentable_cancel ask you before they act. A client that can show a confirmation prompt (Claude Code) shows one. On a client that cannot (claude.ai, Claude Desktop), the first call books, changes or cancels nothing: it returns a preview of exactly what would happen plus a confirmToken. Either way the prompt names the restaurant, date, time and party size, and for a booking or change the card that will be held and the cancellation policy (carried in the booking_token / modify_token from the preview tools; a cancel looks the reservation up on your dining dashboard and warns if it isn't there). Only a repeat call with the same arguments and that token proceeds, once — change any argument in between and it is refused (DRAFT_CHANGED) with a fresh preview.
The scripts/probe-*.ts files spin up the MCP server, call one or two tools through the extension bridge, and print the response. They require the extension to be loaded and an opentable tab to be open.
incomplete_page, distinct from parse_error (a full-size page whose format changed). Refresh the restaurant's page in the signed-in bridged browser, let it finish loading, then retry once.find_slots fails with HTTP 409. The browser's OpenTable session needs refreshing. Open the restaurant's page in the signed-in bridged tab and let its availability load, then retry once. The error says availability is unverified, not empty, and a passing bridge healthcheck does not test it.list_favorites doesn't reflect a fresh add_favorite. The /user/favorites SSR page is cached for a few seconds. Re-list after ~10 s or verify via opentable_get_profile's count.src/transport-fetchproxy.ts — FetchproxyTransport: thin adapter over @fetchproxy/server's FetchproxyServer, the shared WebSocket bridge that talks to the ContextMint Bridge browser extension.src/client.ts — OpenTableClient: wraps the transport with fetchJson / fetchHtml + error-mapping.src/tools/*.ts — one file per concern (reservations / restaurants / favorites / user / search). Each exports registerXxxTools(server, client).src/parse-*.ts — pure HTML/JSON parsers, fully unit-tested.tests/ — 1:1 mirror of src/, vitest. WS-protocol-level tests live upstream in the fetchproxy repo.scripts/probe-*.ts — live round-trip probes (require ContextMint Bridge + sign-in).extensions.persistedQuery.sha256Hash with hashes captured from opentable.com. If OpenTable re-deploys, the server returns PersistedQueryNotFound; see CLAUDE.md → "Hot spots" for the re-capture procedure.dining_area_id is a required book arg. We can't auto-resolve rooms, so pass the restaurant's slug or numeric id to opentable_get_restaurant (slugs route to /r/{slug}, numeric ids to /restaurant/profile/{id}), read diningAreas[], and feed the id into opentable_book.This project was developed and is maintained by AI (Claude Opus 4.7).
Source: README.md at commit 09ad1e2
List the authenticated user's OpenTable reservations. Defaults to upcoming; pass scope="past" or scope="all" to broaden. Each entry includes the security_token needed to cancel or modify.
viewscopeend_datestart_dateList available reservation slots at a specific OpenTable restaurant for a date + party size. Returns each slot's reservation_token (use it with opentable_book — tokens expire quickly, book promptly). Slots may be attributes=['default'|'bar'|'highTop'|'outdoor'] and type=Standard|Experience|POP. You can pass a slot's reservation_token + slot_hash straight to opentable_book without a separate opentable_get_restaurant call — book auto-resolves the dining area. (OpenTable's availability response carries only the seating category, not the numeric dining-area id, so that id is resolved at book time from the booking-details page.) If this errors with "operation ... not yet observed on this tab", open any OpenTable restaurant page in your browser once (the graphql bridge needs to see the page's own availability query fire first), then retry.
daterequiredtimerequiredviewparty_sizerequiredrestaurant_idrequireddatabase_regionPreview an OpenTable booking BEFORE committing. Fetches the /booking/details SSR page and the slot-lock to surface: the cancellation policy (including any credit-card no-show fee), the saved payment card that would be charged/held, and a short-lived `booking_token` that opentable_book consumes. REQUIRED for CC-required slots — opentable_book refuses to commit without the token. Safe to call for standard slots too (the token skips a redundant re-lock in book). Holds the slot for ~60-90s; preview → book should happen within a minute. For Listing-type restaurants (Le Bernardin, etc.) this tool can't fetch a slot at all — callers should check `opentable_get_restaurant.bookable` first and surface the restaurant's phone/URL instead. For Experience-mandatory slots (find_slots returned booking_type=experience_mandatory), pass `experience_id` from the slot's `experience_ids` to route through the Experience slot-lock. Slots that charge the card at booking (a Deposit policy, or a prepaid/priced Experience) are refused with a link to book on opentable.com directly.
daterequiredtimerequiredslot_hashrequiredparty_sizerequiredexperience_idrestaurant_idrequireddining_area_idexperience_idsdatabase_regionreservation_tokenrequiredPreview a MODIFICATION to an existing OpenTable reservation. Takes the existing reservation's identity (restaurant_id + confirmation_number + security_token from opentable_list_reservations or the original opentable_book result) plus the NEW slot args (from a fresh opentable_find_slots call) and returns the new cancellation_policy, CC re-hold details, and a `modify_token` that opentable_modify consumes. Mirrors opentable_book_preview, but the /booking/details URL includes confirmationNumber + securityToken + isModify=true so OpenTable's SSR returns the modify state. dining_area_id is OPTIONAL — omitted, it's auto-resolved from the booking-details page like book_preview does. REQUIRED before opentable_modify — no shortcut path. For Listing-type restaurants the modify can't proceed (no slot picker); check opentable_get_restaurant.bookable first.
daterequiredtimerequiredslot_hashrequiredparty_sizerequiredexperience_idrestaurant_idrequireddining_area_idexperience_idssecurity_tokenrequireddatabase_regionreservation_tokenrequiredconfirmation_numberrequiredBook an OpenTable reservation. Requires a fresh slot_hash + reservation_token from opentable_find_slots (tokens expire within minutes — call find_slots just before book). dining_area_id is OPTIONAL: when omitted it's auto-resolved to the default dining area from OpenTable's booking-details page, so find_slots → book works without a separate opentable_get_restaurant call. For CC-required slots (prime-time at busy restaurants), opentable_book refuses without a `booking_token` from opentable_book_preview — the preview step surfaces the cancellation policy and the saved card that would be held. Auto-fetches the user's profile (name/email/phone) from /user/dining-dashboard. Returns confirmation_number + security_token; save both — they're required to cancel. For Listing-type restaurants there's no slot to lock — callers should check `opentable_get_restaurant.bookable` first and surface the restaurant's phone/URL instead. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds; the prompt names the restaurant, the card that will be held and the cancellation policy (see MCP_CONFIRM_MODE).
daterequiredtimerequiredslot_hashrequiredparty_sizerequiredconfirmTokenbooking_tokenexperience_idrestaurant_idrequireddining_area_idexperience_idsdatabase_regionreservation_tokenrequiredModify an existing OpenTable reservation in place. Requires the existing reservation's identity (restaurant_id + confirmation_number + security_token) plus a fresh modify_token from opentable_modify_preview — preview is mandatory because the new slot's cancellation policy / CC re-hold can differ from the original. Submits /dapi/booking/make-reservation with isModify: true + the existing confirmation_number + security_token; OpenTable preserves confirmation_number across modifies but may regenerate reservation_id and security_token. dining_area_id is OPTIONAL — the modify_token already carries the area opentable_modify_preview resolved; pass it only to restate it (mismatch is refused). Returns the same shape as opentable_book plus was_modified: true so the agent can phrase the user confirmation accurately. For Listing-type restaurants there's no slot to lock — agents should check opentable_get_restaurant.bookable first. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds; the prompt names the restaurant, the current and new slot, and the card re-hold (see MCP_CONFIRM_MODE).
daterequiredtimerequiredslot_hashrequiredparty_sizerequiredconfirmTokenmodify_tokenexperience_idrestaurant_idrequireddining_area_idsecurity_tokenrequiredreservation_tokenrequiredconfirmation_numberrequiredCancel an OpenTable reservation. Requires restaurant_id, confirmation_number, and security_token — all three come from opentable_list_reservations or opentable_book. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds; the prompt names the restaurant, date, time and party size from your dining dashboard (see MCP_CONFIRM_MODE). Refused when the confirmation_number belongs to a different restaurant.
confirmTokenrestaurant_idrequiredsecurity_tokenrequireddatabase_regionconfirmation_numberrequiredGet the authenticated OpenTable user's profile: name, email, phones, loyalty points and tier, home metro, member-since date. Payment and credit-card details are never exposed.
viewList the user's saved restaurants from OpenTable (Saved Restaurants list). Returns each entry's numeric restaurant_id (a number, or null when OpenTable omits it — the same id opentable_get_restaurant, opentable_find_slots and opentable_remove_favorite take), name, cuisine, neighborhood, price band, rating, and OpenTable URL.
viewAdd a restaurant to the user's Saved Restaurants list.
restaurant_idrequiredRemove a restaurant from the user's Saved Restaurants list.
restaurant_idrequiredSearch OpenTable for restaurants. Returns matching restaurants with cuisine, neighborhood, price band, rating, description, and URL. Does NOT include bookable slot tokens — use opentable_find_slots for a specific venue to check availability.
datetermtimeviewlatitudelocationmetro_idlongitudeparty_sizeGet full details for a single OpenTable restaurant: cuisine, price band, description, address, hours, phone, payment options, features, rating/review count, and availability_token (used internally when booking). Accepts the numeric restaurant_id, a slug, a path, or the full URL from opentable_search_restaurants — passing the search result's "url" verbatim always resolves, including legacy venues served at /{slug} instead of /r/{slug}.
viewrestaurant_idrequiredLarge menus return bounded pages of whole items; follow pagination.next_offset with the same filters. Optional section_name selects an exact section; offset/limit paginate items. view=full without paging is uncapped. Get published menus for an OpenTable restaurant, including sections, dishes, prices, variations, currency, provider and updated timestamps. Accepts the same numeric id/slug/path/URL as opentable_get_restaurant. Optional menu_name selects an exact title case-insensitively (e.g. Dinner). Returns available_menus and status: available, menu_not_found, external_only or not_available. External menu_url links are returned but never fetched. Prices describe OpenTable's published menu, not a live quote from the restaurant.
viewlimitoffsetmenu_namesection_namerestaurant_idrequiredRound-trips a small public www.opentable.com URL (/robots.txt) through ContextMint Bridge (your signed-in browser tab) and returns diagnostics: the bridge's role (host/peer/null), port, version, the extension link (linked / pair pending / not attached / never answered), the elapsed round-trip time, and a plain-English hint distinguishing 'bridge never came up' from 'extension not connected' from 'this browser can't serve a capability' from 'real www.opentable.com-side problem'. Read-only, no auth required. Tests bridge transport only. Search/menus/availability are reported only from observed real reads; booking is never probed.
Takes no parameters.
90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
{"restaurant_id":"https://www.opentable.com/r/social-san-juan","menu_name":"Dinner"}{"offset":0,"returned_items":20,"total_items":57,"next_offset":20}npm installnpm run build{ "mcpServers": { "opentable": { "command": "node", "args": ["/absolute/path/to/opentable-mcp/dist/bundle.js"] } }}{ "mcpServers": { "opentable": { "command": "node", "args": ["/absolute/path/to/opentable-mcp/dist/bundle.js"], "env": { "OT_BRIDGE": "mcp-chrome" } } }}node dist/bundle.jsnpm test # vitest, 72 unit tests, mocked fetchnpm run build # tsc + esbuild bundlenpx tsx scripts/probe-find-slots.ts # live GET round-trip via extensionnpx tsx scripts/probe-list-res.ts # live dashboard SSR