Restroworks Restaurant POS API and MCP server Let your AI agent run the back office across outlets.

Restroworks documents a REST API that you request through its account team, and no MCP server (checked 15 Nov 2026). Cotlet runs a hosted Restroworks MCP server with 18 tools that ChatGPT and Claude use in your own Restroworks login. Orders, menu changes and anything a guest sees wait for your OK.

  • Free 7-day trial, no card
  • Unofficial, not affiliated with Restroworks
Restroworks Restaurant POS logo Restroworks Restaurant POS Cloud Browser

18 tools Read and write

Multi-outlet operations

What can your AI agent do in Restroworks? The office work behind every outlet.

  • Rank yesterday's sales by outlet

  • Read flagged voids and discounts

  • Review and approve tomorrow's order

  • Raise a purchase order

  • Change a price on the master menu

  • Book a table with dietary notes

API gated, no MCP

Does Restroworks have an MCP server or an API? The official Restroworks routes, checked 15 November 2026.

Restroworks documents a REST API with webhooks and token authentication at api.restroworks.com. The sandbox is available on request and production access goes through its account team; technology partners join an onboarding program. No Restroworks MCP server and no official ChatGPT or Claude connector was found.

  • The API is built for orders, menus, inventory and sales flowing into ERP, BI, loyalty and accounting systems.
  • NEO is Restroworks' own AI agent: it changes menus, prices and availability on delivery aggregators from a prompt.
  • Restroworks was called Posist until 2024; older posist.biz logins now point to restroworks.biz.
The Restroworks API, working by hand and Cotlet compared
What you need Restroworks APIBy handCotlet
Ask ChatGPT or Claude about your outlets No MCP server found Copy and paste Hosted MCP server
Start today with your own login Request access first Your login Your login, once
Sales, orders, menus and inventory Documented endpoints One outlet at a time 18 tools, writes after your OK
Void flags, tables, recipes, suggested orders Coverage not verified In the back office Same tools, same key

Checked 15 Nov 2026. Sources: Restroworks API · Restroworks API reference · Technology Integration Program · Restroworks LLM info · Restaurant POS system · Reporting software · Analytics software · Anti-theft software · Table management · Tablet ordering · Reservation management · Queue management · Kitchen display system · Kitchen production system · Forecasting software · Inventory management · Recipe management · Supply chain management · Central kitchen management · Menu management · Digital menu boards

Set up once

How does the Restroworks MCP server work? The Restroworks MCP server by Cotlet: your agent works in your own Restroworks login.

  1. 1Sign in to Restroworks

    Once, on your restaurant's own address.

  2. 2Connect your AI agent

    One address in its settings.

  3. 3Ask about every outlet

    Read the numbers, then approve each change.

Your agent works in your own signed-in Cloud Browser. Orders to vendors, menu changes and guest messages wait for your OK. Who can see your session

Any MCP client

How to connect Restroworks to your AI agent

  1. 1

    Sign in to Restroworks in a Cloud Browser. Open your restaurant's own address, <your-restaurant>.restroworks.biz/login, in your Cotlet Cloud Browser and sign in with your Restroworks username and password.

  2. 2

    Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.

  3. 3

    Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.

Restroworks sits on the shared address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned Restroworks on after connecting? Refresh the connector and the 18 Restroworks tools appear.

ChatGPT
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Claude
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
Cursor
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
Codex
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: restroworks_restaurant_pos_read
8 read, 10 write

All 18 Restroworks MCP tools

One tool per back-office workflow on the Restroworks product pages. Guest-side ordering (kiosk, QR, website, branded app) has no tool. The read tools run at once; every write asks first.

Sales and control3

