Official description7 sourcesMCP servers8d ago

wppoland/woocommerce-mcp

Read-only WordPress

View on GitHub ↗Direct link · no redirect page

Config template (adjust for your client)

claude mcp add woocommerce-mcp -- npx -y woocommerce-mcp

A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.

Star count: 2 ★ · wppoland/woocommerce-mcp · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source: collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history: first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score: score 703 · 2 ★ · 7 sources · mcp

FAQ (answers come from our records)

How do I install it?

We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.

Who is it for?

We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.

Who maintains it?

repository wppoland/woocommerce-mcp；first catalogued 2026-10-09；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.

Third-party quality signals

woocommerce-mcp

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

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).
Tools
| Tool | What it does | Needs WooCommerce keys |
|------|--------------|:---:|
| list_products | List / search products (name, sku, price, stock, permalink) | yes |
| get_product | Full details for one product by id | yes |
| list_orders | Recent orders, newest first, optional status filter | yes |
| sales_report | Sales totals for a period (week / month / last_month / year) | yes |
| search_posts | Search published blog posts (public WP REST API) | no |
Everything is **read-only**. The server never creates, edits, or deletes anything in the store.
Install & build
From npm (package name is scoped - the unscoped woocommerce-mcp name is locked on the registry):
From source:
Configure
Set three environment variables:
| Var | Required | Example |
|-----|:---:|---------|
| WP_URL | yes | https://shop.example.com |
| WC_CONSUMER_KEY | for wc_* tools | ck_xxx |
| WC_CONSUMER_SECRET | for wc_* tools | cs_xxx |
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.
Use with Claude Desktop / Claude Code
Add to your MCP client config (e.g. claude_desktop_config.json):
Then ask things like *"What were last month's WooCommerce sales?"* or *"List the 5 most recent orders that are on hold."*
Docs on wppoland.com
- WooCommerce MCP open source (read-only): release and ops guide - npm scope, registry, Glama, and how we ship updates without write tools
Articles (off-site)
Field notes published on DEV (not duplicates of wppoland.com pages):