Deliverect API and MCP server Let your AI agent run the Deliverect portal.

Orders, snoozing, busy mode, opening hours and exports for your Deliverect account. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

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

14 tools Read and write

Menus to closures

What can you automate in Deliverect? Use an AI agent, a workflow or a script.

  • Snooze a sold-out item

  • Add prep time in a rush

  • Set holiday hours

  • Retry failed orders

  • Export last week's orders

  • Report failed and canceled orders

Partner API, read-only connector

Does Deliverect have an MCP server or an API? Yes to both, but neither changes your account for a restaurant.

Deliverect has an API for certified integration partners and two MCP options, and none of them lets a restaurant's agent change its account (checked 31 Oct 2026). Cotlet runs 14 Deliverect tools hosted, over MCP for agents and REST for scripts, in your own Deliverect login.

  • The API uses OAuth client credentials. A partner applies, builds in staging and gets production credentials only after certification. A restaurant cannot create its own keys.
  • The MCP server on the developer hub searches the docs and generates integration code. It has no account tools.
  • Deliverect's connector for Claude has 19 tools, all read-only: stores, menus, opening hours, recent orders and sales reports. Deliverect says it "can't change menus, orders, prices or opening hours". It is listed for Claude only.
  • Deliverect's n8n node can get and set snoozed products, but it needs the same partner credentials.
Deliverect API, Claude connector and Cotlet compared
What you need Partner APIClaude connectorCotlet
Read orders, menus and hours With partner credentials Yes, in Claude Yes
Snooze or unsnooze a product Partners only No Yes
Busy mode or close a store Not a restaurant feature No Yes, after your OK
Special hours for a holiday Not a restaurant feature No Yes, after your OK
Retry a failed order Not a restaurant feature No Yes, after your OK
Your own agent, on a schedule A server you run Claude only Hosted, any MCP client
What your account needs Certified partner A Deliverect login A Deliverect login

Checked 31 Oct 2026. Sources: Deliverect Developer Hub: Get Access Token · Deliverect Developer Hub: Become an Integration Partner · Deliverect Developer Hub: MCP · Deliverect Help Center: Use Deliverect With Claude

Set up once

How does Cotlet connect to Deliverect? One account, two ways to connect.

  1. 1Sign in to Deliverect

    Use your own account in its Cotlet Cloud Browser.

  2. 2Choose MCP or REST

    Connect your agent or create a Cotlet API key.

  3. 3Run your workflow

    Ask your agent or send an HTTP request.

We never keep your Deliverect password, and no busy mode, closure or order retry goes live until you approve it. Who can see your session

Any MCP client

Connect Deliverect to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

  1. 1

    Log in to Deliverect once. Make a Cotlet account, open Deliverect in its Cloud Browser, log in with your own manager login and press Enable for agents.

  2. 2

    Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 where your agent lists its MCP servers or connectors.

  3. 3

    Let the agent through. Chat apps open a Cotlet sign-in page. Code editors, n8n and scripts use an API key you make in the console.

Deliverect shares https://cotlet.dev/mcp/v1 with every other app on your Cotlet account. Turned Deliverect on after you connected? Refresh the connector so its tools appear.

Claude
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-deliverect \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-deliverect": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
Codex
# ~/.codex/config.toml
[mcp_servers.cotlet-deliverect]
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: deliverect_read
Make, Zapier
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: deliverect_write
Scripts and HTTP

How to use the Deliverect REST API

Create your Cotlet API key

Create a Cotlet API key with access to Deliverect and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect Deliverect in Cotlet and enable it for agents. Account access: Your own Deliverect account, with email and password or Google (each job needs the matching role permission, such as Snooze products, Toggle busy mode or Retry orders).

Make your first Deliverect API request

REST
curl "https://cotlet.dev/api/v1/deliverect/orders?from=2026-10-30&to=2026-10-30&status=Failed&location=Ghent+Centrum" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read orders and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt
{
  "status": "success",
  "app": "deliverect",
  "tool": "list_orders",
  "result": {
    "orders": [
      {
        "order_id": "DR-4M8LP",
        "pickup_time": "2026-10-30T12:40",
        "location": "Ghent Centrum",
        "channel": "Deliveroo",
        "delivery_system": "Channel courier",
        "receipt_id": "",
        "status": "Failed"
      }
    ]
  }
}

