[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

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

> 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.

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
- Page: https://cotlet.dev/integrations/restroworks-restaurant-pos-api-mcp-server

## What can your AI agent do in Restroworks?

- 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

## Does Restroworks have an MCP server or an API?

- 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.

| What you need | Restroworks API | By hand | Cotlet |
|---|---|---|---|
| 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](https://www.restroworks.com/restroworks-api/), [Restroworks API reference](https://api.restroworks.com/), [Technology Integration Program](https://www.restroworks.com/partners/technology-integration/), [Restroworks LLM info](https://www.restroworks.com/llm-info/), [Restaurant POS system](https://www.restroworks.com/restaurant-pos-system/), [Reporting software](https://www.restroworks.com/restaurant-reporting-software/), [Analytics software](https://www.restroworks.com/restaurant-analytics-software/), [Anti-theft software](https://www.restroworks.com/restaurant-anti-theft-software/), [Table management](https://www.restroworks.com/restaurant-table-management-software/), [Tablet ordering](https://www.restroworks.com/restaurant-tablet-ordering-system/), [Reservation management](https://www.restroworks.com/restaurant-reservation-management-system/), [Queue management](https://www.restroworks.com/restaurant-queue-management-software/), [Kitchen display system](https://www.restroworks.com/kitchen-display-system/), [Kitchen production system](https://www.restroworks.com/kitchen-production-system/), [Forecasting software](https://www.restroworks.com/restaurant-forecasting-software/), [Inventory management](https://www.restroworks.com/restaurant-inventory-management-software/), [Recipe management](https://www.restroworks.com/restaurant-recipe-management-software/), [Supply chain management](https://www.restroworks.com/restaurant-supply-chain-management-software/), [Central kitchen management](https://www.restroworks.com/central-kitchen-management-software/), [Menu management](https://www.restroworks.com/restaurant-menu-management-software/), [Digital menu boards](https://www.restroworks.com/restrodmb-digital-menu-boards/)

## How does the Restroworks MCP server work?

1. **Sign in to Restroworks.** Once, on your restaurant's own address.
2. **Connect your AI agent.** One address in its settings.
3. **Ask 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.

## How to connect Restroworks to your AI agent

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. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
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
```

## 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 control

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

- **Read sales reports** (`get_sales_report`, read): Read sales broken down by location, hour, daypart, revenue center, order source or category.
- **Read outlet dashboards** (`get_outlet_dashboard`, read): Read the metrics you pick, such as net sales, total bills, average per bill, discounts and void bills.
- **Review void and discount flags** (`review_theft_flags`, read): Read flagged bills: incidents, potential loss against sales, and what triggered each flag.

### Front of house

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

- **List orders across channels** (`list_orders`, read): List open orders from dine-in, takeout, delivery, kiosk, QR and online ordering in one list.
- **Read table status** (`get_table_status`, read): Read each table's status, server, covers, check total and elapsed time, and the shift's settled bills.
- **Edit the floor layout** (`update_floor_layout`, write, asks first): Add, move or rename tables, walls, counters and zones such as Patio, Bar or a VIP section.
- **Book reservations** (`manage_reservations`, write, asks first): List or book reservations: guest, covers, session and time, dietary notes per cover, optional deposit.
- **Update the waitlist** (`manage_waitlist`, write, asks first): Read the virtual queue, add a party, or tell a guest their table is ready.

### Kitchen and production

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

- **Read the kitchen queue** (`get_kitchen_queue`, read): Read the kitchen display queue: orders from every channel, the station each goes to and how long it has waited.
- **Read production forecasts** (`get_production_forecast`, read): Read the forecast per item, station and daypart, and produced against sold by location.
- **Plan central kitchen production** (`plan_central_kitchen`, write, asks first): Read the central kitchen plan from outlet orders, adjust what to make, and lock it into a draft purchase.

### Inventory, recipes and buying

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

- **Read inventory levels** (`get_inventory_levels`, read): Read stock per ingredient in its base unit, with the outlet's approved vendors.
- **Update recipes** (`update_recipe`, write, asks first): Set the ingredients and quantities of a menu dish or prep item, per channel, with substitutes per outlet.
- **Review the suggested order** (`review_suggested_order`, write, asks first): Read tomorrow's suggested order (need, in stock, order), edit quantities and approve it.
- **Create purchase orders** (`create_purchase_order`, write, asks first): Raise a requisition, a direct purchase order or a standing order for a vendor.

### Menus

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

- **Update menus and prices** (`update_menu`, write, asks first): Change items, categories, prices and modifiers on the master menu, by region or for one outlet.
- **Mark items out of stock** (`set_item_availability`, write, asks first): Mark a menu item out of stock or back in stock at an outlet.
- **Update digital menu boards** (`update_menu_boards`, write, asks first): Set the hero items, offer strips and daypart schedule of digital menu boards, then publish.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/restroworks-restaurant-pos-api-mcp-server#tools

## 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](https://cotlet.dev/security.md)).

## What happens when Restroworks changes?

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.

## Approvals, undo and mistakes

1. **Read the stock.** get_inventory_levels returns what is on hand.
2. **Read the suggestion.** review_suggested_order shows need, in stock and order.
3. **Show you the edit.** The changed lines, before anything is saved.
4. **Approve after your OK.** The order is committed only when you say so.

| Action | How to put it right |
|---|---|
| Menu price, recipe, floor layout, menu board | Call update_menu, update_recipe, update_floor_layout or update_menu_boards with the earlier values |
| Item marked out of stock | Mark it back in stock with set_item_availability |
| Approved order or purchase order | Already with the vendor: change or cancel it with them |
| Reservation deposit link or waitlist text | Already 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.

## How much does the Restroworks MCP server cost?

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

| Job | Calls | Credits |
|---|---|---|
| Morning sales and dashboard check | 2 × 30 | 600 |
| Flagged voids and discounts | 1 × 30 | 300 |
| Suggested orders, six outlets | 2 × 156 | 3,120 |
| Items out of stock and back | 1 × 40 | 400 |
| Menu and price changes | 1 × 8 | 80 |
| Reservations with dietary notes | 2 × 20 | 400 |
| Purchase orders | 1 × 20 | 200 |
| Cloud Browser, 30 days |  | 1,500 |
| Total | 510 calls | 6,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.

## Restroworks MCP server: other ways to connect

| Option | What it does | Where it stops |
|---|---|---|
| Restroworks API | REST 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. |
| NEO | Restroworks' own AI agent for menus, prices and availability on delivery aggregators. | Inside Restroworks, for aggregator menus; not a ChatGPT or Claude connector. |
| Restroworks Insights | Ready-made reports on the same sales data. | Reports to read in Restroworks, not actions. |
| By hand | Open 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.

## Who runs Cotlet

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.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
