Skip to main content
Glama
Sign In
Shopify App Store and Chrome Web Store Listings MCP Server

Shopify App Store and Chrome Web Store Listings MCP Server

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Shopify App Store and Chrome Web Store Listings MCP Server

Glama score MCP Registry npm version npm downloads license mcpservers.org

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

Related MCP server: partnerlens-mcp

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

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.

Input

Type

Description

categories

array

One per line. Shopify App Store: a category URL or slug from apps.shopify.com/categories, for example marketing-and-conversion-marketing-email-marketing. Chrome Web Store: a category URL or one of productivity/communication, productivity/developer, productivity/education, productivity/tools, productivity/workflow, lifestyle/art, lifestyle/entertainment, lifestyle/fun, lifestyle/games, lifestyle/household, lifestyle/news, lifestyle/shopping, lifestyle/social, lifestyle/travel, lifestyle/well_being, make_chrome_yours/accessibility, make_chrome_yours/functionality, make_chrome_yours/privacy

keywords

array

Optional. Shopify: matched against every app name in the Shopify App Store app list. Chrome: matched against the name and summary of the extensions on the categories you gave, or on all 18 categories when you gave none. Every word of the keyword must match

app_urls

array

Optional. apps.shopify.com or chromewebstore.google.com listing URLs to read directly. Always read, outside the max apps cap

stores

array

Which stores a keyword is searched in: shopify_app_store, chrome_web_store, or both. Default both. Categories and listing URLs name their own store

max_apps

string

Most apps per category and per keyword. Default 50, up to 500. A Chrome category page lists about 32 extensions

include_details

string

Default true. Keyword and URL rows always read the listing page

min_rating

string

Optional. Skip apps rated below this, for example 4

min_reviews

string

Optional. Skip apps with fewer reviews or ratings than this

max_charge_usd

string

Optional. The run stops before it would charge more than this

proxy_mode

string

A reliability choice. Default auto

Pricing

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

Event

Free plan

Bronze

Silver

Gold

app-listing, one Shopify app or Chrome extension returned, with its listing page read unless include_details is false

$0.005

$0.00475

$0.0045

$0.00425

apify-actor-start, per run start

$0.0006313

$0.0006313

$0.0006313

$0.0006313

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.

Available Tools

1 tool
list_store_appsList Shopify apps and Chrome extensions with their developersA
Read-only

List Shopify App Store apps and Chrome Web Store extensions by category, keyword, or listing URL. Give Shopify category slugs or URLs (marketing-and-conversion-marketing-email-marketing), Chrome categories (productivity/workflow), keywords, or apps.shopify.com and chromewebstore.google.com listing URLs. Each app is one row: name, rating, review count, Shopify pricing line and Built for Shopify flag, or Chrome users and version, plus the developer name, website, registrable domain, address, country, and on Chrome the published email and phone. Apps below min_rating or min_reviews are skipped and not billed. Input with nothing to run comes back as one free row with error_reason input_invalid. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per app row.

NameRequiredDescriptionDefault
storesNoWhich stores a keyword is searched in: shopify_app_store, chrome_web_store, or both. Default both. Categories and listing URLs name their own store
app_urlsNoOptional. apps.shopify.com or chromewebstore.google.com listing URLs to read directly. Always read, outside the max apps cap
keywordsNoOptional. Shopify: matched against every app name in the Shopify App Store app list. Chrome: matched against the name and summary of the extensions on the categories you gave, or on all 18 categories when you gave none. Every word of the keyword must match
max_appsNoMost apps per category and per keyword. Default 50, up to 500. A Chrome category page lists about 32 extensions
categoriesNoOne per line. Shopify App Store: a category URL or slug from apps.shopify.com/categories, for example marketing-and-conversion-marketing-email-marketing. Chrome Web Store: a category URL or one of productivity/communication, productivity/developer, productivity/education, productivity/tools, productivity/workflow, lifestyle/art, lifestyle/entertainment, lifestyle/fun, lifestyle/games, lifestyle/household, lifestyle/news, lifestyle/shopping, lifestyle/social, lifestyle/travel, lifestyle/well_being, make_chrome_yours/accessibility, make_chrome_yours/functionality, make_chrome_yours/privacy
min_ratingNoOptional. Skip apps rated below this, for example 4
proxy_modeNoA reliability choice. Default auto
min_reviewsNoOptional. Skip apps with fewer reviews or ratings than this
max_charge_usdNoOptional. The run stops before it would charge more than this
include_detailsNoDefault true. Keyword and URL rows always read the listing page

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well past the annotations: declares per-row Apify billing, that filtered apps are not billed, that empty input yields a single free row with error_reason input_invalid, that failed runs return an error carrying the run ID, and that an APIFY_TOKEN is required. That is exactly the cost/failure information an agent must know before invoking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then input formats, then row shape, then billing and error behavior — a sensible order with no filler. The row-field sentence is dense and parenthetical-heavy, but every clause carries information an agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description steps up by enumerating the returned fields (name, rating, reviews, pricing, Built for Shopify flag, users/version, developer name, domain, address, country, contact info). Combined with the cost and error semantics, a 10-parameter tool is fully described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3; the description still adds real semantics by tying min_rating/min_reviews to billing exclusion and by showing valid Shopify slug and Chrome category shapes in prose. It does not cover max_apps, proxy_mode, or max_charge_usd, so it is an enhancement rather than full compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and two named resources (Shopify App Store apps, Chrome Web Store extensions) plus the three selection modes (category, keyword, listing URL). The title and first sentence together leave no ambiguity about what the tool returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the accepted input styles with concrete examples for each store, and notes that categories and URLs self-select their store while `stores` only applies to keywords. It stops short of explicit when-not guidance, but with no sibling tools there is little to route against.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedlist_store_apps
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool there is no possibility of misselection between competing tools. The single tool's purpose (list Shopify/Chrome store apps by category, keyword, or URL) is unambiguous and self-contained.

Naming Consistency5/5

The lone name `list_store_apps` follows a clean verb_noun snake_case pattern. No competing conventions exist to create inconsistency.

Tool Count2/5

A single tool is too thin for a server covering two distinct stores and multiple query modes (category, keyword, listing URL). All functionality is collapsed into one parameter-heavy call, which makes it hard for an agent to discover intent-specific operations.

Completeness3/5

Listing is well covered (both stores, category/keyword/URL inputs, rich per-row fields), but there is no detail-lookup, category enumeration, or pagination/continuation operation. Agents wanting a single app's full record or a list of valid categories have no dedicated path.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Store Scraper MCP

    MiguelAlvRed
    A
    license
    C
    quality
    D
    maintenance
    Enables querying and retrieving data from App Store and Google Play Store, including app details, reviews, ratings, rankings, permissions, and search capabilities across both iOS and Android platforms.
    20
    MIT
  • com.storeinspect/mcp

    com.storeinspect/mcpofficial

    StoreInspect
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI clients to search Shopify stores and contacts by market, traffic, revenue, apps, pixels, themes, ads, or contact availability, enrich known domains, preview matching contacts, and reveal selected contact details after approval via OAuth.
    MIT

  • Integration and Marketplace

    mambalabsdev
    A
    license
    A
    quality
    B
    maintenance
    Given a company domain or name, it checks ten app marketplaces — HubSpot, Salesforce AppExchange, Slack, Zapier, Shopify, Atlassian, Chrome Web Store, Microsoft, Google Workspace, and WordPress — to report where the company is listed, with each listing's URL, installs, rating, review count, and match confidence. Useful for competitive research and partner-ecosystem audits across many domains in a single run.
    1
    68 npm
    MIT