MarketMan API and MCP server Let your AI agent watch par levels and draft orders.

ToolWhat it doesAccess

• list_purchase_orders Lists purchase orders of a location by delivery date or sent date. read

  Returns one row per order with the supplier, status, delivery date, number of items and total. Orders come in delivery date order, oldest first. Your role decides which locations you see.

  MCP callmarketman_read → list_purchase_orders

  REST endpointGET https://cotlet.dev/api/v1/marketman/purchase-orders

  Parameters

  Parameters: list_purchase_orders

  Name	Type	Description
  location string required	string	Location name as shown in MarketMan.
  date_from string required	string	First day, YYYY-MM-DD.
  date_to string required	string	Last day, YYYY-MM-DD.
  date_type string	string	delivery or sent. Default delivery.
  status string	string	Filter by sent, pending or approved. Sent means sent to the supplier, pending means received by the supplier, approved means approved by the supplier.

  Example input

  {
    "location": "location",
    "date_from": "date from",
    "date_to": "date to"
  }

  Example response

  {
    "orders": [
      {
        "order_id": "po_41872",
        "supplier": "Fresh Fields Produce",
        "status": "sent",
        "delivery_date": "2026-10-30",
        "items": 12,
        "total": 486.2
      },
      {
        "order_id": "po_41873",
        "supplier": "Lakeside Dairy",
        "status": "approved",
        "delivery_date": "2026-10-31",
        "items": 8,
        "total": 212.4
      }
    ]
  }

• get_purchase_order Returns one purchase order with its lines. read

  Returns the supplier, status, delivery date and every line with item, quantity, unit and price. It does not change the order.

  MCP callmarketman_read → get_purchase_order

  REST endpointGET https://cotlet.dev/api/v1/marketman/orders/{order_id}/purchase-order

  Parameters

  Parameters: get_purchase_order

  Name	Type	Description
  order_id string required	string	Order id from list_purchase_orders.

  Example input

  {
    "order_id": "order_8c41d2"
  }

  Example response

  {
    "order_id": "po_41873",
    "supplier": "Lakeside Dairy",
    "status": "approved",
    "delivery_date": "2026-10-31",
    "lines": [
      {
        "item": "Whole milk",
        "quantity": 6,
        "unit": "case",
        "price": 28.5
      },
      {
        "item": "Butter, unsalted",
        "quantity": 2,
        "unit": "case",
        "price": 20.7
      }
    ],
    "total": 212.4
  }

• list_suppliers Lists the suppliers a location orders from. read

  Returns each supplier with its name and contact email as saved in MarketMan. Use it to group items before you create orders.

  MCP callmarketman_read → list_suppliers

  REST endpointGET https://cotlet.dev/api/v1/marketman/suppliers

  Parameters

  Parameters: list_suppliers

  Name	Type	Description
  location string required	string	Location name as shown in MarketMan.

  Example input

  {
    "location": "location"
  }

  Example response

  {
    "suppliers": [
      {
        "supplier_id": "sup_118",
        "name": "Lakeside Dairy",
        "email": "orders@lakesidedairy.example"
      },
      {
        "supplier_id": "sup_121",
        "name": "Fresh Fields Produce",
        "email": "orders@freshfields.example"
      }
    ]
  }

• create_purchase_order Creates a purchase order for one supplier and sends it. writeasks first

  Creates the order and sends it to the supplier the way MarketMan does when you approve an order. The supplier and your money are affected, and you cannot recall it through Cotlet. It returns the order id, status and total. By default you confirm each call; you can switch that off for this tool.

  MCP callmarketman_write → create_purchase_order

  REST endpointPOST https://cotlet.dev/api/v1/marketman/suppliers/{supplier_id}/purchase-orders

  Parameters

  Parameters: create_purchase_order

  Name	Type	Description
  location string required	string	Location name as shown in MarketMan.
  supplier_id string required	string	Supplier id from list_suppliers.
  delivery_date string required	string	Delivery day, YYYY-MM-DD.
  lines array required	array	Items to order: item_id and quantity in the item unit.
  note string	string	Note for the supplier.

  Example input

  {
    "location": "location",
    "supplier_id": "supplier_8c41d2",
    "delivery_date": "delivery date",
    "lines": "lines"
  }

  Example response

  {
    "order_id": "po_41901",
    "supplier": "Lakeside Dairy",
    "status": "sent",
    "delivery_date": "2026-11-02",
    "items": 2,
    "total": 49.2
  }

ToolWhat it doesAccess

• list_inventory_items Lists the items you order and count, with par level and last count. read

  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.

  MCP callmarketman_read → list_inventory_items

  REST endpointGET https://cotlet.dev/api/v1/marketman/inventory-items

  Parameters

  Parameters: list_inventory_items

  Name	Type	Description
  location string required	string	Location name as shown in MarketMan.
  category string	string	Only items in this category.
  below_par boolean	boolean	Only items whose on-hand quantity is under the par level.

  Example input

  {
    "location": "location"
  }

  Example response

  {
    "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"
      }
    ]
  }

