Travel
Mews
Arrivals, departures, guests, notes and tasks in your Mews hotel.
11 endpoints
Stayflexi gives API keys to partner integrations and runs no MCP server (checked 16 Nov 2026). Cotlet runs a hosted Stayflexi MCP server with 5 tools that ChatGPT and Claude use in your own Stayflexi POS. Orders, folio charges and outlet changes wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Stayflexi. Stayflexi is a trademark of its owner. If Stayflexi's own integrations cover what you need, use them first.
5 tools Read and write
Stayflexi gives API keys to partner integrations such as PriceLabs, but publishes no general API documentation or API price. Zapier lists one Stayflexi trigger, Get Booking. No Stayflexi MCP server and no official ChatGPT or Claude connector was found.
| What you need | Partner API or Zapier | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | Get Booking through Zapier | Copy and paste | Hosted MCP server |
| Start today with your own login | Key for a partner product | Your login | Your login, once |
| Outlet orders, tables and room service | No public POS docs | One screen at a time | 5 tools, writes after your OK |
| Run from n8n or a script | Bookings only, via Zapier | Manual only | REST, same key |
Checked 16 Nov 2026. Sources: Stayflexi integrations · PriceLabs: Stayflexi integration · Stayflexi on Zapier · Stayflexi AI agents · Stayflexi POS system · Docs: Shops / POS · Docs: Outlet Dashboard · Docs: Place Orders · Docs: Order History · Docs: Outlet Configuration · Docs: Tables & Areas · Stayflexi POS on Google Play
Once, in a browser we host for you.
One address in its settings.
Sales reads, orders and room service.
Your agent works in your own signed-in Cloud Browser. Orders, folio charges and outlet changes wait for your OK. Who can see your session
Sign in to Stayflexi in a Cloud Browser. Open pms.stayflexi.com in your Cotlet Cloud Browser and log in with your own Stayflexi user.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
Stayflexi sits on the shared address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned Stayflexi on after connecting? Refresh the connector and the 5 Stayflexi tools appear.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth 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/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: stayflexi_read One tool per POS function of Stayflexi, each matched to the Shops / POS docs. `review_outlet_orders` only reads; the others write and ask first.
Read the outlet dashboard and order history, send table or delivery orders to the kitchen, and post room service to an in-house guest's folio.
The dashboard gives running and printed orders, counts of successful, cancelled, complimentary, due and in-room orders, revenue by cash, card, wallet and other methods, and top and low sellers. History gives each order with bill and invoice number, table or room, source, status, balance and total. It changes nothing and runs without asking.
MCP callstayflexi_read → review_outlet_orders
REST endpointGET https://cotlet.dev/api/v1/stayflexi/outlet-orders/review
| Name | Type | Description |
|---|---|---|
| outlet string required | string | Outlet name as Stayflexi shows it, such as your restaurant or bar. |
| view string | string | `dashboard` (running orders, order statistics, sales overview, product performance) or `history`. Defaults to `dashboard`. |
| from string | string | ISO date. Defaults to today. |
| to string | string | ISO date. Defaults to today. |
| status string | string | For `history`: `settled`, `cancelled`, `complimentary` or `running`. |
| source string | string | For `history`: `restaurant`, `in_room`, `qr` or `delivery`. |
| search string | string | For `history`: order ID, invoice, customer or payment type. |
{
"outlet": "outlet"
} {
"outlet": "Terrace Restaurant",
"view": "history",
"from": "2026-11-16",
"to": "2026-11-16",
"orders": [
{
"bill": "TR-1042",
"table": "T4",
"source": "Restaurant",
"status": "Settled",
"total": 42
},
{
"bill": "TR-1043",
"room": "205",
"source": "In-Room",
"status": "Running",
"total": 28
},
{
"bill": "TR-1044",
"source": "Delivery",
"status": "Settled",
"total": 36
}
],
"total_revenue": 106
} Follows the Place Orders steps: pick the table or delivery, add menu items with modifiers and notes, confirm, and the order goes to the kitchen. The agent reads the items and total back to you before it confirms. Payment is settled by your staff in Stayflexi. By default you confirm each call; you can switch that off for this tool.
MCP callstayflexi_write → create_outlet_order
REST endpointPOST https://cotlet.dev/api/v1/stayflexi/outlet-orders
| Name | Type | Description |
|---|---|---|
| outlet string required | string | Outlet name as Stayflexi shows it, such as your restaurant or bar. |
| for string required | string | `table` or `delivery`. |
| table string | string | For `table`: table number. |
| customer object | object | For `delivery`: name, phone and address. |
| items array required | array | Menu items of the outlet, each with quantity and optional modifiers or a note. |
{
"outlet": "outlet",
"for": "for",
"items": "items"
} {
"outlet": "Terrace Restaurant",
"table": "T4",
"items": [
{
"item": "Grilled Salmon",
"quantity": 1
},
{
"item": "Caesar Salad",
"quantity": 1
}
],
"total": 42,
"sent_to_kitchen": true
} The charge lands on the guest's folio at once, so the agent names the room, items and total and waits for your OK. Only rooms with a guest in house can take an order. By default you confirm each call; you can switch that off for this tool.
MCP callstayflexi_write → post_room_service_order
REST endpointPOST https://cotlet.dev/api/v1/stayflexi/room-service-orders
| Name | Type | Description |
|---|---|---|
| outlet string required | string | Outlet name as Stayflexi shows it, such as your restaurant or bar. |
| room string required | string | An occupied room, as Place Orders lists it under Occupied Rooms (In-House). |
| items array required | array | Menu items of the outlet, each with quantity and optional modifiers or a note. |
{
"outlet": "Terrace Restaurant",
"room": "205",
"items": [
{
"item": "Club Sandwich",
"quantity": 1
},
{
"item": "Fresh Orange Juice",
"quantity": 2
}
]
} {
"outlet": "Terrace Restaurant",
"room": "205",
"items": [
{
"item": "Club Sandwich",
"quantity": 1
},
{
"item": "Fresh Orange Juice",
"quantity": 2
}
],
"total": 28,
"posted_to_folio": true
} Outlets are separate revenue centers with their own taxes and service charges. Tables carry an area, capacity and status.
Each outlet is its own revenue center in Stayflexi, with orders and reports kept apart. Taxes and service charges change what guests pay, so the agent shows you the fields before it saves. Menu items, staff and invoice numbering stay as they are. By default you confirm each call; you can switch that off for this tool.
MCP callstayflexi_write → manage_outlets
REST endpointPOST https://cotlet.dev/api/v1/stayflexi/outlets/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`. `list` and `get` only read. |
| outlet string | string | Outlet name, for `get`, `create` and `update`. |
| fields object | object | For `create` and `update`: basic information, tax configuration, service charge and self-service mode, in Stayflexi's own labels. |
{
"action": "action"
} {
"outlet": "Rooftop Bar",
"type": "Bar",
"service_charge": "10%",
"self_service": false,
"saved": true
} `list` returns each table with its area, occupancy and status. Release a table only after its guests have left and the order is settled, as Stayflexi asks; the agent checks that before releasing. By default you confirm each call; you can switch that off for this tool.
MCP callstayflexi_write → manage_tables
REST endpointPOST https://cotlet.dev/api/v1/stayflexi/tables/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `release`, `create`, `update`. `list` and `get` only read. |
| outlet string required | string | Outlet name as Stayflexi shows it, such as your restaurant or bar. |
| filter string | string | For `list`: `all`, `available`, `occupied` or `printed`. |
| table string | string | Table number, for `release`, `create` and `update`. |
| area string | string | Service area, for `create` and `update`. |
| capacity number | number | Seats, for `create` and `update`. |
{
"action": "action",
"outlet": "outlet"
} {
"outlet": "Terrace Restaurant",
"tables": [
{
"table": "T1",
"area": "Terrace",
"capacity": 2,
"status": "Available"
},
{
"table": "T4",
"area": "Terrace",
"capacity": 6,
"status": "Occupied"
},
{
"table": "B1",
"area": "Bar",
"capacity": 2,
"status": "Printed"
}
]
} Your signed-in Stayflexi browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 5 Stayflexi tools. The session cookie stays in the Cloud Browser.
The outlets, tables and orders your Stayflexi user can open, and nothing more.
Reservations, rates and inventory, the channel manager, payments settings, outlet staff and menu items.
You log in again yourself, in the same Cloud Browser.
Disable Stayflexi for agents, reset the browser, or change your Stayflexi password.
Cotlet never sees or stores your password: you type it into Stayflexi yourself, and the agent only uses the session that login leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
| Action | How to put it right |
|---|---|
| Outlet settings, table area or capacity | Call manage_outlets or manage_tables again with the earlier values |
| Order sent to the kitchen | Already with the kitchen: your staff cancel it in Stayflexi, and Order History shows it as Cancelled |
| Room service charge | Already on the guest folio: your front office corrects it in Stayflexi |
All 4 write tools ask first: by default you confirm each call, and you can switch that off per tool. The read tool, review_outlet_orders, runs at once.
{
"name": "post_room_service_order",
"arguments": {
"outlet": "Terrace Restaurant",
"room": "205",
"items": [
{
"item": "Club Sandwich",
"quantity": 1
},
{
"item": "Fresh Orange Juice",
"quantity": 2
}
]
}
} curl -X POST https://cotlet.dev/api/v1/stayflexi/room-service-orders \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"outlet":"Terrace Restaurant","room":"205","items":[{"item":"Club Sandwich","quantity":1},{"item":"Fresh Orange Juice","quantity":2}]}' {
"outlet": "Terrace Restaurant",
"room": "205",
"items": [
{
"item": "Club Sandwich",
"quantity": 1
},
{
"item": "Fresh Orange Juice",
"quantity": 2
}
],
"total": 28,
"posted_to_folio": true
} The example posts one club sandwich and two orange juices from the Terrace to room 205: $28 on the folio. A cron job or n8n flow can make the same call over REST at /api/v1/stayflexi with the same key and price, in JSON. Failed calls are free.
About $24 a monthfor a hotel with a restaurant and a bar on Stayflexi POS, 4,150 credits. Your Stayflexi plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning sales read, two outlets | 3 × 30 | 900 |
| Room service orders to the folio | 1 × 60 | 600 |
| Table orders placed by the agent | 1 × 45 | 450 |
| Settled tables released after service | 2 × 30 | 600 |
| Weekly order history review | 2 × 4 | 80 |
| Outlet and table setup changes | 1 × 2 | 20 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 265 calls | 4,150 |
The smallest pack, 5,000 credits for $29, covers this month. More outlets or a busy season use more calls.
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.
| 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.
| Option | What it does | Where it stops |
|---|---|---|
| Partner integrations | Products such as PriceLabs connect with a Stayflexi API key. | Each partner does its own job, such as pricing; no public POS docs for your own code. |
| Zapier | One trigger, Get Booking, also callable through Zapier MCP. | Bookings only: no outlets, tables or orders. |
| Stayflexi AI agents | Guest Assist, Reputation Manager and Night Auditor, sold by Stayflexi. | Stayflexi's own agents, not ChatGPT or Claude working in your POS. |
| Stayflexi POS mobile app | Outlets, tables and orders on iOS and Android. | Your staff tap through it; no agent or script can. |
| By hand | Open Shops / POS and click through each outlet. | One screen at a time, only while someone is at the desk. |
If a Stayflexi partner already does your job, such as pricing, use it: it is the vendor's own route. Cotlet fits when you want ChatGPT, Claude or a script reading outlet sales and preparing orders in Stayflexi today, from your own login, with nothing to host.
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 Stayflexi tools.
Sign up free at https://cotlet.dev/signup?app=stayflexi, turn on Stayflexi under Integrations in the console and log in at https://pms.stayflexi.com/ in your Cloud Browser. Then connect your AI agent and ask it about an outlet. The trial needs no card.
Stayflexi gives API keys to partner integrations such as PriceLabs, but publishes no general API documentation or API price (checked 16 Nov 2026). Zapier lists one Stayflexi trigger, Get Booking. No Stayflexi MCP server and no official ChatGPT or Claude connector was found. Cotlet does not need a key: it works in your own signed-in Stayflexi account.
The Shops / POS module (https://stayflexi.com/docs/pos): outlets, tables, table and delivery orders, room service orders to the guest folio, and the outlet dashboard and order history. Reservations, rates, the channel manager and housekeeping are not among the tools.
Stayflexi sells its own AI agents, Guest Assist, Reputation Manager and Night Auditor, on stayflexi.com. Cotlet is separate: it lets ChatGPT, Claude or a script you choose work in your Stayflexi POS with the same tools over MCP or REST.
Use the user whose outlet work the agent should do. The agent sees only the outlets, tables and orders that user can open in Stayflexi.
Only in how it is called. Both carry the same 5 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Stayflexi.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy