Marktplaats MCP vs Woocommerce — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Marktplaats MCP vs Woocommerce
In-depth architectural comparison of the Marktplaats MCP and Woocommerce MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Marktplaats MCP
E-Commerce · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Woocommerce
E-Commerce · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Marktplaats MCP if you need specialized E-Commerce tools running via a local process. Choose Woocommerce if your workspace requires E-Commerce integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Marktplaats MCP when:
You need dedicated capabilities in the E-Commerce domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Search Marktplaats.nl and 2dehands.be, Filter by text, category, price, condition, distance, and recency, Retrieve full listing details and photos.
Search Marktplaats.nl and 2dehands.be, the Dutch and Belgian second-hand marketplaces. Listings with price, condition and distance filters, full ad details, seller verification and reviews, categories, and new-listing monitoring. No account or API key needed. Install via uvx marktplaats-mcp.
WooCommerce MCP Pack — wraps the WooCommerce REST API v3
Marktplaats MCP is categorized under E-Commerce and uses a local stdio subprocess. In contrast, Woocommerce belongs to E-Commerce using local stdio subprocess. Select Marktplaats MCP when you need capabilities focused on e-commerce and Woocommerce when you require tools for e-commerce.
List products from a WooCommerce store using Basic auth (consumer key + secret). Returns product IDs, names, prices, stock status, and type. Supports per_page (max 100) and page for pagination.
woo_get_product
Fetch a single WooCommerce product by numeric ID. Returns full details including name, description, price, categories, attributes, and stock quantity.
woo_list_orders
List WooCommerce orders, optionally filtered by status (pending, processing, on-hold, completed, cancelled, refunded, failed). Returns order IDs, totals, customer info, and line items.
woo_get_order
Fetch a single WooCommerce order by numeric ID. Returns full order details including line items, customer billing/shipping, payment method, totals, and current status.
woo_list_customers
List customers registered in a WooCommerce store. Returns customer IDs, names, emails, and order counts. Supports per_page (max 100) and page for pagination.