• list_inventory_counts Lists past inventory counts of a location. read

  Returns one row per count with its date, whether it was a full or partial count and the number of items counted. Newest first.

  MCP callmarketman_read → list_inventory_counts

  REST endpointGET https://cotlet.dev/api/v1/marketman/inventory-counts

  Parameters

  Parameters: list_inventory_counts

  Name	Type	Description
  location string required	string	Location name as shown in MarketMan.
  date_from string	string	First day, YYYY-MM-DD.
  date_to string	string	Last day, YYYY-MM-DD.

  Example input

  {
    "location": "location"
  }

  Example response

  {
    "counts": [
      {
        "count_id": "cnt_903",
        "date": "2026-10-26",
        "type": "full",
        "items_counted": 214
      },
      {
        "count_id": "cnt_897",
        "date": "2026-10-19",
        "type": "partial",
        "items_counted": 58
      }
    ]
  }

• set_par_level Sets the par level of one inventory item. write

  Changes the par level of one item and returns the old and new value. It reaches no one and you undo it by setting the old value, so it does not wait for your OK. A lower par level changes what MarketMan suggests next time you order.

  MCP callmarketman_write → set_par_level

  REST endpointPUT https://cotlet.dev/api/v1/marketman/items/{item_id}/par-level

  Parameters

  Parameters: set_par_level

  Name	Type	Description
  location string required	string	Location name as shown in MarketMan.
  item_id string required	string	Item id from list_inventory_items.
  par_level number required	number	New par level in the item unit.

  Example input

  {
    "location": "Harbor Grill",
    "item_id": "inv_2210",
    "par_level": 10
  }

  Example response

  {
    "item_id": "inv_2210",
    "name": "Whole milk",
    "old_par_level": 8,
    "par_level": 10
  }

ToolWhat it doesAccess

• get_actual_vs_theoretical Compares what you used (from counts) with what sales say you should have used. read

  Returns each item with actual usage, theoretical usage and the difference. The dates must be days with a count, so call list_inventory_counts first. Sorted by the largest gap.

  MCP callmarketman_read → get_actual_vs_theoretical

  REST endpointGET https://cotlet.dev/api/v1/marketman/actual-vs-theoretical

  Parameters

  Parameters: get_actual_vs_theoretical

  Name	Type	Description
  location string required	string	Location name as shown in MarketMan.
  date_from string required	string	Start count date, YYYY-MM-DD.
  date_to string required	string	End count date, YYYY-MM-DD.

  Example input

  {
    "location": "location",
    "date_from": "date from",
    "date_to": "date to"
  }

  Example response

  {
    "period": {
      "from": "2026-10-19",
      "to": "2026-10-26"
    },
    "items": [
      {
        "name": "Whole milk",
        "unit": "case",
        "actual": 9,
        "theoretical": 7.5,
        "difference": 1.5
      },
      {
        "name": "Butter, unsalted",
        "unit": "case",
        "actual": 3.5,
        "theoretical": 3.2,
        "difference": 0.3
      }
    ]
  }

• get_menu_profitability Returns cost, price and margin for each menu item. read

  Returns each menu item with its portion cost, selling price, units sold and margin. Lowest margin first.

  MCP callmarketman_read → get_menu_profitability

  REST endpointGET https://cotlet.dev/api/v1/marketman/menu-profitability

  Parameters

  Parameters: get_menu_profitability

  Name	Type	Description
  location string required	string	Location name as shown in MarketMan.
  date_from string required	string	First day, YYYY-MM-DD.
  date_to string required	string	Last day, YYYY-MM-DD.

  Example input

  {
    "location": "location",
    "date_from": "date from",
    "date_to": "date to"
  }

  Example response

  {
    "items": [
      {
        "name": "Seafood linguine",
        "cost": 7.9,
        "price": 17,
        "sold": 64,
        "margin_percent": 53.5
      },
      {
        "name": "House burger",
        "cost": 4.1,
        "price": 14,
        "sold": 212,
        "margin_percent": 70.7
      }
    ]
  }

• list_recipes Lists recipes with their ingredients and portion cost. read

  Returns each recipe with its ingredients, quantities and the cost of one portion. It does not change recipes.

  MCP callmarketman_read → list_recipes

  REST endpointGET https://cotlet.dev/api/v1/marketman/recipes

  Parameters

  Parameters: list_recipes

  Name	Type	Description
  location string required	string	Location name as shown in MarketMan.
  search string	string	Part of a recipe name.

  Example input

  {
    "location": "location"
  }

  Example response

  {
    "recipes": [
      {
        "name": "House burger",
        "portion_cost": 4.1,
        "ingredients": [
          {
            "item": "Ground beef",
            "quantity": 0.25,
            "unit": "lb"
          },
          {
            "item": "Brioche bun",
            "quantity": 1,
            "unit": "each"
          }
        ]
      }
    ]
  }

• list_invoices Lists supplier invoices recorded for a location. read

  Returns each invoice with its supplier, date and total. Newest first. It reads invoices only; it does not upload or edit one.

  MCP callmarketman_read → list_invoices

  REST endpointGET https://cotlet.dev/api/v1/marketman/invoices

  Parameters

  Parameters: list_invoices

  Name	Type	Description
  location string required	string	Location name as shown in MarketMan.
  date_from string required	string	First day, YYYY-MM-DD.
  date_to string required	string	Last day, YYYY-MM-DD.

  Example input

  {
    "location": "location",
    "date_from": "date from",
    "date_to": "date to"
  }

  Example response

  {
    "invoices": [
      {
        "invoice_id": "inv_77120",
        "supplier": "Fresh Fields Produce",
        "date": "2026-10-27",
        "total": 486.2
      },
      {
        "invoice_id": "inv_77094",
        "supplier": "Lakeside Dairy",
        "date": "2026-10-24",
        "total": 198
      }
    ]
  }