Model Context Protocol (MCP)

Chataigne exposes a remote Model Context Protocol server for AI assistants such as Claude and Codex. It is a business-oriented facade: tools represent restaurant intentions instead of mirroring every REST endpoint.

Streamable HTTP

Stateless MCP requests use POST /mcp and structured JSON results.

Delegated OAuth

OAuth 2.1, PKCE, live consent and role checks protect every call.

24 focused restaurant tools

18 read tools and 6 bounded actions cover restaurant operations.

6 navigable resources

Models can move from search results to organization, location, catalog, order, customer and conversation details.

Connect

Use the MCP URL supplied for your environment. The canonical production URL is:

https://mcp.chataigne.ai/mcp

A compatible client discovers OAuth metadata automatically at:

/.well-known/oauth-protected-resource/mcp
/.well-known/oauth-authorization-server/api/auth

The connection flow uses OAuth Dynamic Client Registration, Authorization Code with PKCE, and refresh-token rotation. The MCP endpoint accepts Bearer access tokens only; browser cookies and API keys cannot be combined with it.

Add the remote MCP server

Add the canonical /mcp URL in your AI client.

Complete the OAuth consent screen and grant only the scopes required for the intended workflow.

Inspect the connection

Call chataigne_context_get to confirm the delegated user, client, scopes, and enabled toolset.

Discover workspaces

Call chataigne_workspaces_list before using restaurant-specific tools.

Typical workflow

chataigne_context_get
  → chataigne_workspaces_list
  → chataigne_catalog_search
  → chataigne_orders_list
  → chataigne_order_get

List and search tools are cursor-paginated and return compact data. Detail tools expose only immediate relationships. Tool responses contain a short text summary and a validated structuredContent envelope:

{
  "data": { "orders": [] },
  "meta": {
    "request_id": "request-id",
    "next_cursor": "opaque-cursor"
  }
}

Safety boundary

The restaurant V1 surface intentionally excludes payments, refunds, order cancellation/rejection, destructive deletes, campaigns, credentials, full onboarding, provider synchronization, exports and platform administration. Privileged MCP capabilities are documented separately in the gated Admin section.

Global Chataigne administrators can operate across every organization and location, but they still need the corresponding scopes in the OAuth consent. An administrator role never overrides missing OAuth consent.

Model Context Protocol (MCP)

Streamable HTTP

Delegated OAuth

24 focused restaurant tools

6 navigable resources

Connect

Typical workflow

Safety boundary

Authentication and permissions

Tools and resources

Safety and errors

Streamable HTTP

Delegated OAuth

24 focused restaurant tools

6 navigable resources

​Connect

​Typical workflow

​Safety boundary

Authentication and permissions

Tools and resources

Safety and errors

Connect

Typical workflow

Safety boundary