[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) # MarketMan API and MCP server: Let your AI agent watch par levels and draft orders. > MarketMan has a REST API (V3) and no official MCP server (checked 28 Oct 2026). Restaurants buy it as the API Access add-on, which the pricing page lists as read-only with 5,000 calls a month, and the API Partner key and password come from MarketMan support. Cotlet runs 11 MarketMan tools hosted in your own login, over MCP for agents and REST for scripts. Purchase orders, par levels, counts and food cost for your 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/marketman-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/marketman-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with MarketMan - Page: https://cotlet.dev/integrations/marketman-api-mcp-server ## What can you automate in MarketMan? - Flag items below par - Draft the weekly supplier orders - Track deliveries still open - Report actual vs theoretical usage - Find the lowest-margin dishes - Tune par levels from real usage ## Does MarketMan have an MCP server or an API? - The add-on costs $25 a month for 1 to 3 locations, $59 for 4 to 9, $99 for 10 to 30 and $199 above that, on Starter ($249) or Growth ($299). Enterprise, from $449, includes it. - Its endpoints cover the reads on this page. The docs also list CreateOrder and SetInventoryItemParLevel for partners, but the add-on restaurants buy is sold read-only. - No Zapier app and no n8n node for MarketMan. The few GitHub clients for the API are 2021 code with 0 stars, and none is an MCP server. | What you need | API add-on | GitHub client | Cotlet | |---|---|---|---| | Read orders, items, counts, AvT, margins | Yes | Some, with the add-on key | Yes | | Create a purchase order, set a par level | Sold read-only | No | Yes, orders after your OK | | How you get access | Ask support for a partner key | Same key | Your own MarketMan login | | Monthly cap | 5,000 calls | 5,000 calls | Pay per call | | Works in Claude or ChatGPT | You build it | Not an MCP server | Yes | | Allowed by MarketMan's terms | Yes, official | Yes, official API | Uses the web app | Checked 28 Oct 2026. Sources: [MarketMan API V3 documentation](https://api-doc.marketman.com/), [MarketMan pricing and plans](https://www.marketman.com/pricing-for-restaurant-inventory-management-system), [MarketMan restaurant purchasing and order management](https://www.marketman.com/platform/restaurant-purchasing-software-and-order-management), [MarketMan inventory management software](https://www.marketman.com/platform/restaurant-inventory-management-software), [MarketMan SaaS Subscription Agreement](https://www.marketman.com/saas-subscription-agreement) ## How does Cotlet connect to MarketMan? 1. **Sign in to MarketMan.** 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 MarketMan password, and no order goes to a supplier until you approve it. ## Connect MarketMan 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 MarketMan in a Cloud Browser.** Make a Cotlet account, open MarketMan in its Cloud Browser, log in with your usual MarketMan user and press Enable for agents. 2. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 where your agent takes an MCP server or a connector. 3. **Finish the sign-in.** Claude and ChatGPT open a Cotlet sign-in page. Cursor, Codex, n8n and scripts use an API key from the console. One address, `https://cotlet.dev/mcp/v1`, serves MarketMan and the other apps you enable. Enabled MarketMan after you connected? Refresh the connector so the new tools load. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-marketman \ 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-marketman": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-marketman] 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: marketman_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: marketman_write ``` ## How to use the MarketMan REST API ### Create your Cotlet API key Create a Cotlet API key with access to MarketMan and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. Connect MarketMan in Cotlet and enable it for agents. Account access: Your own MarketMan user (a role that can see and place orders for the location). ### Make your first MarketMan API request REST: ``` curl "https://cotlet.dev/api/v1/marketman/inventory-items?location=Harbor+Grill" \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read inventory items 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": "marketman", "tool": "list_inventory_items", "result": { "items": [ { "item_id": "inv_2210", "name": "Whole milk", "category": "Dairy", "unit": "case", "par_level": 8, "on_hand": 3, "supplier": "Lakeside Dairy" }, { "item_id": "inv_2214", "name": "Butter, unsalted", "category": "Dairy", "unit": "case", "par_level": 4, "on_hand": 1, "supplier": "Lakeside Dairy" } ] } } ``` Returns each item with its category, unit, par level, quantity from the last count and usual supplier. Items without a par level are left out when below_par is true. Replace `Harbor Grill` with a location available to your account. Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination. ### MarketMan workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | Lists the suppliers a location orders from. Use `list_suppliers` in your configured business report. | | Make | HTTP > Make a request | Compares what you used (from counts) with what sales say you should have used. Use `get_actual_vs_theoretical` in your configured business report. | | Python or Node.js | REST API | Lists past inventory counts of a location. Use `list_inventory_counts` in your configured business report. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads MarketMan; 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/marketman-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## MarketMan API endpoints and MCP tools ### Purchase orders and suppliers MarketMan order statuses: sent (to the supplier), pending (received by the supplier), approved (by the supplier). A new order goes to the supplier, so it asks first. - **List purchase orders** (`list_purchase_orders`, read): Lists purchase orders of a location by delivery date or sent date. - **Get a purchase order** (`get_purchase_order`, read): Returns one purchase order with its lines. - **List suppliers** (`list_suppliers`, read): Lists the suppliers a location orders from. - **Create a purchase order** (`create_purchase_order`, write, asks first): Creates a purchase order for one supplier and sends it. ### Inventory, counts and par levels On-hand quantity comes from the last count. Every call names a location, and your MarketMan role decides which locations you see. - **List inventory items** (`list_inventory_items`, read): Lists the items you order and count, with par level and last count. - **List inventory counts** (`list_inventory_counts`, read): Lists past inventory counts of a location. - **Set a par level** (`set_par_level`, write): Sets the par level of one inventory item. ### Food cost, recipes and invoices Actual vs theoretical needs two dates that each had a count. Invoices are read only; nothing is uploaded or edited. - **Get actual vs theoretical usage** (`get_actual_vs_theoretical`, read): Compares what you used (from counts) with what sales say you should have used. - **Get menu profitability** (`get_menu_profitability`, read): Returns cost, price and margin for each menu item. - **List recipes** (`list_recipes`, read): Lists recipes with their ingredients and portion cost. - **List invoices** (`list_invoices`, read): Lists supplier invoices recorded for a location. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/marketman-api-mcp-server#tools ## Who can see my MarketMan session, and how do I revoke it? - **What we store.** Your signed-in MarketMan profile, AES-256-GCM, in Finland. Not your password. - **What your agent gets.** The 11 MarketMan tools. No cookie, no API Partner key. - **What the session sees.** The locations, orders, costs and invoices your MarketMan role opens. - **What no tool touches.** Users, billing, POS and accounting settings, recipe edits. - **If MarketMan logs you out.** Your agent gets a link and you log in again. We never log in for you. - **How to cut access.** Disable MarketMan for agents, reset the browser or delete the API key. Use a MarketMan user your company bought a seat for: the agreement allows only Permitted Users the customer authorized. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)); no SOC 2 report or third-party pentest yet. ## Is it against MarketMan's terms? Account safety > Customer must not, and shall not allow any Permitted User or any other third party to: ... use any automated means to access the SaaS Services and/or the MarketMan App > > [MarketMan SaaS Subscription Agreement, Restrictions, last updated 17 Dec 2025](https://www.marketman.com/saas-subscription-agreement) The same agreement lets MarketMan suspend access "at any time in its sole discretion, with or without notice". The API add-on is the route the terms leave clear, for reads. We found no public case of a MarketMan account closed for automation (checked 28 Oct 2026); public complaints are about cancelling a contract. A group that cares should ask its MarketMan account manager first. How we keep your account looking like you: - Your own MarketMan user, logged in by you - One Cloud Browser with its own IP and cookies - Supplier orders wait for your OK - No tool edits recipes, users or integrations - If MarketMan objects, we pause the MarketMan tools for everyone within 24 h > The Terms of Use also ban "a disproportionately large load". Pull a year of reports for 30 locations over several nights, not in one run. ## What happens when MarketMan changes? - **12 h** between tests of the MarketMan reads - **$0** for a call to a MarketMan tool paused for repair If MarketMan moves a report or renames a column in Purchasing, we change the tool and the same prompt keeps working. [status.cotlet.dev](https://status.cotlet.dev) watches the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Lists items under par.** For the location you named, with each usual supplier. 2. **Groups them by supplier.** One draft order each, with quantities to reach par. 3. **Waits for your OK.** Each order shows up in your Cotlet console first. 4. **Reports back.** Orders sent, totals and delivery dates. | Action | Undo | |---|---| | Create and send a purchase order | Not through Cotlet; call or email the supplier | | Set a par level | Yes, set the old value; the tool returns it | | Every read | Nothing to undo; reads change nothing | 1 of 11 tools asks first: create_purchase_order. set_par_level runs at once and returns the old value; it reaches no one but changes what MarketMan suggests on the next order. Turn the wait off per tool for a scheduled run. > Check the delivery date before you approve: a supplier with a cutoff may have closed that day already. MCP call: ``` { "name": "set_par_level", "arguments": { "location": "Harbor Grill", "item_id": "inv_2210", "par_level": 10 } } ``` REST: ``` curl -X PUT https://cotlet.dev/api/v1/marketman/items/inv_2210/par-level \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"location":"Harbor Grill","par_level":10}' ``` Response: ``` { "item_id": "inv_2210", "name": "Whole milk", "old_par_level": 8, "par_level": 10 } ``` Scripts and cron jobs reach the same tools over REST at `/api/v1/marketman`, with one key and one price. A call for a location your role cannot open fails with a permission error and costs nothing. The tools table lists the REST path of each tool. ## How much does the MarketMan MCP server cost? **About $20 a month** for one independent restaurant, 3,480 credits. Your MarketMan plan stays as it is. | Job | Calls | Credits | |---|---|---| | Items below par with their supplier, daily | 2 × 30 | 600 | | Open orders and supplier status, daily | 3 × 30 | 900 | | Draft 4 supplier orders, weekly | 6 × 4 | 240 | | Actual vs theoretical after the count, weekly | 2 × 4 | 80 | | Lowest-margin dishes, weekly | 2 × 4 | 80 | | Invoices against orders, weekly | 2 × 4 | 80 | | Cloud Browser, 30 days | | 1,500 | | Total | | 3,480 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - No API add-on or Enterprise plan needed The month is our example: one location on Starter, 100 to 200 items, a full count each week and 4 supplier orders a week. For comparison, MarketMan's read-only API add-on is $25 a month for 1 to 3 locations, before the code you write (pricing page, 28 Oct 2026). Dollars at the $29 pack rate. ## MarketMan MCP server on GitHub or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [LukasKlement/python-marketman](https://github.com/LukasKlement/python-marketman) | A basic Python client for the V3 API, Apache-2.0. | Needs the add-on key; 0 stars, last commit 25 Apr 2021; not an MCP server. | | [Mashey/tap-marketman](https://github.com/Mashey/tap-marketman) | A Singer tap that exports API data to a warehouse. | Export only; last commit 5 Mar 2021. | | [zirinisp/marketman_google_apps_script](https://github.com/zirinisp/marketman_google_apps_script) | Pulls API data into Google Sheets. | Read only; last commit 13 Nov 2021. | | [Tenzo](https://www.gotenzo.com/integration/marketman/) | Restaurant analytics that reads MarketMan next to POS and labor data. | Dashboards for people, not an agent tool. | If you have the add-on and a developer, the API gives the reads directly. Nothing on GitHub or in Zapier and n8n speaks MCP to MarketMan, and nothing outside the web app creates orders for a restaurant. Cotlet covers both in your own login. ## Who runs Cotlet Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and trading since 2019. Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing) founded it. Write to contact@cotlet.dev with questions about the MarketMan tools. ## MarketMan API and MCP: questions ### How do I get access? Sign up free at https://cotlet.dev, open MarketMan under Integrations in the console and log in to MarketMan in its Cloud Browser. The trial starts with your first app and needs no card. ### How do I connect MarketMan to ChatGPT or Claude? Sign up at cotlet.dev, log in to MarketMan 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 MarketMan account through Cotlet, in their phone apps too. ### What can ChatGPT do in MarketMan? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in MarketMan: draft the weekly supplier order; flag items below par; weekly food cost variance report. You ask in plain words, and anything that reaches other people waits for your OK first. ### Do I need the MarketMan API add-on? No. Cotlet works in your own MarketMan login, so it does not use the API Partner key. MarketMan sells Open API Access as an add-on on Starter and Growth and includes it in Enterprise (pricing page, checked 28 Oct 2026). Your user role still decides which locations and orders you can see. ### Will my agent send orders to suppliers by itself? Only if you switch confirmation off. create_purchase_order reaches a supplier, so by default you confirm each call. Reading orders, counts and reports changes nothing. ### Does MarketMan have webhooks? Yes, inside the API: API Partners can register webhooks for order events. They need the same partner key. Without it, run your agent on a schedule, for example a daily list_purchase_orders. ### Does it work with several locations? Yes. Every tool takes a location by its MarketMan name, and you see the locations your MarketMan role sees. Run a report per location, or ask the agent to loop over them. ### Is the MCP server different from the REST API? Only the way in. Both carry the same 11 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with MarketMan? No. Cotlet is independent and not affiliated with MarketMan or Meal Ticket. ### Can I use the MarketMan 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.