Deploy and Host Toast MCP on Railway

Toast MCP is an open-source MCP server that connects Claude (or any MCP client) to your Toast POS. 55 read-only tools for sales, labor, time entries, orders, menus, inventory, customers, and cash. Live-tested against production restaurants. Built by a restaurant operator, for restaurant operators. Full walkthrough at chriscusack.net.

About Hosting Toast MCP

This template deploys the server from github.com/prime-cost/toast-mcp and runs it in remote (streamable HTTP) mode. You supply three values from your own Toast standard API access: client ID, client secret, and restaurant GUID. A connector password (TOAST_MCP_SECRET) is generated automatically. After deploy, generate a public domain under Settings then Networking (port 3000), confirm https://YOUR-DOMAIN/health returns status ok, then add a custom connector in Claude with the URL https://YOUR-DOMAIN/YOUR-SECRET/mcp. Your credentials stay in your Railway project and the server talks to exactly one host: Toast's API.

Common Use Cases

Ask your restaurant questions from your phone: sales, labor, hourly curves, overtime by employee
Build scheduled reports and agents that pull live POS data reliably
Audit time entries and missing clock-outs without manual exports

Dependencies for Toast MCP Hosting

Toast standard API access (request it from Toast Customer Care: free, mine came through in a day)
A Claude plan that supports custom connectors, or any other MCP client

Why Deploy Toast MCP on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Toast MCP on Railway, your POS answers are one question away, from anywhere, and every tool or agent you build gets a dependable pipe to live data. No exports, no uploads, no browser automation.