Returns the rows of the Orders page: pickup time, location, order ID from the channel, channel, delivery system, receipt ID and status. A canceled order can show twice with the same order ID and receipt ID.

Needs the View orders permission in Deliverect.

Replace Ghent Centrum with your own location; accounts with several locations need the correct location selection.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

Deliverect workflows for agents and automations

Deliverect workflows you configure
ToolConnect throughExample workflow
n8nHTTP RequestRead the failed and canceled order counts per channel. Use get_order_issues in your configured business report.
MakeHTTP > Make a requestList every product that is snoozed right now. Use list_snoozed_products in your configured business report.
Python or Node.jsREST APIList the entries of the Operations page. Use list_operations in your configured business report.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Deliverect; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

8 read, 6 write

Deliverect API endpoints and MCP tools

Orders and failures4

The Orders page and Analytics > Order issues. A retry reaches the kitchen, so it asks first. Needs the View orders and Retry orders permissions.

  • list_orders List orders with their channel and status. read

    Returns the rows of the Orders page: pickup time, location, order ID from the channel, channel, delivery system, receipt ID and status. A canceled order can show twice with the same order ID and receipt ID, the second one marked Canceled, so the POS does not count the revenue twice. Needs the View orders permission.

    MCP calldeliverect_read → list_orders

    REST endpointGET https://cotlet.dev/api/v1/deliverect/orders

    Parameters

    Parameters: list_orders
    NameTypeDescription
    from string string First pickup day, YYYY-MM-DD.
    to string string Last pickup day, YYYY-MM-DD.
    status string string Only orders with this status as shown on the Orders page, for example Failed, Canceled or Finalized.
    channel string string Only orders from this channel.
    location string string Location name as shown on the Locations page. Needed when the account has several locations.

    Example response

    {
      "orders": [
        {
          "order_id": "UE-7K2Q9",
          "pickup_time": "2026-10-30T12:15",
          "location": "Ghent Centrum",
          "channel": "Uber Eats",
          "delivery_system": "Channel courier",
          "receipt_id": "R-20418",
          "status": "Finalized"
        },
        {
          "order_id": "DR-4M8LP",
          "pickup_time": "2026-10-30T12:40",
          "location": "Ghent Centrum",
          "channel": "Deliveroo",
          "delivery_system": "Channel courier",
          "receipt_id": "",
          "status": "Failed"
        }
      ]
    }
  • get_order Read one order with its items, totals and status history. read

    Opens the order and returns what the Display tab shows: each item with its PLU, the total, fees, payment method, whether it is paid, the earlier statuses and, for a failed order, the reason. Needs the View orders permission.

    MCP calldeliverect_read → get_order

    REST endpointGET https://cotlet.dev/api/v1/deliverect/orders/{order_id}

    Parameters

    Parameters: get_order
    NameTypeDescription
    order_id string required string Order ID from list_orders.

    Example input

    {
      "order_id": "order_8c41d2"
    }

    Example response

    {
      "order_id": "DR-4M8LP",
      "status": "Failed",
      "reason": "Invalid PLU: ITEM-2291 not found in the POS",
      "items": [
        {
          "name": "Margherita",
          "plu": "PIZ-001",
          "quantity": 2
        },
        {
          "name": "Tiramisu",
          "plu": "ITEM-2291",
          "quantity": 1
        }
      ],
      "total": 31.5,
      "paid": true,
      "payment_method": "Online",
      "status_history": [
        "Parsed",
        "Failed"
      ]
    }
  • get_order_issues Count failed and canceled orders per channel for a date range. read

    Returns the totals of Analytics > Order issues: failed orders, which hit a problem while being sent, and canceled orders, with the channels that have the most of each. Pair it with list_orders to see the orders behind a count. Needs access to Analytics.

    MCP calldeliverect_read → get_order_issues

    REST endpointGET https://cotlet.dev/api/v1/deliverect/order-issues

    Parameters

    Parameters: get_order_issues
    NameTypeDescription
    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 on the Locations page. Needed when the account has several locations.

    Example input

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

    Example response

    {
      "from": "2026-10-24",
      "to": "2026-10-30",
      "failed": 6,
      "canceled": 16,
      "by_channel": [
        {
          "channel": "Uber Eats",
          "failed": 2,
          "canceled": 5
        },
        {
          "channel": "Deliveroo",
          "failed": 3,
          "canceled": 9
        },
        {
          "channel": "Just Eat",
          "failed": 1,
          "canceled": 2
        }
      ]
    }
  • retry_order Send a failed order to the POS again. writeasks first

    Presses Retry Order on the failed order. Use it after the cause in the Display tab is fixed, for example a PLU that now exists in the POS. If the button is missing, Deliverect support has to resolve it and the call fails. A retried order reaches the kitchen and can be prepared, so it waits for your OK. Needs the Retry orders permission. By default you confirm each call; you can switch that off for this tool.

    MCP calldeliverect_write → retry_order

    REST endpointPOST https://cotlet.dev/api/v1/deliverect/orders/{order_id}/retry

    Parameters

    Parameters: retry_order
    NameTypeDescription
    order_id string required string Order ID of a Failed order from list_orders.

    Example input

    {
      "order_id": "order_8c41d2"
    }

    Example response

    {
      "order_id": "DR-4M8LP",
      "retried": true,
      "status": "Parsed"
    }