Reports by outlet, hour, daypart and category, your saved dashboard views, and the bills Restroworks flags. Scoped by your role.

  • get_sales_report Read sales broken down by location, hour, daypart, revenue center, order source or category. read

    Every outlet reports with the same definitions, so locations compare directly: net sales, per cover and, by item, the share of checks the item appears on. Read only.

    MCP callrestroworks_restaurant_pos_read → get_sales_report

    REST endpointGET https://cotlet.dev/api/v1/restroworks-restaurant-pos/sales-report

    Parameters

    Parameters: get_sales_report
    NameTypeDescription
    outlet string string Outlet name. Leave empty for every outlet your role covers.
    from string required string ISO date.
    to string required string ISO date.
    by string string One of `location`, `hour`, `daypart`, `revenue_center`, `order_source`, `category`, `item`.

    Example input

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

    Example response

    {
      "period": "2026-11-09/2026-11-15",
      "by": "location",
      "rows": [
        {
          "outlet": "Downtown",
          "net_sales": 12480,
          "per_cover": 30.29
        },
        {
          "outlet": "Riverside",
          "net_sales": 9120,
          "per_cover": 22.92
        }
      ]
    }
  • get_outlet_dashboard Read the metrics you pick, such as net sales, total bills, average per bill, discounts and void bills. read

    Views are scoped by your Restroworks role: an area manager sees their restaurants, a brand head their brands. Read only.

    MCP callrestroworks_restaurant_pos_read → get_outlet_dashboard

    REST endpointGET https://cotlet.dev/api/v1/restroworks-restaurant-pos/outlet-dashboard

    Parameters

    Parameters: get_outlet_dashboard
    NameTypeDescription
    metrics array array From `net_sales`, `total_bills`, `avg_per_bill`, `discounts`, `void_bills`, `covers_per_bill`.
    filter string string A brand, format, region or single outlet; or the name of a saved view.
    date string string ISO date. Defaults to today.

    Example response

    {
      "filter": "West region",
      "date": "2026-11-15",
      "net_sales": 96100,
      "total_bills": 312,
      "avg_per_bill": 308,
      "void_bills": 4
    }
  • review_theft_flags Read flagged bills: incidents, potential loss against sales, and what triggered each flag. read

    Restroworks reads every bill and flags voids, deletes and edits, discounts, reprints and complimentary items. Potential loss is exposure, not confirmed theft. Read only.

    MCP callrestroworks_restaurant_pos_read → review_theft_flags

    REST endpointGET https://cotlet.dev/api/v1/restroworks-restaurant-pos/theft-flags/review

    Parameters

    Parameters: review_theft_flags
    NameTypeDescription
    outlet string string Outlet name. Leave empty for every outlet your role covers.
    date string string ISO date. Defaults to today.

    Example response

    {
      "outlet": "Downtown",
      "bills_flagged": 7,
      "incidents": 9,
      "potential_loss": 214,
      "sales": 12480,
      "by_trigger": {
        "void": 4,
        "discount": 2,
        "reprint": 2,
        "complimentary": 1
      }
    }

Front of house5

