[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) # ChowNow API and MCP server: Let your AI agent run the ChowNow Dashboard. > ChowNow has no MCP server and no API a restaurant can switch on for its own Dashboard (checked 28 Oct 2026). Its Partner API lets approved marketplaces place diner orders, and nothing more. Cotlet runs 12 ChowNow tools hosted, over MCP for agents and REST for scripts, in your own Dashboard login. Orders, item availability, hours and customers of your ChowNow restaurant. 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/chownow-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/chownow-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with ChowNow - Page: https://cotlet.dev/integrations/chownow-api-mcp-server ## What can you automate in ChowNow? - Hide an item that sold out - Read new orders - Accept an order with a ready time - Change pickup and delivery hours - Close for a holiday - Find regulars who stopped ordering ## Does ChowNow have an MCP server or an API? - The Partner API is a 0.1.0 draft with 8 endpoints: find restaurants, read the diner menu and availability, quote, place and track an order. ChowNow reviews each request, and access can be declined or revoked. - It reads which items are unavailable and which closures are active, but has no call to hide an item, accept an order, change hours or add a closure. - Zapier, n8n and Pipedream have no ChowNow app; each page answered 404 on 28 Oct 2026. | What you need | Partner API | Dashboard by hand | Cotlet | |---|---|---|---| | Read your orders | Only orders the partner placed | Yes | Yes | | Accept an order with a ready time | No | Yes, on the tablet or Dashboard | Yes, after your OK | | Hide or show a sold-out item | Reads it only | Yes | Yes | | Change hours, add or remove a closure | Reads them only | Yes | Yes, after your OK | | Customer list with order counts | No | Yes, in reports | Yes | | Who can get it | Marketplaces ChowNow approves | Any Dashboard user | Any Dashboard user | Checked 28 Oct 2026. Sources: [ChowNow Developer Portal: Introduction](https://developer.chownow.com/), [ChowNow Developer Portal: Getting Access](https://developer.chownow.com/docs/getting-access), [ChowNow Developer API, OpenAPI spec](https://developer.chownow.com/docs/openapi.json), [ChowNow Help: How to integrate with your Auphan POS](https://get.chownow.com/restaurant-support/integrating-with-your-auphan-pos/) ## How does Cotlet connect to ChowNow? 1. **Sign in to ChowNow.** 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 ChowNow password, and no order acceptance, hours change or closure goes through until you approve it. ## Connect ChowNow 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. **Sign in to the Dashboard once.** Create a Cotlet account, open ChowNow in its Cloud Browser, log in to dashboard.chownow.com and press Enable for agents. 2. **Add the Cotlet address.** Put https://cotlet.dev/mcp/v1 in the MCP server or connector list of your agent. 3. **Allow the connection.** Chat apps send you to a Cotlet sign-in page. Code editors, n8n and scripts take an API key from the console. ChowNow sits on `https://cotlet.dev/mcp/v1` with the other apps of your Cotlet account. If you turn ChowNow on after connecting, refresh the connector and its tools appear. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-chownow \ 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-chownow": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-chownow] 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: chownow_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: chownow_write ``` ## How to use the ChowNow REST API ### Create your Cotlet API key Create a Cotlet API key with access to ChowNow and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. Connect ChowNow in Cotlet and enable it for agents. Account access: Your own ChowNow Dashboard account (access to the location you work on). ### Make your first ChowNow API request REST: ``` curl https://cotlet.dev/api/v1/chownow/locations \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read locations 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": "chownow", "tool": "list_locations", "result": { "locations": [ { "location_id": "loc_8f2a41", "name": "Main Street", "ordering_paused": false }, { "location_id": "loc_c91d07", "name": "Harbor Road", "ordering_paused": true } ] } } ``` Returns the locations under Headquarters that your account can open, with the ID each other tool needs. A one-location restaurant gets one entry. Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination. ### ChowNow workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | List orders of a location, newest first. Use `list_orders` in your configured business report. | | Make | HTTP > Make a request | List the items and modifiers of a location with their availability. Use `list_menu_items` in your configured business report. | | Python or Node.js | REST API | List current and future temporary closures of a location. Use `list_closures` in your configured business report. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads ChowNow; 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/chownow-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## ChowNow API endpoints and MCP tools ### Locations and orders One location per call. Only orders with the status New can be accepted, and the diner gets the ready time. - **List locations** (`list_locations`, read): List the restaurant locations your ChowNow account can open. - **List orders** (`list_orders`, read): List orders of a location, newest first. - **Get order** (`get_order`, read): Get the full detail of one order. - **Accept order** (`accept_order`, write, asks first): Accept a new order and set its pickup or delivery time. ### Menu availability Items and modifiers from Item Availability. A hidden item leaves every platform connected to the menu, and the toggle runs at once. - **List menu items** (`list_menu_items`, read): List the items and modifiers of a location with their availability. - **Set item availability** (`set_item_availability`, write): Hide or show a menu item or modifier for diners. ### Hours and closures Overlapping menu hours make ChowNow refuse the change, and nothing is saved. A closure stops ordering until it ends or is removed. - **Get hours** (`get_hours`, read): Read pickup and delivery hours of a location. - **Update hours** (`update_hours`, write, asks first): Change the pickup or delivery hours of one day. - **List closures** (`list_closures`, read): List current and future temporary closures of a location. - **Create closure** (`create_closure`, write, asks first): Close a location for a set period, now or in the future. - **Remove closure** (`remove_closure`, write, asks first): Remove a temporary closure so the location takes orders again. ### Customers Read only, from the Customer Data report. Diners who opted out are left out. - **List customers** (`list_customers`, read): List customers of a location with their order counts. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/chownow-api-mcp-server#tools ## Who can see my ChowNow session, and how do I revoke it? - **What we store.** Your logged-in Dashboard profile, AES-256-GCM, in Finland. Not the password. - **What your agent gets.** The 12 ChowNow tools. No cookie, no partner credentials. - **What the session sees.** The locations your login opens: orders, menu, hours, customer emails. - **What no tool touches.** Refunds, order cancellations, payouts, billing and account settings. - **If ChowNow asks to verify.** A code or a new login goes through you. We never type it. - **How to cut access.** Disable for agents, reset the browser, or change the login's password. A restaurant group can give the agent a login that opens one location, so a mistake stays there. 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 ChowNow's terms? Account safety > Ask ChowNow for Partner API access. Your request is reviewed by our team; it can be approved for sandbox, or declined. > > [ChowNow Developer Portal, Getting Access, 28 Oct 2026](https://developer.chownow.com/docs/getting-access) ChowNow keeps code access for partners it vets, and the same page says approved access "can later be revoked". Cotlet uses no partner keys: it works in the Dashboard under your login, the way you would. ChowNow could still read an agent in the Dashboard as automated use, so read its [Terms of Use](https://get.chownow.com/terms-of-use/) before you connect one. How we keep your account looking like you: - Your own Dashboard login, signed in by you - One Cloud Browser with its own IP and cookies - Order acceptance, hours and closures wait for your OK - No tool refunds, cancels an order or touches payouts - If ChowNow objects, we pause the ChowNow tools for everyone within 24 h > Your staff accept orders on the same account during service. Let the agent do menu and hours work before you open, and leave the rush to the tablet. ## What happens when ChowNow changes? - **12 h** between tests of the ChowNow reads and item toggles - **24 h** between tests of order, hours and closure changes diners would notice - **$0** for a call to a ChowNow tool paused for repair ChowNow redesigned the Dashboard in August 2025, and screens will move again. When one does, the repair is ours and a scheduled run keeps its prompt. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the queue.** New orders of the location, pickup and delivery apart. 2. **Proposes a time.** A ready time per order, from your prompt. 3. **Waits for your OK.** Each acceptance shows up in your Cotlet console first. 4. **Reports back.** Accepted orders, their times, and the ones left for staff. | Action | Undo | |---|---| | Hide an item | Yes, show it with the same tool | | Accept an order | No, the diner already has the ready time | | Change hours | Set the old hours again; diners may have ordered in between | | Add a closure | Remove it with remove_closure; orders missed meanwhile stay missed | | Remove a closure | Add it again; orders may already have come in | 4 of 12 tools ask first: accept_order, update_hours, create_closure and remove_closure. set_item_availability runs at once, because hiding a dish messages nobody and one more call shows it again. Switch the wait off per tool for a scheduled run. > An active closure is a common reason a location stops getting orders. When orders go quiet, have the agent run list_closures first. MCP call: ``` { "name": "set_item_availability", "arguments": { "location_id": "loc_8f2a41", "item_id": "itm_1042", "available": false } } ``` REST: ``` curl -X PUT https://cotlet.dev/api/v1/chownow/locations/loc_8f2a41/items/itm_1042/availability \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"available":false}' ``` Response: ``` { "item_id": "itm_1042", "name": "Salmon Bowl", "available": false } ``` Scripts reach the same tools over REST at `/api/v1/chownow`, with the same key and price, so a cron job can show yesterday's hidden items again before opening. A call to an order that is no longer New fails and costs nothing. The tools table lists the REST path of each tool. ## How much does the ChowNow MCP server cost? **About $27 a month** for one restaurant location, 4,660 credits. Your ChowNow plan is billed by ChowNow as before. | Job | Calls | Credits | |---|---|---| | Hide sold-out items, show them next morning | 7 × 30 | 2,100 | | Check new orders, accept the pickup ones | 4 × 20 | 800 | | Read a catering order in full | 1 × 8 | 80 | | Holiday closure, set and checked | 2 × 2 | 40 | | Change pickup and delivery hours | 3 × 2 | 60 | | Lapsed regulars for a campaign, weekly | 2 × 4 | 80 | | Cloud Browser, 30 days | | 1,500 | | Total | | 4,660 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - No partner agreement or API keys needed The month is our example: 7 in 10 US restaurants have a single location, and ChowNow publishes no order counts. The daily sold-out round is the biggest line; a kitchen that rarely runs out pays mostly for the browser. Dollars at the $29 pack rate. ## ChowNow MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [ChowNow Partner API](https://developer.chownow.com/) | Places and tracks diner orders for a marketplace, hotel concierge or catering tool. | ChowNow approves each partner. No call accepts an order or changes the menu, hours or closures. | | [Apify: Restaurant Menu Pricing Modifiers Scraper](https://apify.com/arezdev/restaurant-menu-pricing-modifiers-scraper) | Pulls public menu items, prices and modifiers from ChowNow and other ordering pages, pay per result. | Public menus only, read only; it never opens your Dashboard. | | [Apify: ChowNow Phone Number Scraper](https://apify.com/neuro-scraper/chownow-phone-number-scraper) | Lead lists of ChowNow restaurants with public phone numbers. | Built for selling to restaurants, not for running one. | | [api-evangelist/chownow](https://github.com/api-evangelist/chownow) | A text profile of what ChowNow exposes, no code. | Docs only. No MCP server for ChowNow exists on GitHub. | A marketplace that sells ChowNow food should apply for the Partner API. Menu research across many restaurants fits a scraper. Cotlet is for the owner or manager who wants an agent to do the Dashboard work of their own locations. ## Who runs Cotlet Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273). It has worked since 2019 and was founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Send questions about the ChowNow tools to contact@cotlet.dev. ## ChowNow API and MCP: questions ### How do I get access? Make a free account at https://cotlet.dev, open ChowNow under Integrations in the console and log in to the ChowNow Dashboard in its Cloud Browser. The trial starts with your first app, and no card is asked. ### How do I connect ChowNow to ChatGPT or Claude? Sign up at cotlet.dev, log in to ChowNow 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 ChowNow account through Cotlet, in their phone apps too. ### What can ChatGPT do in ChowNow? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in ChowNow: hide sold-out menu items; accept new online orders; close for a holiday. You ask in plain words, and anything that reaches other people waits for your OK first. ### Do I need a certain ChowNow plan? Cotlet works in your own Dashboard, so it can do what your plan shows there. ChowNow lists some reports by plan: Order History is under the Hub and Premier plans, and Accounting Data under Pro. list_customers reads the Customer Data report, which ChowNow lists under its Pro reports. ### Can it refund or cancel an order? No. The tools accept orders and change menu availability, hours and closures. Refunds, order cancellations, payouts and your account and payment settings stay in ChowNow. ### Does ChowNow have webhooks? Not for restaurant owners, and the Partner API spec lists none. To catch new orders, run your agent on a schedule, for example list_orders with status New every few minutes during service. ### Does it work with my POS? Cotlet works in the ChowNow Dashboard, whatever POS sits behind it. If your POS already syncs stock to ChowNow, change availability in the POS so the two do not overwrite each other. ### Is the MCP server different from the REST API? Only the way in differs. Both carry the same 12 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and cron jobs use REST. ### Is Cotlet affiliated with ChowNow? No. Cotlet is independent and not affiliated with ChowNow, Inc. ### Can I use the ChowNow 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.