Skip to main content
The restaurant MCP surface contains 18 read tools and 6 merchant operational actions. Inputs reject unknown properties, lists are bounded to 50 records, conversation transcripts to 100 messages, and analytics calls to eight metrics over at most 366 days. Additional platform-administration capabilities are documented only in the gated Admin section.

Context and workspaces

The settings sections are store, order, opening_hours, delivery, payment_methods, ai, loyalty, referrals, notifications, and privacy.

Catalog

Search results include a chataigne://catalog-items/... resource URI when applicable.

Orders and customers

An owner is always explicit:
or:
Requesting contact details on an order requires both orders.read and customers.read.

Conversations

Internal tool traces, raw provider identities and provider payloads are never returned.

Analytics and configuration

Supported analytics metric keys are:

Operational actions

Merchant operational actions are available only when the platform write rollout is enabled and the token has the write scope. chataigne_order_status_set accepts only accepted, in_preparation, awaiting_shipment, awaiting_collection, in_delivery, or completed. It cannot cancel, reject, mark delivery failure, or refund.

Resource templates

The server advertises only resource templates covered by the token’s scopes:
Resources return application/json and apply the same live authorization as their matching detail tool.