Best MCP Servers for Ecommerce: Shopify, WooCommerce, Amazon, eBay & More Compared

01 The pick: YosefHayim's ebay-mcp is the best all-around ecommerce MCP server

Read from GitHub push-activity data (pushed_at) on 2026-07-25 and 2026-07-26, eight of the ten community MCP servers in this ecommerce cohort haven't been touched in over 90 days — the oldest, boldcommerce-magento2-mcp, since 2025-04-22 — and only two are current: amazon-sp-mcp (2026-06-30) and YosefHayim's ebay-mcp (2026-07-19), which is the best all-around pick here on the strength of that freshness plus a 298-tool surface, an MIT licence, and 105 GitHub stars. It is not the right choice for every seller, though: if you run a Shopify, WooCommerce, Magento, BigCommerce, Etsy, Amazon, Printful or Recharge store, the platform-specific runner-up in section 05 is the better install, and ebay-mcp's own read-only mode has a real gap covered below.

02 How we compared them

This cohort is the ten community ecommerce MCP servers queued for this page: geli2001-shopify-mcp, iosdevsk-mcp-for-woocommerce, techspawn-woocommerce-mcp, boldcommerce-magento2-mcp, etugrand-bigcommerce-api-mcp, aserper-etsy-mcp, amazon-sp-mcp, printful-mcp, recharge-storefront-api-mcp and yosefhayim-ebay-mcp. For each one we read the repository source directly rather than trusting the README: tool registration files, auth/session handling code, and the actual GraphQL or REST calls each tool issues. That source read happened on 2026-07-25; GitHub repo metadata (stars, forks, open issues, licence, last commit on the default branch) and npm registry data were re-read on 2026-07-26 — this is the public record and source read on 2026-07-26 that every figure below traces back to. Where a platform ships its own first-party MCP server or documentation, we checked that too, because a community server should be judged against what the vendor already offers, not in isolation. Nothing here was run, called or timed — no MCP handshake exists in this data, and no server was invoked. What follows is what the source and the public record show.

03 The shortlist compared

Every column below is filled for every candidate, including the #1 pick, using the same units. Two servers ship no LICENSE file in their repository as of the source read, so licence is marked n/a rather than assumed permissive.

04 ebay-mcp (YosefHayim): why it wins

ebay-mcp is the freshest server in the cohort — last commit 2026-07-19, days before this page's public record and source read on 2026-07-26 — and the largest by tool surface: counting defineTool({ call sites across its 14 category files gives 298 registered tools (account, analytics, browse, communication, connector, developer, fulfillment, inventory, marketing, metadata, other, taxonomy, tokenManagement, trading), far past the roughly two dozen the README enumerates. It runs on 105 GitHub stars, 49 forks, 2 open issues and an MIT licence, and its own eBay OAuth model documents an exact, checkable rate-limit cliff: a user token gives 10,000–50,000 requests/day, and the client-credentials fallback drops that to 1,000/day. It also ships runtime tool gating (list_ebay_tools, enable_ebay_tools, disable_ebay_tools) plus an EBAY_MCP_TOOLS family filter, so a deployment can advertise a subset of those 298 tools instead of all of them.

The gap: YosefHayim's EBAY_READ_ONLY mode is not a behavioural guarantee. For any tool that carries no readOnlyHint/destructiveHint annotation, admission falls back to matching the tool's name against a hard-coded write-verb pattern and read-verb pattern (src/mcp/readOnlyFilter.ts:30-31), with a default-deny fallthrough decided at src/mcp/readOnlyFilter.ts:49-63. The file's own header concedes this fallback exists because many inventory and fulfillment endpoints ship unannotated — so on a 298-tool catalogue, "read-only" is a naming convention as much as a code guarantee. Unconfigured installs also advertise the full 298-tool set at handshake, since EBAY_MCP_TOOLS defaults to "all" (src/config/toolFamilies.ts:44-47). Installation is npx ebay-mcp (npm ebay-mcp@1.14.1, published 2026-07-19), followed by a setup wizard:

npx ebay-mcp
npm run setup

eBay itself ships a first-party MCP, npm-public-api-mcp, but it is a small passthrough with 11 stars and no marketing pushing it, so a community server carrying the SERP is expected rather than a sign the platform is neglected.

05 Runners-up and when each beats the winner

Unless you run one of the platforms below, ebay-mcp's freshness and tool depth make it the stronger general pick. But eBay's server cannot touch a Shopify, WooCommerce, Magento, BigCommerce, Etsy, Amazon, Printful or Recharge store, so platform sellers should install their own server instead.

