Shopify App Store Chrome Web Store Listings MCP Server

Shopify App Store and Chrome Web Store Listings MCP Server

An MCP server for the Mamba Labs Shopify App Store and Chrome Web Store Listings actor on Apify. Give it categories, keywords, or listing URLs. It returns one row per app with the app's numbers and its developer's own website and domain.

What's Inside

• What it does
• Quick start
• Prerequisites
• Example prompts
• Tool
• Inputs
• Pricing
• Your keys
• Full actor documentation
• License

What it does

• Shopify App Store: apps per category (24 per page, paged), or by keyword matched against every app name in the store's app list. Rating, reviews, pricing line, Built for Shopify flag, launch date, developer page, website, address.
• Chrome Web Store: extensions per category (about 32 per category page), or by keyword across the categories. Rating, exact rating count, users, version, last update, developer website, address, email, and phone.
• Developer domain: the registrable domain of the developer website on every row, ready to join to a company list.

Apps below your rating or review filter are skipped and never billed. Input with nothing to run comes back as one free row whose error_reason starts with input_invalid:.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-shopify-app-store-chrome-web-store-listings": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-shopify-app-store-chrome-web-store-listings"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The list_store_apps tool appears.

Prerequisites

• Node.js 18 or newer.
• An Apify API token from console.apify.com/account/integrations, set as APIFY_TOKEN. The server lists its tool without a token; a call needs one.

Example prompts

• "List the top 20 email marketing apps in the Shopify App Store with their developer websites."
• "Which productivity extensions in the Chrome Web Store have over 100,000 users, and how do I contact their developers?"
• "Find Shopify apps with 'reviews' in the name rated 4.5 or higher."

Tool

list_store_apps. One tool. Example arguments:

{
  "categories": [
    "marketing-and-conversion-marketing-email-marketing",
    "productivity/workflow"
  ],
  "max_apps": "10"
}

Inputs

Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults. Numbers and booleans are sent as strings.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

Rows for a category, sitemap, or listing that could not be read are free, and so is the no_results row.

Your keys

The actor needs no key. It reads the public category and listing pages of both stores and holds no key of any kind. Proxy traffic adds nothing to your price: Mamba Labs pays the platform costs of the run. proxy_mode is a reliability setting.

Full actor documentation

apify.com/mambalabs/shopify-app-store-chrome-web-store-listings

License

MIT. See LICENSE.