[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) # Deliverect API and MCP server: Let your AI agent run the Deliverect portal. > 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. 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. [MCP setup](https://cotlet.dev/integrations/deliverect-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/deliverect-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with Deliverect - Page: https://cotlet.dev/integrations/deliverect-api-mcp-server ## What can you automate in Deliverect? - 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 ## Does Deliverect have an MCP server or an API? - 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. | What you need | Partner API | Claude connector | Cotlet | |---|---|---|---| | 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](https://developers.deliverect.com/reference/access-token), [Deliverect Developer Hub: Become an Integration Partner](https://developers.deliverect.com/docs/become-an-integration-partner), [Deliverect Developer Hub: MCP](https://developers.deliverect.com/docs/deliverect-mcp), [Deliverect Help Center: Use Deliverect With Claude](https://help.deliverect.com/en/articles/17779451-use-deliverect-with-claude) ## How does Cotlet connect to Deliverect? 1. **Sign in to Deliverect.** Use your own account in its Cotlet Cloud Browser. 2. **Choose MCP or REST.** Connect your agent or create a Cotlet API key. 3. **Run 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. ## 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. **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. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 where your agent lists its MCP servers or connectors. 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, 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: Tool: deliverect_write ``` ## 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 | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | Read the failed and canceled order counts per channel. Use `get_order_issues` in your configured business report. | | Make | HTTP > Make a request | List every product that is snoozed right now. Use `list_snoozed_products` in your configured business report. | | Python or Node.js | REST API | List the entries of the Operations page. Use `list_operations` in your configured business report. | Send `Authorization: Bearer ` 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](https://cotlet.dev/integrations/deliverect-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## Deliverect API endpoints and MCP tools ### Orders and failures 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`, read): List orders with their channel and status. - **Get order** (`get_order`, read): Read one order with its items, totals and status history. - **Get order issues** (`get_order_issues`, read): Count failed and canceled orders per channel for a date range. - **Retry order** (`retry_order`, write, asks first): Send a failed order to the POS again. ### Snoozing 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_products`, read): List the products of a location menu with their snooze status. - **List snoozed products** (`list_snoozed_products`, read): List every product that is snoozed right now. - **Snooze product** (`snooze_product`, write): Take a product or modifier off the menus for a while. - **Unsnooze product** (`unsnooze_product`, write): Bring a snoozed product back on the menus. ### Stores and hours 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_locations`, read): List the locations of the account with their channel links. - **Set busy mode** (`set_busy_mode`, write, asks first): Add preparation time to new orders, close the stores or reopen them. - **Get opening hours** (`get_opening_hours`, read): Read the opening hours and special hours of a location. - **Add special hours** (`add_special_hours`, write, asks first): Close a location or set custom hours for a holiday or other date range. ### Operations and exports The Operations page tells you whether a snooze or a closure went through. An export returns the CSV link. - **List operations** (`list_operations`, read): List the entries of the Operations page: busy mode, closures, snoozes, exports and syncs. - **Export orders** (`export_orders`, write): Request an orders CSV and return its download link. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/deliverect-api-mcp-server#tools ## 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](https://cotlet.dev/security.md)). We have no SOC 2 report or third-party pentest yet. ## Is it against Deliverect's terms? Account safety > The account credentials (username and password) are confidential and cannot be shared with third parties. > > [Deliverect Terms of Service, read 31 Oct 2026](https://www.deliverect.com/en/terms-of-service) 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. ## What happens when Deliverect changes? - **12 h** between tests of the Deliverect reads and snoozes - **24 h** between tests of busy mode, closures and retries your guests or kitchen would notice - **$0** for a call to a Deliverect tool paused for repair When a portal screen moves, we repair the tool and your scheduled runs keep the same prompt. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Finds the failures.** Today's orders with the status Failed at your location. 2. **Reads the reason.** The Display tab of each one, for example a PLU the POS does not know. 3. **Waits for your OK.** Every retry shows up in your Cotlet console first. 4. **Reports back.** Which orders were retried, their new status, and which still need support. | Action | Undo | |---|---| | Snooze a product | Yes, unsnooze it with the same tool | | Busy mode or close stores | Call set_busy_mode with open; guests may have seen the wait or the closure | | Add special hours | Edit or delete them in Opening hours; guests may have seen the closure | | Retry an order | No, the POS may already have it and the kitchen may be cooking | | Export orders | Nothing 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. ## How much does the Deliverect MCP server cost? **About $20 a month** for an operator with 3 locations, 3,440 credits. Your Deliverect subscription stays with Deliverect. | Job | Calls | Credits | |---|---|---| | Snooze sold-out items, daily | 3 × 30 | 900 | | Failed and canceled order report, daily | 2 × 30 | 600 | | Retry one failed order | 2 × 8 | 160 | | Busy mode on and off during a rush | 2 × 8 | 160 | | Holiday closure for 3 locations | 4 × 2 | 80 | | Weekly orders export | 1 × 4 | 40 | | Cloud Browser, 30 days | | 1,500 | | Total | | 3,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. ## Deliverect MCP server on GitHub, n8n or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [Deliverect MCP Connector](https://help.deliverect.com/en/articles/17779451-use-deliverect-with-claude) | 19 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/mcp](https://developers.deliverect.com/docs/deliverect-mcp) | Documentation search and code generation for integrators. | No account access. | | [NoBanks/deliverect-mcp](https://github.com/NoBanks/deliverect-mcp) | 8 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 node](https://github.com/Deliverect/n8n-nodes-deliverect) | Built 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. ## Who runs Cotlet 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 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.