Skip to content

MCP endpoint

post/api/mcp

The Model Context Protocol endpoint an AI assistant connects to in order to read the public booking surface on a guest's behalf. One endpoint for the whole platform, with the venue as a tool argument.

Not a REST operation. The body is JSON-RPC 2.0 and the method vocabulary is the MCP specification's (initialize, tools/list, tools/call, ...). Read the MCP specification for the envelope, and call tools/list against this endpoint for the tools: that is the authoritative, self-describing answer.

Six tools, none of which books anything. find_venues searches the businesses that chose to be found by name, suburb or postcode; get_venue, find_appointment_times and find_table_times read; start_appointment_booking and start_table_booking turn a slot token into a short-lived link on the venue's own booking page, where the guest enters their own details and confirms. No tool accepts a guest's name, email or phone, and none moves money. Opening a start_table_booking link holds that table for about ten minutes on the booking page; the tool call itself holds nothing. Everything returned is already shown to any visitor of the venue's booking page.

Findable on every plan, bookable from Growth and Pro (Venue Growth and Venue Pro). get_venue answers for any venue with its bookingPage link. The two time searches and the two booking tools need the venue's plan to include AI booking; below it they answer with bookingPage and liveTimes: false.

No timezone and no machine-readable instant is ever returned. Times come back as display text plus an opaque signed slot token, because a model handed a timezone next to a time converts it and books hours wrong.

No CORS. An MCP client is a server-to-server HTTP client; the browser-based MCP Inspector cannot reach this, so use the Inspector CLI.

No authentication, by design: nothing this endpoint reads is private.

Response Body

application/json

curl -X POST "https://example.com/api/mcp"
{  "jsonrpc": "2.0",  "id": "string",  "result": {},  "error": {    "code": 0,    "message": "string"  }}