Orders from every channel, tables, reservations and the waitlist. No tool rings up or settles a bill.

  • list_orders List open orders from dine-in, takeout, delivery, kiosk, QR and online ordering in one list. read

    Returns each order with its channel, table or order number, items and status, such as ordered, preparing, ready, packing or dispatched. Read only: the agent does not ring up or settle bills.

    MCP callrestroworks_restaurant_pos_read → list_orders

    REST endpointGET https://cotlet.dev/api/v1/restroworks-restaurant-pos/orders

    Parameters

    Parameters: list_orders
    NameTypeDescription
    outlet string string Outlet name. Leave empty for every outlet your role covers.
    channel string string One of `dine_in`, `takeout`, `delivery`, `kiosk`, `qr`, `online`. Leave empty for all.

    Example response

    {
      "outlet": "Downtown",
      "orders": [
        {
          "number": "#42",
          "channel": "delivery",
          "items": "8-pc Nuggets",
          "status": "Ready"
        },
        {
          "number": "T12",
          "channel": "dine_in",
          "items": "Crispy Chicken Combo",
          "status": "Ordered"
        }
      ]
    }
  • get_table_status Read each table's status, server, covers, check total and elapsed time, and the shift's settled bills. read

    Tables come back available, reserved or occupied, with elapsed time. The shift view adds settled and unsettled bills per floor and the average time per table. Read only.

    MCP callrestroworks_restaurant_pos_read → get_table_status

    REST endpointGET https://cotlet.dev/api/v1/restroworks-restaurant-pos/table-status

    Parameters

    Parameters: get_table_status
    NameTypeDescription
    outlet string required string Outlet name, as your Restroworks role shows it.
    floor string string A floor or zone, for example Patio.

    Example input

    {
      "outlet": "outlet"
    }

    Example response

    {
      "outlet": "Downtown",
      "floor": "Floor 1",
      "tables": [
        {
          "table": "12",
          "status": "occupied",
          "server": "Server A",
          "covers": 3,
          "check": 86.5,
          "elapsed_min": 42
        },
        {
          "table": "2",
          "status": "reserved",
          "at": "20:00"
        }
      ],
      "settled": 312.5,
      "unsettled": 86
    }
  • update_floor_layout Add, move or rename tables, walls, counters and zones such as Patio, Bar or a VIP section. writeAsks first

    The layout is what servers seat guests from, so the agent shows you the change before it saves. By default you confirm each call; you can switch that off for this tool.

    MCP callrestroworks_restaurant_pos_write → update_floor_layout

    REST endpointPATCH https://cotlet.dev/api/v1/restroworks-restaurant-pos/floor-layout

    Parameters

    Parameters: update_floor_layout
    NameTypeDescription
    outlet string required string Outlet name, as your Restroworks role shows it.
    zone string required string The dining zone to change.
    changes array required array Elements to add, move, rename or remove: tables with seats, walls, counters, notes.

    Example input

    {
      "outlet": "outlet",
      "zone": "zone",
      "changes": "changes"
    }

    Example response

    {
      "outlet": "Downtown",
      "zone": "Patio",
      "tables": 6,
      "saved": true
    }
  • manage_reservations List or book reservations: guest, covers, session and time, dietary notes per cover, optional deposit. writeAsks first

    A booked table is held for its full turn time, so nobody books over it. A deposit request reaches the guest and asks for money. By default you confirm each call; you can switch that off for this tool.

    MCP callrestroworks_restaurant_pos_write → manage_reservations

    REST endpointPOST https://cotlet.dev/api/v1/restroworks-restaurant-pos/reservations/manage

    Parameters

    Parameters: manage_reservations
    NameTypeDescription
    action string required string One of `list`, `create`. `list` only reads.
    outlet string required string Outlet name, as your Restroworks role shows it.
    guest string string Guest name and phone, for `create`.
    covers number number Party size.
    time string string ISO date and time.
    notes array array Allergens and dietary needs per cover, shared with the kitchen.
    deposit_per_cover number number Optional advance payment per cover; Restroworks sends the guest a payment link.

    Example input

    {
      "action": "action",
      "outlet": "outlet"
    }

    Example response

    {
      "outlet": "Downtown",
      "guest": "Example Guest",
      "covers": 4,
      "time": "2026-11-21T19:30",
      "table": "4",
      "deposit": 40,
      "link_sent": true
    }
  • manage_waitlist Read the virtual queue, add a party, or tell a guest their table is ready. writeAsks first

    Restroworks texts guests as the line moves. `notify` sends one now, so it reaches the guest. By default you confirm each call; you can switch that off for this tool.

    MCP callrestroworks_restaurant_pos_write → manage_waitlist

    REST endpointPOST https://cotlet.dev/api/v1/restroworks-restaurant-pos/waitlist/manage

    Parameters

    Parameters: manage_waitlist
    NameTypeDescription
    action string required string One of `list`, `add`, `notify`, `seat`. `list` only reads.
    outlet string required string Outlet name, as your Restroworks role shows it.
    party string string Name and phone, for `add`; the queue number for the others.
    size number number Party size, for `add`.

    Example input

    {
      "action": "action",
      "outlet": "outlet"
    }

    Example response

    {
      "outlet": "Downtown",
      "average_wait_min": 18,
      "queue": [
        {
          "number": 3,
          "party": 2,
          "status": "Table ready"
        },
        {
          "number": 4,
          "party": 4,
          "status": "In queue"
        }
      ]
    }

Kitchen and production3

