Ecommerce Store Discovery MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | An Apify API token from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_ecommerce_storesA | Find online stores that sell a product on a given platform (shopify, woocommerce, bigcommerce, or any), with each store confirmed on its own homepage. Give keywords and a platform. One row per store: domain, store_name, platform with platform_confidence and platform_evidence, myshopify_domain, payment_methods, subscription_apps, currencies, product_count (Shopify products feed), Tranco rank band and trend (a rank, not traffic), contact_emails, phone, and Instagram, Facebook, and TikTok links from the homepage, plus the search that found it. Sites that do not show the platform are skipped and not charged. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per confirmed store and per Google result page read. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong tool or confusing overlapping purposes. Its purpose is clearly stated as ecommerce store discovery.
The single tool name follows a clear snake_case verb_noun pattern: discover_ecommerce_stores. Although there is only one name, it is descriptive and internally consistent.
A single tool is thin for an MCP server, even one narrowly focused on store discovery. The tool itself is broad and complex, but the surface offers no separate lookup, filtering, or result-management operations.
The discovery operation returns rich store-level details, platform evidence, contact data, social links, ranking context, and error run IDs. Minor gaps remain, such as no follow-up lookup by domain or pagination/result-management tools, but the core discovery workflow is covered.