A Toast MCP server, so Claude can work with your Toast data

Status: no official server yet

Authentication

The server signs in with client credentials at POST /authentication/v1/authentication/login and receives a Bearer token.

Each request also sends the Toast-Restaurant-External-ID header, which selects the restaurant.

Honest limits

• Standard Toast API access is read-only. It allows GET requests with scopes such as orders:read and menus:read. Creating or changing orders, menus or anything else needs write access, which requires Toast partner approval. That is why every tool on this page only reads.
• Which of these tools you can use depends on your access level and the scopes on your credentials. We confirm that against your credentials at scoping.

How you’d connect it

The server runs two ways: locally over stdio, started with npx, or remotely over Streamable HTTP at a URL on your own host. The commands below use placeholders; your README has the real package name, URL and variables. NOLU does not run a shared hosted Toast server.

Claude Code

# remote (Streamable HTTP)
claude mcp add --transport http toast https://<your-host>/mcp

# local (stdio)
claude mcp add toast -e TOAST_CLIENT_ID=<value> -e TOAST_CLIENT_SECRET=<value> -e TOAST_RESTAURANT_EXTERNAL_ID=<value> -- npx -y <your-server-package>

Claude Desktop

For a remote server, add the URL https://<your-host>/mcp as a custom connector. For a local server, add it to claude_desktop_config.json:

{
  "mcpServers": {
    "toast": {
      "command": "npx",
      "args": ["-y", "<your-server-package>"],
      "env": {
        "TOAST_CLIENT_ID": "<value>",
        "TOAST_CLIENT_SECRET": "<value>",
        "TOAST_RESTAURANT_EXTERNAL_ID": "<value>"
      }
    }
  }
}

Cursor

In .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "toast": { "url": "https://<your-host>/mcp" }
  }
}

Variable names above are examples. Keep credentials in local config or your host’s secret store, never in the repository.

Who it is for

• Toast customers (restaurant groups and operators) who want Claude to work with their own Toast account, using their own credentials.
• Toast itself, if it wants an MCP server built around its API for its customers. That usually means the Standard tier, with OAuth so each user signs in with their own account.

Questions