woocommerce-mcp is a small read-only Model Context Protocol (MCP) server for WordPress and WooCommerce. It lets Claude or any MCP client answer questions about a live store based on the official REST API, covering products, orders, sales, and blog posts. The overall design is fully read-only: the server does not create, edit, or delete anything in the store, and no plugin needs to be installed on the store; instead, it communicates directly with the existing WordPress/WooCommerce REST endpoints.
Main capabilities Provides read-only WordPress and WooCommerce access through the REST API, including: searching products, getting product details, querying recent orders, getting sales reports, and searching blog posts. The documentation mentions that you can ask it questions such as "What were WooCommerce sales last month?" or "List the 5 most recent orders that are on hold." The search_posts feature can be used against any public WordPress site without a key.
How to use It can be installed from npm (the package name has a scope, because the unscoped woocommerce-mcp name is already locked on the registry). Before use, three environment variables need to be set. Keys need to be created in WooCommerce → Settings → Advanced → REST API → Add key, and granted Read permission. The key is sent over HTTPS to your own store as REST query authentication; the official recommendation is to use HTTPS and grant the key Read access only.
When used in Claude Desktop / Claude Code, it needs to be added to the MCP client configuration (for example, claude_desktop_config.json), after which you can ask Claude questions directly about store data.
Use cases Suitable for scenarios where an AI assistant needs to read live WooCommerce store data (products, orders, sales, posts), such as store operations queries, sales data Q&A, and order status viewing. Because it is fully read-only, it is suitable for users with high data security requirements who do not want AI to modify store content.
Limitations and notes Theserver is read-only and does not support any write operations. It requires Node 18+ (uses the built-in fetch). Logs are output to stderr, so they do not disrupt the stdio MCP protocol on stdout. API errors include the message returned by the store, and credentials are not echoed back. Apart from the above, specific information about pricing, charging model, platform support scope, and so on is not currently provided.
