This is a read-only MCP server for WordPress + WooCommerce that lets you query store data and blog content via the official REST APIs. It never creates, modifies, or deletes any data.
list_products: Search and browse WooCommerce products by name/SKU or filter by status (draft, pending, private, publish). Returns product ID, name, SKU, price, stock status, and permalink. Supports pagination.
get_product: Retrieve full details for a single WooCommerce product by its ID.
list_orders: View recent WooCommerce orders (newest first), optionally filtered by status (pending, processing, on-hold, completed, cancelled, refunded, failed). Supports pagination.
sales_report: Get WooCommerce sales totals — gross sales, order count, and items sold — for a given period (week, month, last_month, or year).
search_posts: Search published WordPress blog posts via the public WordPress REST API (no WooCommerce credentials required). Supports pagination.
Provides read-only access to WooCommerce store data: list/search products, get product details, list orders, and retrieve sales reports.
Allows searching published blog posts via the public WordPress REST API. No authentication required.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@woocommerce-mcp What were last month's sales totals?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A small, read-only Model Context Protocol server for WordPress + WooCommerce. It lets Claude (or any MCP client) answer questions about a live store — products, orders, sales, and blog posts — over the official REST APIs. No writes, no plugins to install on the store: it talks to the existing WordPress/WooCommerce REST endpoints.
Built and maintained by WPPoland, a senior WordPress developer working with WordPress since 2006. If you need this wired into a real store stack, we build WooCommerce ERP and API integrations and enterprise e-commerce architecture (headless, integrations, AI-ready data).
Tool | What it does | Needs WooCommerce keys |
| List / search products (name, sku, price, stock, permalink) | yes |
| Full details for one product by id | yes |
| Recent orders, newest first, optional status filter | yes |
| Sales totals for a period (week / month / last_month / year) | yes |
| Search published blog posts (public WP REST API) | no |
Everything is read-only. The server never creates, edits, or deletes anything in the store.
Related MCP server: WooCommerce MCP Server by CData
From npm (package name is scoped - the unscoped woocommerce-mcp name is locked on the registry):
npm install -g @wppoland/woocommerce-mcp
# or: npx @wppoland/woocommerce-mcpFrom source:
git clone https://github.com/wppoland/woocommerce-mcp.git
cd woocommerce-mcp
npm install
npm run buildSet three environment variables:
Var | Required | Example |
| yes |
|
| for |
|
| for |
|
Create the WooCommerce keys in WooCommerce → Settings → Advanced → REST API → Add key with Read permission. search_posts works without keys against any public WordPress site.
The keys are sent to your own store over HTTPS as REST query auth. Use HTTPS, and give the key Read access only.
Add to your MCP client config (e.g. claude_desktop_config.json):
{
"mcpServers": {
"woocommerce": {
"command": "node",
"args": ["/absolute/path/to/woocommerce-mcp/dist/index.js"],
"env": {
"WP_URL": "https://shop.example.com",
"WC_CONSUMER_KEY": "ck_xxx",
"WC_CONSUMER_SECRET": "cs_xxx"
}
}
}
}Then ask things like "What were last month's WooCommerce sales?" or "List the 5 most recent orders that are on hold."
WooCommerce MCP open source (read-only): release and ops guide - npm scope, registry, Glama, and how we ship updates without write tools
Field notes published on DEV (not duplicates of wppoland.com pages):
A read-only MCP server for WooCommerce: what AI agents actually need from a store
Syncing a wholesaler's API into WooCommerce without overselling or melting the server
Twelve months after migrating wppoland.com from WordPress to Astro on Cloudflare Pages
Show HN: discussion
npm run check # builds, then asserts all five tools register (no network/credentials needed)Node 18+ (uses the built-in fetch).
Logs go to stderr so they never corrupt the stdio MCP protocol on stdout.
API errors are surfaced with the store's message; credentials are never echoed.
MIT © WPPoland
WooCommerce sales totals for a period (week, month, last_month, year). Gross sales, orders, items.
Inputs: period.
Search published WordPress blog posts (public REST API, no WooCommerce keys required).
Inputs: search (required), per_page.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
The two tools serve entirely different purposes: one provides WooCommerce sales reports, the other searches WordPress blog posts. There is zero overlap in functionality, making it impossible to confuse them.
Tool names use different patterns: 'sales_report' is a noun phrase, while 'search_posts' follows a verb_noun pattern. This inconsistency makes the set feel ad hoc rather than systematically named.
With only 2 tools for a 'woocommerce-mcp' server, the count is far too low. While a minimal server could be justified, the expected scope for WooCommerce typically includes many more operations (e.g., products, orders, customers).
The tool surface is severely incomplete for WooCommerce. Key operations like managing products, orders, or customers are entirely missing, and the inclusion of a general WordPress search tool unrelated to e-commerce does not address the core domain.
Federated commerce search across independent WooCommerce merchants. Keyless, read-only MCP server.
MerchantFlow is a hosted, read-only ecommerce analytics MCP server for Shopify and WooCommerce. It gives AI assistants tenant-scoped access to revenue, profit and loss, product and SKU profitability, COGS coverage, fulfillment costs, advertising spend, ROAS, marketing performance, cohorts, LTV, and business valuation across connected commerce and marketing platforms. Connect with OAuth over Streamable HTTP. No local server installation is required.
Hosted WooCommerce MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
WooCommerce MCP server for ChatGPT, Claude and any AI agent: list orders, update order status, create refund, create coupon, update product and get sales report in your own WooCommerce account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to WooCommerce yourself; Cotlet does not store your password and you need no WooCommerce API key. About the official WooCommerce 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). Setup and FAQ: https://cotlet.dev/integrations/woocommerce-api-mcp-server