The kitchen queue by station, forecasts by daypart and the central kitchen plan.

  • get_kitchen_queue Read the kitchen display queue: orders from every channel, the station each goes to and how long it has waited. read

    The same list the kitchen display shows in the browser. Read only.

    MCP callrestroworks_restaurant_pos_read → get_kitchen_queue

    REST endpointGET https://cotlet.dev/api/v1/restroworks-restaurant-pos/kitchen-queue

    Parameters

    Parameters: get_kitchen_queue
    NameTypeDescription
    outlet string required string Outlet name, as your Restroworks role shows it.
    station string string A station, for example Grill or Bar.

    Example input

    {
      "outlet": "outlet"
    }

    Example response

    {
      "outlet": "Downtown",
      "station": "Grill",
      "tickets": [
        {
          "order": "#1043",
          "channel": "delivery",
          "waiting": "00:01"
        },
        {
          "order": "#1041",
          "channel": "kiosk",
          "waiting": "02:40"
        }
      ]
    }
  • get_production_forecast Read the forecast per item, station and daypart, and produced against sold by location. read

    Restroworks forecasts each item from sales history, refreshes estimates every 15 minutes during the shift, and tracks produced, sold and forecast quantities. Read only.

    MCP callrestroworks_restaurant_pos_read → get_production_forecast

    REST endpointGET https://cotlet.dev/api/v1/restroworks-restaurant-pos/production-forecast

    Parameters

    Parameters: get_production_forecast
    NameTypeDescription
    outlet string string Outlet name. Leave empty for every outlet your role covers.
    date string string ISO date. Defaults to today.
    station string string A station, for example Fry station.

    Example response

    {
      "outlet": "Downtown",
      "station": "Fry station",
      "daypart": "Lunch",
      "items": [
        {
          "item": "French Fries",
          "forecast": 296,
          "produced": 280,
          "sold": 271
        }
      ]
    }
  • plan_central_kitchen Read the central kitchen plan from outlet orders, adjust what to make, and lock it into a draft purchase. writeAsks first

    The plan nets each item against stock and breaks it into raw materials. Locking turns it into the purchase plan with a draft order. By default you confirm each call; you can switch that off for this tool.

    MCP callrestroworks_restaurant_pos_write → plan_central_kitchen

    REST endpointPOST https://cotlet.dev/api/v1/restroworks-restaurant-pos/central-kitchen/plan

    Parameters

    Parameters: plan_central_kitchen
    NameTypeDescription
    action string required string One of `get`, `edit`, `lock`. `get` only reads.
    date string string ISO date. Defaults to today.
    changes array array For `edit`: item and quantity to make.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "date": "2026-11-16",
      "items": [
        {
          "item": "Croissant",
          "need": 130,
          "prepared": 40,
          "make": 90
        }
      ],
      "purchase_plan": [
        {
          "item": "Flour",
          "on_hand": 18,
          "need": 60,
          "order": 42,
          "unit": "lb"
        }
      ],
      "locked": false
    }

Inventory, recipes and buying4