Snoozing4

Per location and menu. Not every channel supports snoozing, and a product that is also a modifier needs two calls. A snooze reverses with one call and does not wait for your OK.

  • list_products List the products of a location menu with their snooze status. read

    Returns the products of the menu on Operations > Snoozing with their PLU and whether each is snoozed and until when. A product that is also a modifier of another product is listed in both places, because snoozing one does not snooze the other. Needs the View products permission.

    MCP calldeliverect_read → list_products

    REST endpointGET https://cotlet.dev/api/v1/deliverect/products

    Parameters

    Parameters: list_products
    NameTypeDescription
    menu string required string Menu name as shown on the Snoozing page.
    search string string Only products whose name or PLU contains this text.
    location string string Location name as shown on the Locations page. Needed when the account has several locations.

    Example input

    {
      "menu": "menu"
    }

    Example response

    {
      "menu": "Lunch",
      "products": [
        {
          "name": "Margherita",
          "plu": "PIZ-001",
          "snoozed": false
        },
        {
          "name": "Tiramisu",
          "plu": "ITEM-2291",
          "snoozed": true,
          "snoozed_until": "2026-10-31T06:00"
        }
      ]
    }
  • list_snoozed_products List every product that is snoozed right now. read

    Returns what the Snoozed products button shows: each snoozed product with its menu and the date it comes back, or indefinitely. Use it every morning to check nothing stays hidden by mistake. Needs the View products permission.

    MCP calldeliverect_read → list_snoozed_products

    REST endpointGET https://cotlet.dev/api/v1/deliverect/snoozed-products

    Parameters

    Parameters: list_snoozed_products
    NameTypeDescription
    location string string Location name as shown on the Locations page. Needed when the account has several locations.

    Example response

    {
      "snoozed": [
        {
          "name": "Tiramisu",
          "plu": "ITEM-2291",
          "menu": "Lunch",
          "until": "2026-10-31T06:00"
        },
        {
          "name": "Truffle fries",
          "plu": "SID-014",
          "menu": "Lunch",
          "until": "indefinitely"
        }
      ]
    }
  • snooze_product Take a product or modifier off the menus for a while. write

    Uses the bell icon on Operations > Snoozing. The product disappears from the channels that support snoozing, and not all do. A product that is also a modifier needs a second call with modifier_of. Check list_operations if the item still shows on a channel. It reaches no customer directly and unsnooze_product reverses it in one call, so it does not wait for your OK. Needs the Snooze products permission.

    MCP calldeliverect_write → snooze_product

    REST endpointPOST https://cotlet.dev/api/v1/deliverect/product/snooze

    Parameters

    Parameters: snooze_product
    NameTypeDescription
    product string required string Product name or PLU from list_products.
    menu string required string Menu name as shown on the Snoozing page.
    duration string required string One hour, a number of hours, a date to come back on, or indefinitely.
    modifier_of string string Product name. Set it to snooze this item as a modifier of that product instead of as a product.
    location string string Location name as shown on the Locations page. Needed when the account has several locations.

    Example input

    {
      "product": "Tiramisu",
      "menu": "Lunch",
      "duration": "until 2026-10-31 06:00",
      "location": "Ghent Centrum"
    }

    Example response

    {
      "product": "Tiramisu",
      "plu": "ITEM-2291",
      "menu": "Lunch",
      "location": "Ghent Centrum",
      "snoozed": true,
      "until": "2026-10-31T06:00"
    }
  • unsnooze_product Bring a snoozed product back on the menus. write

    Selects the product under Snoozed products and makes it available at once or at the time you give. Snoozing it again reverses the call, so it does not wait for your OK. Needs the Unsnooze products permission.

    MCP calldeliverect_write → unsnooze_product

    REST endpointPOST https://cotlet.dev/api/v1/deliverect/product/unsnooze

    Parameters

    Parameters: unsnooze_product
    NameTypeDescription
    product string required string Product name or PLU from list_snoozed_products.
    menu string required string Menu name as shown on the Snoozing page.
    at string string When it comes back, YYYY-MM-DDTHH:MM. Without it the product is available right away.
    location string string Location name as shown on the Locations page. Needed when the account has several locations.

    Example input

    {
      "product": "product",
      "menu": "menu"
    }

    Example response

    {
      "product": "Truffle fries",
      "plu": "SID-014",
      "menu": "Lunch",
      "location": "Ghent Centrum",
      "snoozed": false
    }

