Book MCP — overview

The Book MCP lets any AI assistant act as a concierge: find a restaurant on Forktime and book a table — with one developer key that works across every venue, no per-restaurant setup. It’s the opposite of the Manage MCP: cross-venue instead of your-brands-only, and create-only instead of full control.

https://api.forktime.ai/booking/mcp

What it does — and doesn’t

Can

Search venues by city, country, cuisine, or name
Check availability for a day, time, and party size
Book a table (creates the reservation, texts the guest a link)

Can't

Edit or cancel a booking
See any restaurant’s internal data (guests, menu edits, analytics)
Touch anything it didn’t just create

The flow

search_venues — the guest wants “Italian in Toronto.” You get back matching restaurants, each with a slug.
get_availability — pass the chosen venue’s slug + the date + party size. You get the bookable times.
book — pass the venue, the chosen time, party size, and the guest’s name + phone. The reservation is created.

Editing and cancelling — by design, not here

There is no update or cancel tool. When a booking is made, the guest receives an SMS with a secure link to their reservation. Any change — a new time, a bigger party, a cancellation — happens there, by the guest, on their own ticket.

That’s deliberate: the Book MCP can only ever create, and only ever for the guest whose phone is on the booking. It can’t reach into a restaurant, and it can’t touch someone else’s reservation.

Also available in the browser

The same three capabilities are exposed as WebMCP on Forktime booking pages, so a browser-based agent on the venue’s booking page can search, check availability, and book without a separate connection. The Book MCP is the remote equivalent — for any MCP client, not just a browser agent.

Authentication — get a developer key, then connect.
Tools — search_venues, get_availability, book.