• Unless you run Shopify — then geli2001-shopify-mcp, which covers Admin-side product, order and customer writes that Shopify's own first-party MCPs don't reach. It has a real gap of its own: get-products hard-codes variants(first: 5) and media(first: 1) with no pageInfo on either sub-connection, and get-orders hard-codes lineItems(first: 10) — both truncate silently (src/tools/getProducts.ts:74,87; src/tools/getOrders.ts:104).
• Unless you run WooCommerce — then WooCommerce's own core MCP integration is the right default for most stores; between the two community options, iosdevsk-mcp-for-woocommerce is read-only by tool type but its run_api_function forwards any GET route — including /wp/v2/users — behind only is_user_logged_in() and a five-substring denylist, not an allowlist (includes/Tools/McpRestApiCrud.php:100-102,123,141-166,174-184). techspawn-woocommerce-mcp, meanwhile, is not an MCP server at all: it's a raw JSON-RPC line reader over stdin with axios as its only runtime dependency, and it answers an MCP initialize handshake with Unknown method: initialize (src/index.ts:1812-1861; package.json:10-12).
• Unless you run Magento — then boldcommerce-magento2-mcp, the only server here with revenue-analytics tools (get_revenue, get_revenue_by_country, get_product_sales). Both revenue tools hard-code currency: 'USD', with an in-source comment admitting "This should be dynamically determined from the store configuration" (mcp-server.js:911, :1228) — a real problem on any non-USD store.
• Unless you run Amazon — then amazon-sp-mcp, entirely read-only across 14 tools with unusually deep FBA-fee and storage-fee coverage. Its get_orders tool returns an 11-key projection that drops buyer info, shipping address and marketplace id, and stops after a hard-coded maxPages = 20 with no nextToken input in its schema to resume (src/tools/orders.ts:85,114,130-142,7-21).
• Unless you run Etsy — then aserper-etsy-mcp, with full shop-operating coverage including taxonomy and ledger tools most integrations skip. Its OAuth flow requests all 20 Etsy scopes by default — including listings_d, billing_r, cart_w, favorites_w and recommend_w — even though no registered tool module uses cart, favorites, recommendation or billing scopes (src/index.ts:24-30).
• Unless you run Printful — then printful-mcp, the only print-on-demand server in this cohort. Its printful_confirm_order tool — the call that charges the order and starts production — takes only order_id, carries no idempotency key, and returns failures as the plain string "Error: <message>" inside a successful MCP result, with no isError flag set anywhere in the package (src/printful_mcp/tools/orders.py:132-149).
• Unless you run Recharge subscriptions — then recharge-storefront-api-mcp, the only server here with subscription lifecycle tools like swap_subscription and skip_gift_subscription_charge. Its README documents 87 tools in 16 categories, but the source registers 77 across 15 modules, and the entire eight-tool "Authentication" category the README describes has no corresponding source file, import or registration anywhere (src/tools/index.js:5-36).

06 What we'd skip and why

etugrand-bigcommerce-api-mcp is the one to skip: three tools total (get_all_products, get_all_customers, get_all_orders), all read-only list endpoints with no single-record fetch and no writes, 5 GitHub stars, no LICENSE file in the repository, and no commit since 2025-09-09. BigCommerce's own first-party MCP only serves developer documentation rather than operating a live store, so the honest read is that BigCommerce has no good MCP yet — this entry is included for transparency about that gap, not as a recommendation to install it.

For most ecommerce-assistant builds, YosefHayim's ebay-mcp remains the strongest general pick in this cohort on freshness (2026-07-19), tool depth (298 tools) and licence terms (MIT) — with the read-only-mode caveat above — while Shopify, WooCommerce, Magento, Amazon, Etsy, Printful and Recharge sellers should reach for their platform-specific runner-up instead.

07 Frequently asked questions

What is the best MCP server for ecommerce overall?

YosefHayim's ebay-mcp, based on a 2026-07-19 last commit (the most recent in this cohort), 298 registered tools, and an MIT licence — read from the public record and source on 2026-07-26.

Is ebay-mcp's read-only mode safe to rely on?

Not fully. EBAY_READ_ONLY falls back to matching a tool's name against write/read regex patterns whenever the tool has no readOnlyHint or destructiveHint annotation (src/mcp/readOnlyFilter.ts:30-31,49-63), and the source's own comments admit many inventory/fulfillment tools are unannotated.

Which MCP server should a Shopify store use instead of ebay-mcp?

geli2001-shopify-mcp, which covers Admin API product, order and customer operations that Shopify's own first-party MCP surfaces don't reach — though its get-products and get-orders tools silently truncate variants, images and line items past small hard-coded limits (src/tools/getProducts.ts:74,87; src/tools/getOrders.ts:104).

Is there a good MCP server for BigCommerce?

Not yet. etugrand-bigcommerce-api-mcp offers only 3 read-only list tools, has no LICENSE file, and has had no commit since 2025-09-09; BigCommerce's own first-party MCP only serves developer documentation, not live store data.

Why does staleness matter for an ecommerce MCP server?

Read from GitHub on 2026-07-25/26, 8 of the 10 servers in this cohort have gone over 90 days without a commit — the oldest, boldcommerce-magento2-mcp, since 2025-04-22 — meaning most of these projects are not being actively maintained against platform API changes.