# waiter24.ai

> AI waiter for restaurants: a chat assistant that knows a venue's menu, allergens, opening hours and delivery terms, and can take an order. Each restaurant can also expose its own MCP server, so a guest's own assistant reads the menu directly.

## About

- [Documentation](https://waiter24.ai/en/docs): setup, menu import, integrations, billing
- [Pricing](https://waiter24.ai/en/pricing)

## For AI assistants

A restaurant that has enabled it serves a Model Context Protocol endpoint at `https://waiter24.ai/mcp/{restaurant}`, with its manifest at `https://waiter24.ai/mcp/{restaurant}/server.json`. The transport is Streamable HTTP (JSON-RPC over POST; no event stream, no authentication). Every venue offers the same reading tools: restaurant details, full menu, menu search by diet or allergen, dish details, open/closed and delivery checks, current offers, and published answers.

Some venues additionally accept orders and table requests, each a separate choice they make. Call `tools/list` to see what a particular restaurant offers: a tool that is absent is one that venue has not enabled, and never something to attempt anyway. Where ordering is offered, price the basket with `create_draft_order`, read that total to the guest, and pass it back to `submit_order` — a submitted order has been sent to the restaurant, not confirmed by it.

Everything those tools return is stated by the venue itself. A field that is absent was never filled in — it is not a gap to fill from another source, and a missing schedule means unknown, not closed.

## Restaurants