WooCommerce MCP server for your AI

Inside your store admin, under WooCommerce → Settings → Advanced → REST API. Generate a key at the Read/Write permission level, then paste the three values the connect form asks for: Store URL, Consumer key and Consumer secret. A Read-only key will still authenticate, but WooCommerce will reject anything that writes — creating products, updating orders, issuing coupons.

No. Authentication is the REST API consumer key/secret pair you generate in WooCommerce, plus the Store URL — no admin username or password is involved. The key is issued by one store, so the connection reaches that store, and you manage it from the same REST API screen where you created it.

Five API modules: Products, Orders, Customers, Reports and Coupons — 25 operations in total, 13 of them read and 12 write. Products is the largest at 9 operations, then Orders at 7, Customers at 4, Reports at 3 and Coupons at 2. Reports also covers system_status, which returns store environment details such as the WooCommerce version, active theme, plugins and database.

15 of the tools load by default so your client's tool list stays short and the model picks well among them. The rest stay searchable and get pulled in when a request needs them. If you would rather have all of them present from the first message, turn on the full catalog for the connection.

Yes, through triggers. Order created, Product created, Customer created, Coupon created and Product category created are polled on a schedule. Order completed, Order cancelled, Order refunded, Order payment failed and Order put on hold run on change detection, as do Product out of stock, Product back in stock, Product put on sale and Product variation added.

Variations belong to a parent variable product, so the agent needs the parent product id before it can call list_product_variations or create_product_variation — usually by running list_products or get_product first. Sizes and colors are variations, not standalone products, which is the detail that trips people up on a bulk price or stock change. Name the parent product in your request and the agent can resolve the id itself.

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Any client that supports a remote Streamable HTTP MCP server — Claude Desktop, Claude Web, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

Loading 25 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 15-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. You can switch a connection to the full catalog at any time.

A tool is something your AI calls — there are 25 here. A trigger is something PopMCP watches for you: 16 WooCommerce events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into WooCommerce.