WooCommerce MCP Server vs MainWP
WooCommerce MCP Server is an MCP server published by AmitGurbani. Marketplaces we read that list it: 1 (Official MCP Registry). MainWP is an MCP server published by mainwp. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  WooCommerce MCP Server |  MainWP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.0 Downloads/month (npm): 390 Downloads/week (npm): 66 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 1.5.1 Downloads/month (npm): 2 010 Downloads/week (npm): 284 Forks (GitHub): 7 Stars (GitHub): 31 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.5.1 Downloads/month (npm): 2 010 Downloads/week (npm): 284 Forks (GitHub): 7 Stars (GitHub): 31 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | WooCommerce MCP Server | MainWP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 2 (worse) | 31 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 7 (better) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (@amitgurbani/mcp-server-woocommerce) | On your machine (@mainwp/mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 12 |
| Licence (differs) | Not stated | GPL-3.0 |
| Repository (differs) | github.com/amitgurbani/mcp-server-woocommerce | github.com/mainwp/mainwp-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
WooCommerce MCP Server
101 tools for WooCommerce store management with field filtering and guided prompts.
MainWP
Manage WordPress sites in MainWP from AI tools, with approval before destructive changes by default.
How to run each
WooCommerce MCP Server As a local MCP server: npm package
claude mcp add --transport stdio mcp-server-woocommerce -- npx -y @amitgurbani/mcp-server-woocommerceMainWP As a local MCP server: npm package
claude mcp add --env "MAINWP_APP_PASSWORD=<YOUR_MAINWP_APP_PASSWORD>" --env "MAINWP_URL=<YOUR_MAINWP_URL>" --env "MAINWP_USER=<YOUR_MAINWP_USER>" --transport stdio mainwp-mcp -- npx -y @mainwp/mcpRequires: MAINWP_APP_PASSWORD (secret), MAINWP_URL, MAINWP_USER
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of WooCommerce MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: WooCommerce MCP Server · What it can do: MainWP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.