[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.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)

# WooCommerce API and MCP server

> Yes. WooCommerce has a full REST API (wc/v3) for orders, products, customers, coupons, refunds and reports, and a store owner creates consumer keys for it per store (checked 16 Oct 2026). Its official MCP server is a developer preview, off by default, and its built-in abilities cover only products and orders.

Open-source e-commerce plugin for WordPress: orders, products, customers, coupons and refunds in a store you host yourself.

## What is the WooCommerce API?

Cotlet's WooCommerce API exposes 11 endpoints for your own WooCommerce account: list orders, get order, list products, list customers, list coupons, get sales report, update order status, add order note, create refund, create coupon and update product. The list_orders endpoint returns orders with status, total, customer and date, filtered by status, date, customer or product. Each endpoint takes simple JSON inputs like status, limit or page and works both as an operation of the woocommerce_read or woocommerce_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas.md)
- **Endpoints:** 11 (6 read, 5 write)
- **Updated:** 2026-10-22

Yes. Cotlet is a hosted MCP server and REST API for WooCommerce with 11 endpoints (6 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does WooCommerce have an official API?

Yes. WooCommerce has a full REST API (wc/v3) for orders, products, customers, coupons, refunds and reports, and a store owner creates consumer keys for it per store (checked 16 Oct 2026). Its official MCP server is a developer preview, off by default, and its built-in abilities cover only products and orders.

| Task | WooCommerce official | Cotlet |
|---|---|---|
| List and read orders | Yes: REST API and the MCP preview | Yes |
| Update order status | Yes: REST API and the MCP preview | Yes |
| Add an order note | Partly: REST API only; the MCP preview lists no note ability | Yes |
| Create a refund | Partly: REST API only; the MCP preview has no refund ability | Yes |
| Create a coupon | Partly: REST API only; the MCP preview has no coupon ability | Yes |
| Update a product price or stock | Yes: REST API and the MCP preview | Yes |
| Read customers | Partly: REST API only; the MCP preview has no customer ability | Yes |
| Pull a sales report | Partly: REST API only; the MCP preview has no report ability | Yes |

Sources: [WooCommerce REST API documentation (wc/v3)](https://woocommerce.github.io/woocommerce-rest-api-docs/), [WooCommerce Docs: REST API keys](https://woocommerce.com/document/woocommerce-rest-api/), [WooCommerce developer blog: Call for testing, WooCommerce MCP (beta)](https://developer.woocommerce.com/2025/11/03/call-for-testing-woocommerce-mcp-beta/), [WooCommerce: WooCommerce MCP (developer preview, April 2026)](https://woocommerce.com/posts/woocommerce-mcp/)

## For AI agents

```text
Yes. WooCommerce has a full REST API (wc/v3) for orders, products, customers, coupons, refunds and reports, and a store owner creates consumer keys for it per store (checked 16 Oct 2026). Its official MCP server is a developer preview, off by default, and its built-in abilities cover only products and orders.
Cotlet provides a hosted MCP server and REST API for WooCommerce: 11 tools (6 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=woocommerce, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    woocommerce_read, woocommerce_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/woocommerce, each operation at its own route, e.g. PATCH /api/v1/woocommerce/products/{product_id}
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_orders, get_order, list_products, list_customers, list_coupons, get_sales_report, update_order_status, add_order_note, create_refund, create_coupon, update_product
Confirm      update_order_status, add_order_note, create_refund, create_coupon, update_product (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/woocommerce-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=woocommerce, requests WooCommerce in the Cotlet console and creates an API key there.
2. The user signs in to WooCommerce once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables WooCommerce for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted WooCommerce server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to WooCommerce in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get WooCommerce only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no WooCommerce login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following WooCommerce's terms; Cotlet is not affiliated with WooCommerce.
```

## What can an AI agent do in WooCommerce?

Cotlet is best for WooCommerce store owners and agencies who want their AI agent to complete orders, issue refunds, create coupons and report sales without running or fixing a server.

- **[Mark shipped orders as completed](https://cotlet.dev/integrations/woocommerce-api-mcp-server/mark-orders-completed.md)** (runs: daily): "List the processing orders in my WooCommerce store. For every order that has a tracking number in its notes, set the status to completed. Leave the rest alone and tell me why." → `list_orders`, `get_order`, `update_order_status`
- **[Refund orders from a support list](https://cotlet.dev/integrations/woocommerce-api-mcp-server/refund-orders-from-a-list.md)**: "Order 1042 arrived damaged: refund the ceramic mug, 22.00, through the payment gateway, then add a private note with the reason. Tell me the order status afterwards." → `get_order`, `create_refund`, `add_order_note`
- **[Create single-use coupon codes](https://cotlet.dev/integrations/woocommerce-api-mcp-server/create-single-use-coupons.md)**: "Create one 15% coupon for each email on this list, valid for one use only and until 30 November. Name them SPRING- plus four random characters and give me the list of codes." → `list_coupons`, `create_coupon`
- **Send a weekly sales report** (runs: weekly): "Every Monday at 8:00, pull last week's sales report for my WooCommerce store and list the orders with a refund. Send me net sales, orders, items, refunds and coupons used in five lines." → `get_sales_report`, `list_orders`
- **Put products on sale and restock**: "Set the sale price of every published product in the Summer category to 20% below its regular price, and tell me which products are low on stock." → `list_products`, `update_product`

## Can WooCommerce automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a WooCommerce connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to mark shipped orders as completed, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/woocommerce/orders. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/woocommerce/orders with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 11 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to WooCommerce.

### list_orders

Orders with status, total, customer and date, filtered by status, date, customer or product. Access: read. REST: `GET /api/v1/woocommerce/orders`. MCP: `woocommerce_read → list_orders`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | any, pending, processing, on-hold, completed, cancelled, refunded or failed. Default: any. |
| `after` | datetime | no | Only orders created after this date. |
| `before` | datetime | no | Only orders created before this date. |
| `customer_id` | integer | no | Only orders of this customer, from list_customers. |
| `product_id` | integer | no | Only orders that contain this product, from list_products. |
| `limit` | integer | no | Results per page. Default: 10. |
| `page` | integer | no | Page number, starting at 1. Default: 1. |

Lists orders, newest first. Filter by status to build a queue such as Processing, or by date to see what came in since your last check. The status filter takes any, pending, processing, on-hold, completed, cancelled, refunded or failed; the default is any. Each page returns total and total_pages so an agent can read the whole queue. Orders are visible to the Administrator and Shop Manager roles.

Example response:

```json
{
  "orders": [
    {
      "order_id": 1043,
      "number": "1043",
      "status": "processing",
      "total": "34.00",
      "currency": "USD",
      "customer_name": "Maria Costa",
      "payment_method_title": "Credit card",
      "date_created": "2026-10-14T16:20:00Z",
      "item_count": 2
    }
  ],
  "total": 14,
  "total_pages": 2
}
```

### get_order

One order with line items, shipping, payment method, refunds and notes. Access: read. REST: `GET /api/v1/woocommerce/orders/{order_id}`. MCP: `woocommerce_read → get_order`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | integer | yes | Order ID from list_orders. |

Returns one order in full: the line items with their IDs, the shipping and fee lines, the payment method, the refunds already made on it and its notes. Use the line_item_id values with create_refund. Customer name and address are included, which is personal data, so the call needs a role that can see orders.

Example response:

```json
{
  "order_id": 1042,
  "status": "processing",
  "currency": "USD",
  "payment_method_title": "Credit card",
  "line_items": [
    {
      "line_item_id": 7001,
      "product_id": 311,
      "name": "Linen tote bag",
      "quantity": 2,
      "total": "28.00"
    },
    {
      "line_item_id": 7002,
      "product_id": 318,
      "name": "Ceramic mug",
      "quantity": 1,
      "total": "22.00"
    }
  ],
  "shipping_total": "8.00",
  "total": "58.00",
  "refunds": [],
  "notes": [
    {
      "note_id": 9120,
      "note": "Tracking number 1Z999AA10123456784",
      "customer_note": false
    }
  ]
}
```

### list_products

Products with price, sale price, stock and status, filtered by search, category, status or SKU. Access: read. REST: `GET /api/v1/woocommerce/products`. MCP: `woocommerce_read → list_products`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Text in the product name or description. |
| `sku` | string | no | Exact SKU. |
| `category` | integer | no | Product category ID. |
| `status` | enum | no | any, draft, pending, private or publish. Default: any. |
| `on_sale` | boolean | no | true returns only products on sale. |
| `limit` | integer | no | Results per page. Default: 10. |
| `page` | integer | no | Page number, starting at 1. Default: 1. |

Lists products with their regular and sale price, stock quantity and publication status. Filter by a search term, category, status or SKU, or show only products on sale. Use it to find the product_id for update_product and to check stock after a refund or a sale. Variations are returned on the product that owns them.

Example response:

```json
{
  "products": [
    {
      "product_id": 311,
      "name": "Linen tote bag",
      "sku": "TOTE-LIN-01",
      "status": "publish",
      "regular_price": "14.00",
      "sale_price": "",
      "on_sale": false,
      "manage_stock": true,
      "stock_quantity": 40
    }
  ],
  "total": 1,
  "total_pages": 1
}
```

### list_customers

Customers with email, order count and total spent. Contains personal data. Access: read. REST: `GET /api/v1/woocommerce/customers`. MCP: `woocommerce_read → list_customers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Part of a name or an email. |
| `limit` | integer | no | Results per page. Default: 10. |
| `page` | integer | no | Page number, starting at 1. Default: 1. |

Lists registered customers with their email, number of orders and total spent. Search by name or email. The result contains personal data of your customers, so it is returned only to a role that can see orders, and your agent should not forward it to tools you do not trust. Guest buyers appear on their orders, not here.

Example response:

```json
{
  "customers": [
    {
      "customer_id": 58,
      "name": "Jordan Lee",
      "email": "jordan.lee@example.com",
      "orders_count": 3,
      "total_spent": "142.00"
    }
  ],
  "total": 1,
  "total_pages": 1
}
```

### list_coupons

Coupons with code, discount, usage count, limit and expiry date. Access: read. REST: `GET /api/v1/woocommerce/coupons`. MCP: `woocommerce_read → list_coupons`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `code` | string | no | Exact coupon code. |
| `search` | string | no | Text in the coupon code. |
| `limit` | integer | no | Results per page. Default: 10. |
| `page` | integer | no | Page number, starting at 1. Default: 1. |

Lists coupons with the code, discount type, amount, how many times each was used, its usage limit and its expiry date. Search by text or look up an exact code before you create one. Coupon codes are not case-sensitive in WooCommerce.

Example response:

```json
{
  "coupons": [
    {
      "coupon_id": 2201,
      "code": "welcome10",
      "discount_type": "percent",
      "amount": "10",
      "usage_count": 41,
      "usage_limit": 500,
      "date_expires": "2026-12-31"
    }
  ],
  "total": 1,
  "total_pages": 1
}
```

### get_sales_report

Sales totals for a period: gross and net sales, orders, items, tax, shipping, refunds and coupons used. Access: read. REST: `GET /api/v1/woocommerce/sales-report`. MCP: `woocommerce_read → get_sales_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `period` | enum | no | week, month, last_month or year. |
| `date_min` | date | no | Start date, YYYY-MM-DD. Use with date_max. |
| `date_max` | date | no | End date, YYYY-MM-DD. |

Returns the store's sales report for one period, with the totals and a day-by-day list. Pass period for week, month, last_month or year, or a custom range with date_min and date_max in YYYY-MM-DD. Without either, the report covers the current day only. The WooCommerce Analytics screens count by a Date Type setting (created, paid or completed, default Date Paid), so numbers read there can differ from a report built on another date.

Example response:

```json
{
  "period": {
    "date_min": "2026-10-05",
    "date_max": "2026-10-11"
  },
  "total_sales": "1860.00",
  "net_sales": "1744.00",
  "average_sales": "249.14",
  "total_orders": 31,
  "total_items": 53,
  "total_tax": "92.00",
  "total_shipping": "88.00",
  "total_refunds": 2,
  "total_discount": 3,
  "totals": [
    {
      "date": "2026-10-05",
      "sales": "310.00",
      "orders": 5,
      "items": 9
    },
    {
      "date": "2026-10-06",
      "sales": "245.00",
      "orders": 4,
      "items": 7
    },
    {
      "date": "2026-10-07",
      "sales": "280.00",
      "orders": 5,
      "items": 8
    },
    {
      "date": "2026-10-08",
      "sales": "190.00",
      "orders": 3,
      "items": 5
    },
    {
      "date": "2026-10-09",
      "sales": "260.00",
      "orders": 4,
      "items": 7
    },
    {
      "date": "2026-10-10",
      "sales": "330.00",
      "orders": 6,
      "items": 10
    },
    {
      "date": "2026-10-11",
      "sales": "245.00",
      "orders": 4,
      "items": 7
    }
  ]
}
```

### update_order_status

Set an order to pending, processing, on-hold, completed, cancelled, refunded or failed. Access: write, asks the user first. REST: `PATCH /api/v1/woocommerce/orders/{order_id}/status`. MCP: `woocommerce_write → update_order_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | integer | yes | Order ID from list_orders. |
| `status` | enum | yes | pending, processing, on-hold, completed, cancelled, refunded or failed. |

Changes the status of one order. Allowed values are pending, processing, on-hold, completed, cancelled, refunded and failed. WooCommerce sends the customer an email when an order is completed, and Cancelled returns line-item stock when inventory management is on. Setting Cancelled or Refunded does not refund the customer; use create_refund for that. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "order_id": 1044,
  "previous_status": "processing",
  "status": "completed",
  "date_modified": "2026-10-15T08:02:00Z"
}
```

### add_order_note

Add a private note for your team or a note the customer sees and is emailed. Access: write, asks the user first. REST: `POST /api/v1/woocommerce/orders/{order_id}/note`. MCP: `woocommerce_write → add_order_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | integer | yes | Order ID from list_orders. |
| `note` | string | yes | The note text. |
| `customer_note` | boolean | no | true shows the note to the customer and notifies them. Default: false. |

Adds a note to an order. By default the note is private and only staff see it. With customer_note set to true, WooCommerce shows the note to the customer and notifies them. Notes cannot be edited by this tool, so a wrong customer note stays on the order. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "note_id": 9131,
  "order_id": 1043,
  "note": "Tracking number 1Z999AA10123456791",
  "customer_note": true,
  "date_created": "2026-10-15T08:03:00Z"
}
```

### create_refund

Refund an amount or specific line items of an order, through the payment gateway or as a manual record. Access: write, asks the user first. REST: `POST /api/v1/woocommerce/orders/{order_id}/refunds`. MCP: `woocommerce_write → create_refund`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | integer | yes | Order ID from list_orders. |
| `amount` | string | yes | Refund amount in the order currency, for example "22.00". |
| `reason` | string | no | Reason stored with the refund. |
| `line_items` | array | no | Items to refund: objects with line_item_id from get_order, quantity and amount. |
| `api_refund` | boolean | no | true refunds through the payment gateway, false only records it. Default: true. |

Creates a refund on one order for the amount you give, optionally tied to line items from get_order. With api_refund true, the default, WooCommerce uses the payment gateway API to send the money back, which needs a compatible gateway; with false it only records the refund and you send the money yourself. A refund below the full order value is a partial refund and the order status does not change; a full refund sets it to Refunded. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "refund_id": 1051,
  "order_id": 1042,
  "amount": "22.00",
  "reason": "Damaged in transit",
  "refunded_via": "payment gateway",
  "order_status": "processing"
}
```

### create_coupon

Create a coupon with a discount type, amount, expiry date, usage limits and allowed emails. Access: write, asks the user first. REST: `POST /api/v1/woocommerce/coupons`. MCP: `woocommerce_write → create_coupon`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `code` | string | yes | Coupon code. Not case-sensitive. |
| `amount` | string | yes | Discount as a number, for example "15", also for percentages. |
| `discount_type` | enum | no | percent, fixed_cart or fixed_product. Default: fixed_cart. |
| `date_expires` | date | no | Last day the coupon works, YYYY-MM-DD. |
| `usage_limit` | integer | no | Total uses across all customers. |
| `usage_limit_per_user` | integer | no | Uses allowed per customer. |
| `minimum_amount` | string | no | Minimum spend for the coupon to apply. |
| `free_shipping` | boolean | no | true makes the coupon work with free shipping. Default: false. |
| `email_restrictions` | array | no | Billing emails allowed to use the coupon; wildcards such as *@gmail.com work. |

Creates one coupon. The code is required and not case-sensitive. discount_type is percent, fixed_cart or fixed_product, the default is fixed_cart, and amount is a number given as a string, also for percentages. Add date_expires, usage limits, a minimum or maximum spend, and email_restrictions to tie the code to customers. A coupon gives money off at checkout, so it is treated as reaching your customers. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "coupon_id": 2210,
  "code": "SPRING-JL3K",
  "discount_type": "percent",
  "amount": "15",
  "date_expires": "2026-11-30",
  "usage_limit": 1,
  "usage_limit_per_user": 1,
  "email_restrictions": [
    "jordan.lee@example.com"
  ]
}
```

### update_product

Change a product name, status, price, sale price or stock. Access: write, asks the user first. REST: `PATCH /api/v1/woocommerce/products/{product_id}`. MCP: `woocommerce_write → update_product`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `product_id` | integer | yes | Product ID from list_products. |
| `name` | string | no | New product name. |
| `status` | enum | no | draft, pending, private or publish. |
| `regular_price` | string | no | Regular price, for example "14.00". |
| `sale_price` | string | no | Sale price; an empty string ends the sale. |
| `manage_stock` | boolean | no | true tracks the stock quantity. |
| `stock_quantity` | integer | no | Units in stock. Needs manage_stock. |

Updates one product. Change the regular price or the sale price, switch the status between draft, pending, private and publish, or set the stock quantity with manage_stock. Prices are strings in the store currency, and an empty sale_price ends the sale. A published product changes on your storefront at once, so the call is treated as reaching your customers. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "product_id": 311,
  "name": "Linen tote bag",
  "status": "publish",
  "regular_price": "14.00",
  "sale_price": "11.20",
  "on_sale": true,
  "manage_stock": true,
  "stock_quantity": 40
}
```

## How do I connect WooCommerce to Claude Code, Codex or Cursor?

Connecting WooCommerce takes three steps: sign up, sign in to WooCommerce once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect WooCommerce to your agent.

1. **Create an account** Sign up and add WooCommerce in the console. Your API key is there too.

2. **Sign in to WooCommerce in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to WooCommerce there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the WooCommerce tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
List the processing orders in my WooCommerce store. For every order that has a tracking number in its notes, set the status to completed. Leave the rest alone and tell me why.
```

### Call WooCommerce from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/woocommerce with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X PATCH https://cotlet.dev/api/v1/woocommerce/products/311 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"sale_price":"11.20"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "product_id": 311,
  "name": "Linen tote bag",
  "status": "publish",
  "regular_price": "14.00",
  "sale_price": "11.20",
  "on_sale": true,
  "manage_stock": true,
  "stock_quantity": 40
}
```

## Why use Cotlet for WooCommerce?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to WooCommerce yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When WooCommerce changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect WooCommerce to Cotlet?

Yes. You sign in to WooCommerce yourself, in your own Cloud Browser, and we never save your password. Your agents only get WooCommerce once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official WooCommerce integration?**

No, Cotlet is independent of WooCommerce. WooCommerce's own API is too limited for this work. Cotlet works through your own WooCommerce account, the way you use WooCommerce in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to WooCommerce in your console: your agents lose access at once and you stay signed in. Signing out of WooCommerce in the browser works too, and Reset browser deletes the whole profile.

## Is there a WooCommerce MCP server on GitHub?

Yes. Community WooCommerce MCP servers exist on GitHub, usually maintained by one person, and the REST API is open to anyone with a consumer key. Either way you install, host and fix the connection yourself, one store at a time. Cotlet hosts the same tools for you, and our team keeps them working.

|  | GitHub MCP server or your own REST script | Cotlet |
|---|---|---|
| Setup | Create REST consumer keys under WooCommerce > Settings > Advanced > REST API for every store, then install and configure a server or write the script | Sign up, enter your store's URL, sign in once, add one MCP server or API key |
| Changes in your store or WooCommerce | The official MCP preview may change its APIs before a final release; you or the maintainer adjust the setup | Our team tests it daily and fixes it for you; failed calls are free |
| Your credentials | A consumer key and secret in a config file; each pair is tied to one WordPress user and the secret is shown only once | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| What your store needs | Official MCP: the feature switched on, WordPress 6.9 or newer and a local Node.js proxy; REST: readable permalinks and a key | Nothing to install or switch on in the store |
| Upkeep | You update, monitor and debug it yourself, for every store | Nothing to host or update |
| Where it runs | Your computer or your own server, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time and your hosting | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when WooCommerce changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the WooCommerce API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the WooCommerce API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $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. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own WooCommerce account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to WooCommerce yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get WooCommerce only after you enable it. When WooCommerce signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to WooCommerce, sign out of WooCommerce in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **WooCommerce's terms:** You use your own WooCommerce account and stay responsible for following WooCommerce's terms. Cotlet is independent and not affiliated with WooCommerce. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open WooCommerce in the console and press Request access. Then you create your API key and connect WooCommerce there.

**Do I need to be technical?**

No. You sign in to WooCommerce once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect WooCommerce to Cotlet?**

Yes. You sign in to WooCommerce yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get WooCommerce once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My WooCommerce sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your WooCommerce cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through WooCommerce's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. WooCommerce sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no WooCommerce login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

WooCommerce offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need REST API keys or the WooCommerce MCP preview?**

No. WooCommerce's own routes need consumer keys created under WooCommerce > Settings > Advanced > REST API for every store, and the official MCP server also needs a feature switch and a local proxy. Cotlet works in your store's account after you sign in once, with nothing to install or switch on in the store.

**Which role does my WordPress account need?**

The Administrator or Shop Manager role. WooCommerce shows orders to those roles, and its coupon guide asks for an administrator or shop manager account.

**Can my agent post or send messages in WooCommerce without asking me?**

No. Every call to update_order_status, add_order_note, create_refund, create_coupon or update_product waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the WooCommerce API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/woocommerce from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.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 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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.