Sign in to see your venue's slug and publishable key in every sample.
Your account has no venue yet, so the samples keep their placeholders. Sign out
Signed in as · . Create a publishable key in the console and reload to see it here. Sign out
Signed in as · . The samples show your venue's publishable key. Sign out
Developer docs
Run your venue with an AI assistant
Four operator workflows over the MCP server — briefing, holiday closures, launching an event, a gift voucher — with the tools used and the confirmations.
The MCP server lets an assistant do what you would click through in the console, with exactly your permissions. This tutorial shows four workflows from an operator's week as they actually run: what you ask, which tools the assistant calls, where it stops to ask you, and what you can rely on. Connect the server first (Connect your assistant); everything below needs you signed in as an operator.
How an agent should work
The same four habits make every workflow below safe, and they are what a well-behaved assistant does without being told:
- Read before it writes. Tools that replace a whole list — the weekly hours, the menus — say so, and the assistant reads the current state first so nothing you did not mention is lost. For a small change it picks the single-change tool, such as adding a closure.
- Preview, then confirm. A change that is hard to undo (cancelling, refunding, deleting, voiding, regenerating a QR code) works in two steps. The first call changes nothing and answers with a preview of exactly what would happen. Only after you agree does the assistant call again with the confirmation, which is valid for five minutes, for you, for that tool and for exactly those arguments. If the assistant changes anything between the two calls, it starts again with a new preview.
- Stay inside your permissions. The API decides, so what the console refuses for your role or plan, the tool refuses with the same message. On an account with several venues the assistant passes the
venueargument of every venue tool;venues_listshows the slugs. - Never carry a secret into the chat. A secret API key is shown once on a page of its own, outside the conversation. Voucher codes, ticket codes, QR token values and a guest's cancel link are never part of a tool's answer.
A call over the limit — 120 tool calls a minute, 30 of which may change data — returns an error that says how long to wait.
1. Start the day: the briefing
You: Give me today's briefing.
The prompt daily_briefing reads only. The assistant calls reservations_today_overview and reservations_list for the day's bookings and arrivals in the next hours, and summarises what needs you: today's bookings, deposits that are still unpaid and the arrivals in the next hours.
You: Which of the unpaid deposits are for tonight?
Assistant: Two bookings for this evening still have a deposit open: BDP-… at 19:00 for six, and BDP-… at 20:30 for four. Do you want me to message them?
messages_list and messages_reply handle guest messages. A reply sends an e-mail on the venue's behalf, so a careful assistant shows you the text before it sends.
2. Close for a holiday
You: We are closed on 24 and 25 December and open until 02:00 on New Year's Eve.
The prompt set_holiday_hours does three things in order. It reads the current hours (hours_get), turns your sentence into exact dates, and lists the bookings that fall on the closed days (reservations_list) — the part a human forgets. It then shows you the plan:
Assistant: I would add a closure for 24 December and 25 December, and set a special day for 31 December from 17:00 to 02:00. Eleven bookings fall on the 24th and 25th. I will not cancel any of them; I suggest you contact those guests. Shall I apply the hours?
Only after your yes does it call hours_add_closure for each closed day and hours_set_special_day for New Year's Eve. These are single-change tools: the weekly schedule is left alone. Cancelling the eleven bookings would be a separate step with its own preview per booking (reservations_set_status); the assistant does not do it as a side effect of closing.
3. Launch an event
You: Set up a darts league night on 14 January, 19:30 to 23:00, free registration, 48 places, six per registration.
The assistant calls events_create with a draft: title, venue-local date and times, free registration mode, capacity 48 and six tickets per registration. The event is a draft — nothing is public yet. It shows you the preview the console would (events_preview), including the rendered description, and asks about anything you left out: a picture, a description, the language.
You: Looks good, publish it.
events_publish makes it public. From here guests can register through your site's events widget. To watch it fill:
You: How many places are left, and who is registered?
The assistant reads the event (events_get) and event_registrations_list. On the night, event_checkin marks a ticket, and event_undo_checkin takes back a wrong scan. A paid event works the same way with a ticket price and a refund policy, and needs Premium and a connected payout account; payouts_status tells the assistant whether it can sell.
Cancelling the event (events_cancel) or refunding a registration (event_registrations_refund) is a confirmed change: you see exactly which registrations and amounts are affected before anything happens.
4. Give a voucher
You: Issue a 25 euro voucher for Ada Lovelace, as an apology for last Friday, valid for a year.
The assistant calls vouchers_issue with a not-paid payment (a goodwill voucher), the amount, the recipient and the expiry. The code is never shown in the chat: the recipient receives it by e-mail, and the answer carries only the voucher's reference. Later:
You: Has Ada used it?
vouchers_get shows the balance and the ledger of what happened to it. Voiding it (vouchers_void), changing its expiry (vouchers_change_expiry) and refunding a sale (vouchers_refund_sale) follow the preview-and-confirm pattern. At the table, voucher_lookup and voucher_redeem take a code you type or paste: the assistant needs the code to redeem it, so give it only when you mean to, and know that it is not echoed back.
What an assistant cannot do
- Take a payment. A deposit, a ticket or a voucher is paid on the venue's booking page or in the BookDinePlay app. The assistant can start nothing that moves a guest's money.
- Read a secret. Keys, codes and links are withheld as above.
- Work around your plan. Game resources, deposits, online ticket sales and several venues follow your plan exactly as in the console.
Next steps
- What the tools do — every tool and prompt by area.
- Connect your assistant — add the server to Claude, ChatGPT or VS Code.
- Several venues — the
venueargument in detail.