A side-by-side look at the WordPress MCP and Woocommerce MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose WordPress MCP for e-commerce work over a hosted endpoint; choose Woocommerce MCP for e-commerce as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose WordPress MCP when
You need dedicated capabilities in the E-Commerce domain.
list_ordersRecent orders, newest first, optional status filter
sales_reportSales totals for a period (week / month / last_month / year)
search_postsSearch published blog posts (public WP REST API)
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
WordPress MCP is categorized under E-Commerce and uses a remote HTTP/SSE transport. Woocommerce MCP belongs to E-Commerce and uses a local stdio subprocess. Pick WordPress MCP for e-commerce work and Woocommerce MCP for e-commerce.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
WordPress MCP has no declared pricing — check the project's own site. Woocommerce MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add wordpress-mcp-2 and wppoland-woocommerce-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, WordPress MCP has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Woocommerce MCP has 63/100 (Good) with 6 views, 0 installs and 2 GitHub stars.