Stores and hours4

Busy mode and special hours show on the channels, so they ask first. Deliverect never reopens a store by itself after busy mode.

  • list_locations List the locations of the account with their channel links. read

    Returns each location from the Locations page with the delivery channels linked to it. Channels that support busy mode are marked, because not every channel does. Any user who can open the Locations page can call it.

    MCP calldeliverect_read → list_locations

    REST endpointGET https://cotlet.dev/api/v1/deliverect/locations

    Parameters

    No parameters.

    Example response

    {
      "locations": [
        {
          "name": "Ghent Centrum",
          "channels": [
            {
              "name": "Uber Eats",
              "busy_mode": true
            },
            {
              "name": "Deliveroo",
              "busy_mode": true
            },
            {
              "name": "Just Eat",
              "busy_mode": false
            }
          ]
        },
        {
          "name": "Antwerp Zuid",
          "channels": [
            {
              "name": "Uber Eats",
              "busy_mode": true
            },
            {
              "name": "Deliveroo",
              "busy_mode": true
            }
          ]
        }
      ]
    }
  • set_busy_mode Add preparation time to new orders, close the stores or reopen them. writeasks first

    Uses the Busy mode button of the location on the Locations page. Guests on the channels see longer waits or no way to order, so it waits for your OK. Deliverect does not reopen the store by itself, not even at the next opening hours, so an open call is needed to end it. Channels missing from the window do not support it and must be closed on the channel's own site. Needs the Toggle busy mode permission. By default you confirm each call; you can switch that off for this tool.

    MCP calldeliverect_write → set_busy_mode

    REST endpointPUT https://cotlet.dev/api/v1/deliverect/busy-mode

    Parameters

    Parameters: set_busy_mode
    NameTypeDescription
    mode string required string busy adds preparation time, close stops new orders, open reopens the stores or removes the added time.
    extra_prep_time integer integer Extra preparation time to add, as entered in the Busy mode window. Only with busy.
    channel string string Only this channel. Without it the call covers every channel of the location that supports the mode.
    location string required string Location name as shown on the Locations page.

    Example input

    {
      "mode": "mode",
      "location": "location"
    }

    Example response

    {
      "location": "Ghent Centrum",
      "mode": "busy",
      "extra_prep_time": 15,
      "channels_changed": [
        "Uber Eats",
        "Deliveroo"
      ],
      "channels_unsupported": [
        "Just Eat"
      ]
    }
  • get_opening_hours Read the opening hours and special hours of a location. read

    Returns the days and hours from Locations > Opening hours, including a second range for a break in service, and the special hours on the Special hours tab or the holidays on the Holidays tab, depending on what the account has. Special hours override the normal schedule only inside their period.

    MCP calldeliverect_read → get_opening_hours

    REST endpointGET https://cotlet.dev/api/v1/deliverect/opening-hours

    Parameters

    Parameters: get_opening_hours
    NameTypeDescription
    location string string Location name as shown on the Locations page. Needed when the account has several locations.

    Example response

    {
      "location": "Ghent Centrum",
      "hours": [
        {
          "day": "Monday",
          "ranges": [
            {
              "open": "11:30",
              "close": "14:30"
            },
            {
              "open": "17:30",
              "close": "22:00"
            }
          ]
        },
        {
          "day": "Tuesday",
          "ranges": [
            {
              "open": "11:30",
              "close": "22:00"
            }
          ]
        }
      ],
      "special_hours": [
        {
          "name": "Christmas closure",
          "from": "2026-12-25",
          "to": "2026-12-26",
          "hours": "Closed"
        }
      ]
    }
  • add_special_hours Close a location or set custom hours for a holiday or other date range. writeasks first

    Creates the entry on Locations > Opening hours > Special hours with the Add special hours button. The hours apply on their own during the period and the regular schedule returns after it. Not all channels support special hours, and Just Eat cannot extend hours this way. An account that only has the Holidays tab gets a holiday entry instead. Guests see the closure, so it waits for your OK. Needs the Manage opening hours permission. By default you confirm each call; you can switch that off for this tool.

    MCP calldeliverect_write → add_special_hours

    REST endpointPOST https://cotlet.dev/api/v1/deliverect/special-hours

    Parameters

    Parameters: add_special_hours
    NameTypeDescription
    name string required string Name that identifies the special hours.
    from string required string First day, YYYY-MM-DD.
    to string required string Last day, YYYY-MM-DD.
    hours string required string closed, or custom with the rows in custom_hours.
    custom_hours array array Rows with day, open and close (HH:MM). Only with custom.
    location string required string Location name as shown on the Locations page.

    Example input

    {
      "name": "Jane Doe",
      "from": "from",
      "to": "to",
      "hours": "hours",
      "location": "location"
    }

    Example response

    {
      "name": "Christmas closure",
      "location": "Ghent Centrum",
      "from": "2026-12-25",
      "to": "2026-12-26",
      "hours": "Closed",
      "created": true
    }