Stock in base units, the recipes that deduct it, the suggested order and purchase orders to vendors.

  • get_inventory_levels Read stock per ingredient in its base unit, with the outlet's approved vendors. read

    Each billed menu item deducts its recipe from stock, so levels move with sales. Units follow the buy, count and use conversions set at brand level. Read only.

    MCP callrestroworks_restaurant_pos_read → get_inventory_levels

    REST endpointGET https://cotlet.dev/api/v1/restroworks-restaurant-pos/inventory-levels

    Parameters

    Parameters: get_inventory_levels
    NameTypeDescription
    outlet string required string Outlet name, as your Restroworks role shows it.
    item string string An ingredient, for example Cheddar.

    Example input

    {
      "outlet": "outlet"
    }

    Example response

    {
      "outlet": "Downtown",
      "items": [
        {
          "item": "Cheddar",
          "on_hand": 12000,
          "unit": "g"
        },
        {
          "item": "Burger buns",
          "on_hand": 60,
          "unit": "pc"
        }
      ]
    }
  • update_recipe Set the ingredients and quantities of a menu dish or prep item, per channel, with substitutes per outlet. writeAsks first

    Recipes drive stock deduction and plate cost at every outlet that uses them. An outlet substitute is logged for audit. By default you confirm each call; you can switch that off for this tool.

    MCP callrestroworks_restaurant_pos_write → update_recipe

    REST endpointPATCH https://cotlet.dev/api/v1/restroworks-restaurant-pos/recipe

    Parameters

    Parameters: update_recipe
    NameTypeDescription
    item string required string Menu dish or prep item, for example Chicken Alfredo or Alfredo sauce.
    lines array required array Ingredient, quantity and unit per line.
    channel string string For a variant: `dine_in` or `delivery`, with packaging lines.
    outlet string string For an ingredient substitute at one outlet only.

    Example input

    {
      "item": "item",
      "lines": "lines"
    }

    Example response

    {
      "item": "Mac & Cheese",
      "channel": "delivery",
      "lines": 3,
      "plate_cost": 3.9,
      "saved": true
    }
  • review_suggested_order Read tomorrow's suggested order (need, in stock, order), edit quantities and approve it. writeAsks first

    Restroworks forecasts the need, subtracts stock on hand and suggests the order; the store manager edits and approves it. Approving commits the order, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.

    MCP callrestroworks_restaurant_pos_write → review_suggested_order

    REST endpointPOST https://cotlet.dev/api/v1/restroworks-restaurant-pos/suggested-order/review

    Parameters

    Parameters: review_suggested_order
    NameTypeDescription
    action string required string One of `get`, `edit`, `approve`. `get` only reads.
    outlet string required string Outlet name, as your Restroworks role shows it.
    changes array array For `edit`: item and new quantity.

    Example input

    {
      "action": "edit",
      "outlet": "Downtown",
      "changes": [
        {
          "item": "Buns",
          "order": 170
        }
      ]
    }

    Example response

    {
      "outlet": "Downtown",
      "date": "2026-11-16",
      "lines": [
        {
          "item": "Chicken",
          "need": 120,
          "in_stock": 45,
          "order": 75
        },
        {
          "item": "Buns",
          "need": 240,
          "in_stock": 60,
          "order": 170
        }
      ],
      "approved": false
    }
  • create_purchase_order Raise a requisition, a direct purchase order or a standing order for a vendor. writeAsks first

    Restroworks prices each line from the vendor rate valid on that date. A purchase order commits money to a vendor, so the agent shows the vendor, lines and total first. By default you confirm each call; you can switch that off for this tool.

    MCP callrestroworks_restaurant_pos_write → create_purchase_order

    REST endpointPOST https://cotlet.dev/api/v1/restroworks-restaurant-pos/purchase-orders

    Parameters

    Parameters: create_purchase_order
    NameTypeDescription
    type string required string One of `requisition`, `direct`, `standing`.
    outlet string required string Outlet name, as your Restroworks role shows it.
    vendor string required string An approved vendor.
    lines array required array Item and quantity per line.

    Example input

    {
      "type": "type",
      "outlet": "outlet",
      "vendor": "vendor",
      "lines": "lines"
    }

    Example response

    {
      "type": "direct",
      "outlet": "Downtown",
      "vendor": "Example Foods",
      "lines": [
        {
          "item": "Chicken Breast",
          "quantity": 40,
          "unit": "lb",
          "rate": 2.1
        }
      ],
      "total": 84,
      "status": "created"
    }

Menus3

