Toast API and MCP server Let your AI agent handle the Toast back office.

ToolWhat it doesAccess

• list_menus List the menus of a location with their availability. read

  Returns each menu from Menus > Menu management > Menu manager with the days and times it is available. Availability is set per menu in Toast, never per item, group or modifier. Any Toast Web user who can open the menus can call it.

  MCP calltoast_read → list_menus

  REST endpointGET https://cotlet.dev/api/v1/toast/menus

  Parameters

  Parameters: list_menus

  Name	Type	Description
  location string	string	Location name as shown in Toast Web. Needed when the account has several locations.

  Example response

  {
    "location": "Main Street",
    "menus": [
      {
        "name": "Lunch",
        "availability": "Specific days and time",
        "hours": [
          {
            "day": "Monday",
            "start": "11:00",
            "end": "15:00"
          }
        ]
      },
      {
        "name": "Dinner",
        "availability": "Specific days and time",
        "hours": [
          {
            "day": "Monday",
            "start": "17:00",
            "end": "22:00"
          }
        ]
      },
      {
        "name": "Drinks",
        "availability": "All day",
        "hours": []
      }
    ]
  }

• list_menu_items List the items of a menu with their stock status. read

  Returns the menu groups and items from the Menu builder with each item's stock status and, for Limited stock, the count left. Use stock_status Out of stock to get the 86 list. An item that sits in more than one place on a menu appears once per place.

  MCP calltoast_read → list_menu_items

  REST endpointGET https://cotlet.dev/api/v1/toast/menu-items

  Parameters

  Parameters: list_menu_items

  Name	Type	Description
  menu string required	string	Menu name, for example Dinner.
  stock_status string	string	Only items with this status: In stock, Out of stock or Limited stock.
  location string	string	Location name as shown in Toast Web.

  Example input

  {
    "menu": "menu"
  }

  Example response

  {
    "menu": "Dinner",
    "items": [
      {
        "name": "Salmon plate",
        "group": "Mains",
        "stock_status": "Limited stock",
        "count": 4
      },
      {
        "name": "Ribeye",
        "group": "Mains",
        "stock_status": "Out of stock",
        "count": 0
      },
      {
        "name": "House salad",
        "group": "Starters",
        "stock_status": "In stock",
        "count": null
      }
    ]
  }

• set_item_stock Mark a menu item In stock, Out of stock or Limited stock. write

  Sets the status the way Update Stock does in the Menu builder and publishes it. Out of stock keeps the item visible but not orderable, which is 86ing. Limited stock flips to Out of stock when the last unit sells. An item in several places on a menu is changed in every place and the response lists them. The account needs menu editing access. It reaches no one directly and one call undoes it, so it does not wait for your OK.

  MCP calltoast_write → set_item_stock

  REST endpointPUT https://cotlet.dev/api/v1/toast/item-stock

  Parameters

  Parameters: set_item_stock

  Name	Type	Description
  item string required	string	Item name as shown in the Menu builder.
  menu string required	string	Menu name, for example Dinner.
  stock_status string required	string	In stock, Out of stock or Limited stock.
  count integer	integer	Units left. Only with Limited stock.
  location string	string	Location name as shown in Toast Web.

  Example input

  {
    "item": "Ribeye",
    "menu": "Dinner",
    "stock_status": "Out of stock",
    "location": "Main Street"
  }

  Example response

  {
    "item": "Ribeye",
    "menu": "Dinner",
    "stock_status": "In stock",
    "places_updated": 2,
    "published": true
  }

• set_menu_availability Set the days and times a menu is available. writeasks first

  Chooses Specific days and time in the menu's Availability section, fills the day and time table, saves and publishes. Hours apply to the whole menu, because Toast has no hours for a single item, group or modifier. Guests see the new hours as soon as it is published, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.

  MCP calltoast_write → set_menu_availability

  REST endpointPUT https://cotlet.dev/api/v1/toast/menu-availability

  Parameters

  Parameters: set_menu_availability

  Name	Type	Description
  menu string required	string	Menu name, for example Dinner.
  hours array required	array	Rows with day, start and end (HH:MM). A day without a row is closed for this menu.
  location string	string	Location name as shown in Toast Web.

  Example input

  {
    "menu": "menu",
    "hours": "hours"
  }

  Example response

  {
    "menu": "Dinner",
    "hours": [
      {
        "day": "Friday",
        "start": "17:00",
        "end": "22:00"
      },
      {
        "day": "Saturday",
        "start": "17:00",
        "end": "22:00"
      }
    ],
    "published": true
  }

ToolWhat it doesAccess

• get_sales_summary Read the Sales summary report for a date range. read

  Returns the totals of Reports > Sales > Sales summary. Gross sales is the regular price of items and service charges, without tax or tip. Net sales is gross sales minus discounts and refunds. Toast records a sale when the check is first opened, not when it is paid. The account needs the Sales reports permission.

  MCP calltoast_read → get_sales_summary

  REST endpointGET https://cotlet.dev/api/v1/toast/sales-summary

  Parameters

  Parameters: get_sales_summary

  Name	Type	Description
  from string required	string	First day, YYYY-MM-DD.
  to string required	string	Last day, YYYY-MM-DD.
  dining_option string	string	Only this dining option, as named in Toast Web.
  location string	string	Location name as shown in Toast Web.

  Example input

  {
    "from": "from",
    "to": "to"
  }

  Example response

  {
    "from": "2026-10-19",
    "to": "2026-10-25",
    "gross_sales": 18420.5,
    "discounts": 412,
    "refunds": 38.5,
    "net_sales": 17970,
    "tips": 2104.75
  }

ToolWhat it doesAccess

