Shopify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASDATA_API_KEY | Yes | Your HasData API key from the dashboard, used for authentication. |
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": false
} |
| completions | {} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hasdata_shopify_collections_getCollectionsA | Get Shopify Store Collections Lists collections from any public Shopify storefront URL with limit (up to 250) and page pagination. Returns each collection's id, title, handle, body_html description, image, and timestamps. Use the returned handles as input to the Shopify Products endpoint to enumerate category-specific catalogs, or to map a competitor's merchandising taxonomy and track collection changes over time. |
| hasdata_shopify_products_getProductsA | Get Shopify Store Products Pulls products from any public Shopify storefront URL, optionally filtered by a collection handle, with limit (up to 250) and page pagination. Returns product id, title, handle, vendor, product_type, tags, body_html, images, variants with prices/SKUs/inventory status, and timestamps. Use for competitive price monitoring, catalog mirroring, availability tracking, building product datasets for comparison shopping, or feeding structured SKU data into downstream analytics and dropshipping pipelines. |
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 2 tools
The two tools target clearly distinct resources: collections and products. There is no functional overlap or ambiguity about which tool to use.
Both tool names follow the same pattern: hasdata_shopify_<resource>_get<Resource>s. The structure is consistent and predictable across the small toolset.
Two tools is thin for a general-purpose server, but the scope is clearly limited to read-only public Shopify storefront data. The count is borderline and could benefit from additional endpoints, but it is not unreasonable for this narrow purpose.
The pair covers core storefront exploration: listing collections and listing products within a collection or across the store. Minor gaps exist, such as no direct single-product lookup or search, but the main catalog enumeration workflow is complete.