The master menu with regional and outlet overrides, out of stock items and digital menu boards. Changes reach guests on every channel.

  • update_menu Change items, categories, prices and modifiers on the master menu, by region or for one outlet. writeAsks first

    A master menu change reaches every outlet and channel that inherits it, from POS to kiosk, QR, website and delivery listings. That is many guests at once, so the agent lists the outlets affected before publishing. By default you confirm each call; you can switch that off for this tool.

    MCP callrestroworks_restaurant_pos_write → update_menu

    REST endpointPATCH https://cotlet.dev/api/v1/restroworks-restaurant-pos/menu

    Parameters

    Parameters: update_menu
    NameTypeDescription
    items array required array Item, category, price and modifiers to set.
    scope string string Master menu (default), a brand, format, region or one outlet as an override.

    Example input

    {
      "items": "items"
    }

    Example response

    {
      "scope": "Master menu",
      "items": [
        {
          "item": "Cheeseburger Combo",
          "was": 9.99,
          "now": 9.49
        }
      ],
      "outlets": 6,
      "published": true
    }
  • set_item_availability Mark a menu item out of stock or back in stock at an outlet. writeAsks first

    The change reaches every channel of that outlet, and menu boards show the next mapped item instead. Guests stop seeing the item at once. By default you confirm each call; you can switch that off for this tool.

    MCP callrestroworks_restaurant_pos_write → set_item_availability

    REST endpointPUT https://cotlet.dev/api/v1/restroworks-restaurant-pos/item-availability

    Parameters

    Parameters: set_item_availability
    NameTypeDescription
    outlet string required string Outlet name, as your Restroworks role shows it.
    item string required string Menu item.
    in_stock boolean required boolean False to take it off, true to bring it back.

    Example input

    {
      "outlet": "outlet",
      "item": "item",
      "in_stock": true
    }

    Example response

    {
      "outlet": "Downtown",
      "item": "Loaded Fries",
      "in_stock": false,
      "channels": [
        "POS",
        "Kiosk",
        "QR",
        "Online"
      ]
    }
  • update_menu_boards Set the hero items, offer strips and daypart schedule of digital menu boards, then publish. writeAsks first

    Boards take prices and availability from the POS on their own; this tool sets what they feature and when. Publishing changes what guests see in the restaurant. By default you confirm each call; you can switch that off for this tool.

    MCP callrestroworks_restaurant_pos_write → update_menu_boards

    REST endpointPATCH https://cotlet.dev/api/v1/restroworks-restaurant-pos/menu-boards

    Parameters

    Parameters: update_menu_boards
    NameTypeDescription
    outlet string string Outlet name. Leave empty for every outlet your role covers.
    board string required string Board or layout name.
    items array array Hero items and offer banners.
    schedule array array Daypart menus: breakfast, lunch, dinner or promotional, with times.

    Example input

    {
      "board": "board"
    }

    Example response

    {
      "board": "Counter left",
      "items": [
        "Juicy Fried Chicken Burger",
        "Big Stack combo"
      ],
      "schedule": [
        {
          "menu": "Breakfast",
          "from": "07:00",
          "to": "11:00"
        }
      ],
      "published": true
    }
Encrypted, revocable

Who can see my Restroworks session, and how do I revoke it?

  • What we store

    Your signed-in Restroworks browser profile, AES-256-GCM encrypted, in Finland. Never your password.

  • What your agent gets

    The 18 Restroworks tools. The session cookie stays in the Cloud Browser.

  • What the session sees

    The brands and outlets your Restroworks role covers: an area manager's restaurants, a brand head's brands.

  • What no tool touches

    Taking payment or settling bills, users and roles, aggregator and payment integrations, and NEO.

  • If Restroworks signs you out

    You sign in again yourself, in the same Cloud Browser.

  • How to cut access

    Disable Restroworks for agents, reset the browser, or change your Restroworks password.

Cotlet never sees or stores your password. You type it yourself on your restaurant's own Restroworks address, and the agent only uses the session that sign-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).

We keep it working

What happens when Restroworks changes? The tools work through the same back-office screens your managers use.

Cotlet watches the apps it serves and updates the Restroworks server when the back office changes, so your agent keeps working without a change on your side. The move from posist.biz to restroworks.biz addresses is the kind of change it absorbs.

The agent sees only what your login sees. Sign in as a brand head for every outlet, or as an area manager for a region; modules your contract does not include stay out of reach.

If Restroworks signs you out, one click in the Cotlet console reopens the Cloud Browser so you can sign in again.

10 tools ask first

Approvals, undo and mistakes Vendors, guests and outlets get nothing until you say so.

  1. 01 Read the stock get_inventory_levels returns what is on hand.
  2. 02 Read the suggestion review_suggested_order shows need, in stock and order.
  3. 03 Show you the edit The changed lines, before anything is saved.
  4. 04 Approve after your OK The order is committed only when you say so.
Fixing a Restroworks write that went wrong
ActionHow to put it right
Menu price, recipe, floor layout, menu boardCall update_menu, update_recipe, update_floor_layout or update_menu_boards with the earlier values
Item marked out of stockMark it back in stock with set_item_availability
Approved order or purchase orderAlready with the vendor: change or cancel it with them
Reservation deposit link or waitlist textAlready with the guest: follow up directly

All 10 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 8 read tools run at once.

MCP call
{
  "name": "review_suggested_order",
  "arguments": {
    "action": "edit",
    "outlet": "Downtown",
    "changes": [
      {
        "item": "Buns",
        "order": 170
      }
    ]
  }
}
REST
curl -X POST https://cotlet.dev/api/v1/restroworks-restaurant-pos/suggested-order/review \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"edit","outlet":"Downtown","changes":[{"item":"Buns","order":170}]}'
Response
{
  "outlet": "Downtown",
  "date": "2026-11-16",
  "lines": [
    {
      "item": "Chicken",
      "need": 120,
      "in_stock": 45,
      "order": 75
    },
    {
      "item": "Buns",
      "need": 240,
      "in_stock": 60,
      "order": 170
    }
  ],
  "approved": false
}