• list_time_entries List worked shifts with clock-in and clock-out times. read

  Returns the rows of Reports > Labor > Time entry management with job, time in and time out. Entries Toast closed on its own carry a 4:00 a.m. clock-out and auto_clock_out true. The account needs the Labor reporting permission.

  MCP calltoast_read → list_time_entries

  REST endpointGET https://cotlet.dev/api/v1/toast/time-entries

  Parameters

  Parameters: list_time_entries

  Name	Type	Description
  from string required	string	First day, YYYY-MM-DD.
  to string required	string	Last day, YYYY-MM-DD.
  employee string	string	Only this employee, as named in Toast Web.
  auto_clock_outs_only boolean	boolean	Only entries Toast clocked out automatically.
  location string	string	Location name as shown in Toast Web.

  Example input

  {
    "from": "from",
    "to": "to"
  }

  Example response

  {
    "entries": [
      {
        "entry_id": "te_7f3a",
        "employee": "Dana Reyes",
        "job": "Server",
        "time_in": "2026-10-26T16:02",
        "time_out": "2026-10-27T04:00",
        "auto_clock_out": true
      },
      {
        "entry_id": "te_7f3b",
        "employee": "Luis Ortega",
        "job": "Line cook",
        "time_in": "2026-10-26T15:30",
        "time_out": "2026-10-26T23:41",
        "auto_clock_out": false
      }
    ]
  }

• update_time_entry Change the clock-in or clock-out time of a worked shift. writeasks first

  Edits the Time in and Time out fields of the entry in Time entry management. Changes sync to Toast Payroll, so they change what the employee is paid. The account needs the Edit time entries and Labor reporting permissions. It returns the entry as saved. By default you confirm each call; you can switch that off for this tool.

  MCP calltoast_write → update_time_entry

  REST endpointPATCH https://cotlet.dev/api/v1/toast/entries/{entry_id}/time-entry

  Parameters

  Parameters: update_time_entry

  Name	Type	Description
  entry_id string required	string	Id from list_time_entries.
  time_in string	string	New clock-in, YYYY-MM-DDTHH:MM.
  time_out string	string	New clock-out, YYYY-MM-DDTHH:MM.

  Example input

  {
    "entry_id": "entry_8c41d2"
  }

  Example response

  {
    "entry_id": "te_7f3a",
    "employee": "Dana Reyes",
    "time_in": "2026-10-26T16:02",
    "time_out": "2026-10-26T23:15",
    "auto_clock_out": false
  }

ToolWhat it doesAccess

• list_shifts List scheduled shifts for a date range. read

  Returns the shifts of Team > Scheduling, published or not, with the employee (empty for an open shift) and a published flag. Only admins and managers see unpublished shifts, so the account needs one of those roles. Toast Web can take up to 15 minutes to show a newly added employee.

  MCP calltoast_read → list_shifts

  REST endpointGET https://cotlet.dev/api/v1/toast/shifts

  Parameters

  Parameters: list_shifts

  Name	Type	Description
  from string required	string	First day, YYYY-MM-DD.
  to string required	string	Last day, YYYY-MM-DD.
  location string	string	Location name as shown in Toast Web.

  Example input

  {
    "from": "from",
    "to": "to"
  }

  Example response

  {
    "shifts": [
      {
        "shift_id": "sh_2201",
        "employee": "Dana Reyes",
        "job": "Server",
        "start": "2026-10-30T16:00",
        "end": "2026-10-30T23:00",
        "published": true
      },
      {
        "shift_id": "sh_2202",
        "employee": null,
        "job": "Line cook",
        "start": "2026-10-30T15:00",
        "end": "2026-10-30T23:00",
        "published": false
      }
    ]
  }

• create_shift Add a shift to the schedule, published or not. writeasks first

  Creates the shift in Team > Scheduling and needs the Admin or Manager role. With publish true, employees see it in the MyToast app, and an open shift appears on the Open shifts page where anyone can pick it up. Unpublished shifts reach no one, but a call that publishes does, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.

  MCP calltoast_write → create_shift

  REST endpointPOST https://cotlet.dev/api/v1/toast/shifts

  Parameters

  Parameters: create_shift

  Name	Type	Description
  start string required	string	Shift start, YYYY-MM-DDTHH:MM.
  end string required	string	Shift end, YYYY-MM-DDTHH:MM.
  employee string	string	Employee as named in Toast Web. Without one the shift is open.
  job string	string	Job as named in Toast Web.
  publish boolean	boolean	true publishes now. Default false keeps the shift hidden from employees.
  location string	string	Location name as shown in Toast Web.

  Example input

  {
    "start": "start",
    "end": "end"
  }

  Example response

  {
    "shift_id": "sh_2203",
    "employee": "Dana Reyes",
    "job": "Server",
    "start": "2026-10-31T16:00",
    "end": "2026-10-31T23:00",
    "published": false
  }

• publish_shifts Publish selected shifts so employees see them. writeasks first

  Publishes only the shifts you pass, like Publish selected in Scheduling. Other unpublished shifts stay hidden. Employees see published shifts in the MyToast app. Editing a published shift later may not reach employees who already checked their schedule. By default you confirm each call; you can switch that off for this tool.

  MCP calltoast_write → publish_shifts

  REST endpointPOST https://cotlet.dev/api/v1/toast/shifts/publish

  Parameters

  Parameters: publish_shifts

  Name	Type	Description
  shift_ids array required	array	Shift ids from list_shifts.

  Example input

  {
    "shift_ids": "shift ids"
  }

  Example response

  {
    "published": [
      "sh_2202",
      "sh_2203"
    ],
    "still_unpublished": 0
  }