MCP Ecommerce Platform Profiler

What mcp-ecommerce-platform-profiler MCP server does

The mcp-ecommerce-platform-profiler MCP server accepts a company domain and returns one flat record describing observable ecommerce characteristics. The record can identify platforms such as Shopify, WooCommerce, Magento, BigCommerce, Salesforce Commerce, Squarespace, Wix, PrestaShop, and commercetools. It can also report detected payment providers, subscription indicators, marketplace indicators, estimated catalog size, currencies, and shipping destinations.

Detection results include more than a platform label. The response carries platform confidence and evidence, such as a header or HTML signal, along with the pages read, coverage, fetch status, and whether the result was degraded. Product counts are estimates rather than guaranteed exact totals. The output contains 22 snake_case fields and no nested objects, making it suitable for systems that consume a single row per company.

How it works

The package is a thin client for the Mamba Labs Ecommerce Platform Profiler actor on Apify; detection logic runs in Apify and the actor result is returned to the MCP client. The server performs static reads of the homepage and sitemap. When checkCheckout is enabled, it also reads the public cart page to find providers that may not appear on the homepage. It does not use a browser or submit checkout actions.

By default, product count and payment-provider checks are enabled. Shopify catalog estimates can use the products endpoint, while other estimates use the sitemap. A successful lookup is cached for seven days unless skipCache is set to true. Storefronts returning 403 or 429 can be retried once through a residential exit when escalateOnBlock is enabled; disabling that option makes the request fail fast.

Setup and configuration

The mcp-ecommerce-platform-profiler MCP server requires Node.js 18 or newer, an Apify account, and an Apify API token. Install it for a stdio MCP client with npx and provide the token as APIFY_TOKEN:

{
  "mcpServers": {
    "mamba-ecommerce-platform-profiler": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-ecommerce-platform-profiler"],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

The main tool is profile_ecommerce_platform. Its company_domain input identifies the storefront. company_name is optional but recommended because it is checked against a discovered record. Additional options control product counts, payment-provider checks, cart-page reads, blocking behavior, and cache use.

Tools and capabilities

• Identify the detected ecommerce platform and alternate platform signals.
• Record confidence and the evidence supporting platform detection.
• Find payment-provider scripts visible on the storefront or public cart page.
• Indicate possible subscriptions and marketplace applications.
• Estimate catalog size and identify the estimate source.
• Return observed currencies, shipping destinations, coverage, and fetch status.

Limitations and notes

The mcp-ecommerce-platform-profiler MCP server only sees information exposed through its static reads. If a storefront reveals its platform only after JavaScript runs, the result is reported as not_extractable rather than inferred from a similar platform. Providers loaded only during a complete checkout may not be visible, although reading the public cart page can expose some of them.

The cart check is a read of a public URL: it does not add items, start checkout, or submit forms. Product counts are approximate, and currencies or shipping destinations may be absent. A blocked site may be retried when escalation is enabled, but the returned row can still have reduced coverage or a non-OK fetch status. Consult the Apify actor documentation for the complete input and output schema, pricing, and run history.