Operations and exports2

The Operations page tells you whether a snooze or a closure went through. An export returns the CSV link.

  • list_operations List the entries of the Operations page: busy mode, closures, snoozes, exports and syncs. read

    Returns each operation with its type, status, time and the user who started it. Use it to check that a snooze or a busy mode change went through on every channel, and to see why a snooze failed. Needs the View operation reports permission.

    MCP calldeliverect_read → list_operations

    REST endpointGET https://cotlet.dev/api/v1/deliverect/operations

    Parameters

    Parameters: list_operations
    NameTypeDescription
    from string string First day, YYYY-MM-DD.
    to string string Last day, YYYY-MM-DD.
    operation_type string string Only this type as named on the Operations page, for example Busy mode, Close store or Export.
    status string string Only operations with this status, for example success or failure.
    location string string Location name as shown on the Locations page. Needed when the account has several locations.

    Example response

    {
      "operations": [
        {
          "type": "Busy mode",
          "status": "success",
          "time": "2026-10-30T18:42",
          "user": "maya@yourname.com",
          "channel": "Uber Eats"
        },
        {
          "type": "Close store",
          "status": "failure",
          "time": "2026-10-30T18:43",
          "user": "maya@yourname.com",
          "channel": "Just Eat"
        }
      ]
    }
  • export_orders Request an orders CSV and return its download link. write

    Uses Orders > more > Export orders, then opens the new EXPORT entry on the Operations page and returns its download link. The export is the only report that lists orders by payment method, which the Orders page cannot filter by. It reaches no one and leaves no change in the account, so it does not wait for your OK. Needs the Export orders permission.

    MCP calldeliverect_write → export_orders

    REST endpointPOST https://cotlet.dev/api/v1/deliverect/orders/export

    Parameters

    Parameters: export_orders
    NameTypeDescription
    from string required string First pickup day, YYYY-MM-DD.
    to string required string Last pickup day, YYYY-MM-DD.
    status string string Only orders with this status.
    channel string string Only orders from this channel.
    split_items boolean boolean true puts each item on its own row.
    location string string Location name as shown on the Locations page. Needed when the account has several locations.

    Example input

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

    Example response

    {
      "operation": "EXPORT",
      "status": "success",
      "rows": 412,
      "download_url": "https://example.com/exports/orders-2026-10-24_2026-10-30.csv"
    }