The example cuts Downtown's suggested bun order from 180 to 170 and leaves it unapproved: 240 needed, 60 in stock. A cron job or n8n flow can make the same call over REST at /api/v1/restroworks-restaurant-pos with the same key and price, in JSON. Failed calls are free.

Pay per call

How much does the Restroworks MCP server cost?

About $38 a monthfor a group of six outlets, 6,600 credits. Your Restroworks contract stays as it is.

Illustrative month, our assumption: successful calls for this workload
JobCallsCredits
Morning sales and dashboard check2 × 30600
Flagged voids and discounts1 × 30300
Suggested orders, six outlets2 × 1563,120
Items out of stock and back1 × 40400
Menu and price changes1 × 880
Reservations with dietary notes2 × 20400
Purchase orders1 × 20200
Cloud Browser, 30 days1,500
Total510 calls6,600

The smallest pack is 5,000 credits for $29; this month needs a little more. Larger groups and daily approvals per outlet use more calls.

  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Your Restroworks contract and modules apply as they are

Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.

Cotlet credit packs: price, credits and calls at 10 credits each
Credits Price, one time Calls at 10 credits Per 1,000 credits
5,000 $29 500 $5.80
15,000 $79 1,500 $5.27
32,000 $149 3,200 $4.66
60,000 $249 6,000 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Other options

Restroworks MCP server: other ways to connect What each route does for a restaurant group, and where it stops.

Other ways to work with Restroworks, checked 15 Nov 2026
OptionWhat it doesWhere it stops
Restroworks APIREST and webhooks for orders, menus, inventory and sales into your ERP, BI or own front end.Access through the account team; your team builds, hosts and fixes the integration.
NEORestroworks' own AI agent for menus, prices and availability on delivery aggregators.Inside Restroworks, for aggregator menus; not a ChatGPT or Claude connector.
Restroworks InsightsReady-made reports on the same sales data.Reports to read in Restroworks, not actions.
By handOpen each outlet in the back office.One outlet and one screen at a time.

If your IT team is building an ERP or BI feed, use the Restroworks API: it is the vendor's own route and has webhooks. Cotlet fits when an owner or area manager wants ChatGPT, Claude or a script reading and changing the back office today, from their own login, with nothing to host.

EU company, since 2019

Who runs Cotlet A company you can look up.

Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Restroworks tools.

Restroworks MCP server: questions

How do I get access?

Sign up free at https://cotlet.dev/signup?app=restroworks-restaurant-pos, turn on Restroworks under Integrations in the console and sign in on your restaurant's own restroworks.biz address in your Cloud Browser. Then connect your AI agent and ask about yesterday's sales. The trial needs no card.

Does Restroworks have an API?

Restroworks documents a REST API with webhooks at api.restroworks.com: token-based, with the sandbox available on request and production access through its account team; technology partners join an onboarding program (checked 15 Nov 2026). No Restroworks MCP server and no official ChatGPT or Claude connector was found; NEO is its own AI agent for menus on delivery aggregators. Cotlet does not use that API: it works in your own signed-in Restroworks account.

Which address do I sign in at?

Your restaurant's own Restroworks address, in the form <your-restaurant>.restroworks.biz/login, with the username and password Restroworks gave you. Older posist.biz addresses now point to restroworks.biz with the same login.

Can the agent take payments or settle bills?

No. No tool rings up orders, takes payment or settles a bill at the POS. The order and table tools only read; reservation deposits are links Restroworks sends to the guest after your OK.

Which Restroworks user should I sign in with?

The user whose outlets the agent should cover. Restroworks scopes views by role, so an area manager's login shows that region and a brand head's login shows their brands.

Is the MCP server different from the REST API?

Only in how it is called. Both carry the same 18 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.

Is Cotlet affiliated with Restroworks?

No. Cotlet is independent and not affiliated with Restroworks.

Hand tomorrow's Restroworks order review to your agent.

Free 7-day trial with 2,000 credits, no card needed.