Encrypted, revocable

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

  • What we store

    Your logged-in Deliverect profile, AES-256-GCM, in Finland. Not the password.

  • What your agent gets

    The 14 Deliverect tools. No cookie, no client secret.

  • What the session sees

    What your Deliverect role sees: orders, menus, locations, hours, operations.

  • What no tool touches

    Billing, subscriptions, payments and refunds, and user or role settings.

  • Google sign-in

    Deliverect lets you sign in with email and password or with Google. You sign in yourself, we never do.

  • How to cut access

    Disable for agents, reset the browser, or change the password in Deliverect.

Deliverect roles decide what a login can do: Snooze products, Toggle busy mode, Manage opening hours, Retry orders and Export orders are separate permissions. Make a role with only those, or restrict the user to the locations the agent should work on, and leave the rest off. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We have no SOC 2 report or third-party pentest yet.

Account risk

Is it against Deliverect's terms? Account safety The terms say nothing about bots, but they restrict credentials.

"The account credentials (username and password) are confidential and cannot be shared with third parties."
Deliverect Terms of Service, read 31 Oct 2026

We found no clause on bots, scripts, scraping or automation. Deliverect may suspend the services if it "suspects or confirms that Deliverect Services are used in breach of these Terms ... or for unintended purposes". Cotlet never receives your password: you sign in yourself in your own Cloud Browser. Deliverect could still treat an agent in your login as unintended use. We found no public case of a restaurant cut off for automation (one search, 31 Oct 2026).

How we keep your account looking like you

  • Your own Deliverect login, signed in by you
  • One Cloud Browser with its own IP and cookies
  • Busy mode, closures and retries wait for your OK
  • No tool touches billing, payments or users
  • If Deliverect objects, we pause the Deliverect tools for everyone within 24 h

Your staff use the same portal during service. Do big jobs, like holiday closures for every location, before opening or after close.

Tested every 12 h

What happens when Deliverect changes? The fix is ours; your prompts stay as they are.

between tests of the Deliverect reads and snoozes
12 h
between tests of busy mode, closures and retries your guests or kitchen would notice
24 h
for a call to a Deliverect tool paused for repair
$0

When a portal screen moves, we repair the tool and your scheduled runs keep the same prompt. status.cotlet.dev checks the site, console and API every 3 minutes.

3 tools ask first

Approvals, undo and mistakes Nothing that guests or the kitchen notice goes out unasked.

  1. 01 Finds the failures Today's orders with the status Failed at your location.
  2. 02 Reads the reason The Display tab of each one, for example a PLU the POS does not know.
  3. 03 Waits for your OK Every retry shows up in your Cotlet console first.
  4. 04 Reports back Which orders were retried, their new status, and which still need support.
Which Deliverect actions can be undone
ActionUndo
Snooze a productYes, unsnooze it with the same tool
Busy mode or close storesCall set_busy_mode with open; guests may have seen the wait or the closure
Add special hoursEdit or delete them in Opening hours; guests may have seen the closure
Retry an orderNo, the POS may already have it and the kitchen may be cooking
Export ordersNothing changes in the account

3 of 14 tools ask first: set_busy_mode, add_special_hours and retry_order. snooze_product and unsnooze_product run at once, because they reach no guest by message and one call reverses them. Turn the wait off per tool for a scheduled run.

Deliverect does not reopen a store after busy mode. Ask the agent to end it, or set a reminder in the same prompt.

MCP call
{
  "name": "snooze_product",
  "arguments": {
    "product": "Tiramisu",
    "menu": "Lunch",
    "duration": "until 2026-10-31 06:00",
    "location": "Ghent Centrum"
  }
}
REST
curl -X POST https://cotlet.dev/api/v1/deliverect/product/snooze \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"product":"Tiramisu","menu":"Lunch","duration":"until 2026-10-31 06:00","location":"Ghent Centrum"}'
Response
{
  "product": "Tiramisu",
  "plu": "ITEM-2291",
  "menu": "Lunch",
  "location": "Ghent Centrum",
  "snoozed": true,
  "until": "2026-10-31T06:00"
}

Scripts reach the same tools over REST at /api/v1/deliverect, with the same key and price, so a cron job can snooze the usual sold-out items before lunch. A call your Deliverect role cannot make fails and costs nothing. The tools table lists the REST path of each tool.

Pay per call

How much does the Deliverect MCP server cost?

About $20 a monthfor an operator with 3 locations, 3,440 credits. Your Deliverect subscription stays with Deliverect.

A month of Deliverect jobs for one operator, in credits
JobCallsCredits
Snooze sold-out items, daily3 × 30900
Failed and canceled order report, daily2 × 30600
Retry one failed order2 × 8160
Busy mode on and off during a rush2 × 8160
Holiday closure for 3 locations4 × 280
Weekly orders export1 × 440
Cloud Browser, 30 days1,500
Total3,440
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • No partner credentials needed

The month is our example: three locations on three channels, with volumes we assumed because Deliverect publishes no average. Deliverect prices its own plans per quote. Dollars at the $29 pack rate.

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

Deliverect MCP server on GitHub, n8n or hosted: which to use Every route except Cotlet needs partner credentials to change anything.

Other Deliverect MCP servers and connectors, checked 31 Oct 2026
OptionWhat it doesWhere it stops
Deliverect MCP Connector19 read-only tools for stores, menus, hours, orders and sales reports, from Deliverect itself, with your own login.Reads only, and is listed for Claude only. It cannot snooze, close a store or retry an order.
developers.deliverect.com/mcpDocumentation search and code generation for integrators.No account access.
NoBanks/deliverect-mcp8 tools for orders, menus, locations, channels, busy mode and snoozing. MIT licensed.Needs partner client credentials and a host you run; 1 star, last commit 31 May 2026. Live-channel actions are switched off by default.
Deliverect n8n nodeBuilt by Deliverect: get stores, get and set snoozed products, sync products, publish a menu.Needs the same partner credentials.

To ask Claude about last week's sales, Deliverect's own connector is the simplest pick and costs nothing extra. For an agent you choose that snoozes items, closes stores and retries orders, and that runs on a timer, Cotlet works without partner credentials.

EU company, since 2019

Who runs Cotlet A company you can look up.

Take Group sp. z o.o. runs Cotlet: a software company registered in Poland, EU (VAT PL6342984273), working since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Deliverect tools go to contact@cotlet.dev.

Deliverect API and MCP: questions

How do I get access?

Create a free account at https://cotlet.dev, open Deliverect under Integrations in the console and log in to Deliverect in its Cloud Browser. The trial starts with your first app and asks for no card.

How do I connect Deliverect to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Deliverect once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Deliverect account through Cotlet, in their phone apps too.

What can ChatGPT do in Deliverect?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Deliverect: snooze sold-out items; daily failed and canceled order report; retry failed orders. You ask in plain words, and anything that reaches other people waits for your OK first.

What does my Deliverect account need?

The same role permissions the job needs in the portal. Snoozing needs Snooze products and Unsnooze products, busy mode needs Toggle busy mode, special hours need Manage opening hours, retrying needs Retry orders and exports need Export orders. A call without the permission fails. You do not need partner credentials for Cotlet.

Does Deliverect's own Claude connector do the same?

It covers the reading. Deliverect's connector for Claude has 19 read-only tools for orders, menus, stores, opening hours and sales reports, and it cannot change menus, orders, prices or opening hours. Cotlet adds the changes and works with any MCP client, not only Claude.

Does busy mode stop orders on every channel?

No. Deliverect says not all delivery channels support busy mode. A channel that is not in the Busy mode window must be closed on its own site, and the response of set_busy_mode lists the channels it could not change.

Does Deliverect have webhooks?

Deliverect signs webhooks for its integration partners, but Cotlet does not receive them. To react to a failed order, run your agent on a schedule, for example a daily list_orders with the status Failed.

Can the agent touch billing, payments or refunds?

No. None of the tools reaches billing, subscriptions, payments, refunds, users or roles.

Is the MCP server different from the REST API?

Only the way in. Both carry the same 14 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts, cron jobs and HTTP steps use REST.

Is Cotlet affiliated with Deliverect?

No. Cotlet is independent and not affiliated with Deliverect NV.

Can I use the Deliverect API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.

Give your agent access to Deliverect.

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