Shopify MCP
PYPI · SCALABLY-SHOPIFY-MCP · 2 COMPONENTS · SCANNED SEP 20
Read-only Shopify Admin GraphQL MCP: query, introspect, bulk export, ShopifyQL. 6 tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 33 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1476 tokens (~246/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "shopify_graphql_query" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Shopify MCP server?
Shopify MCP runs locally as a PyPI package, launched with uvx scalably-shopify-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · scalably-shopify-mcp
claude mcp add io-scalably-shopify-mcp -- uvx scalably-shopify-mcp
{
"mcpServers": {
"io-scalably-shopify-mcp": {
"command": "uvx",
"args": [
"scalably-shopify-mcp"
]
}
}
} {
"servers": {
"io-scalably-shopify-mcp": {
"command": "uvx",
"args": [
"scalably-shopify-mcp"
]
}
}
} codex mcp add io-scalably-shopify-mcp -- uvx scalably-shopify-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-scalably-shopify-mcp": {
"type": "local",
"command": [
"uvx",
"scalably-shopify-mcp"
],
"enabled": true
}
}
} openclaw mcp add io-scalably-shopify-mcp --command uvx --arg scalably-shopify-mcp
mcp_servers:
io-scalably-shopify-mcp:
command: "uvx"
args: ["scalably-shopify-mcp"] {
"McpServers": {
"io-scalably-shopify-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"scalably-shopify-mcp"
]
}
}
} assistant mcp add io-scalably-shopify-mcp -t stdio -c uvx -a scalably-shopify-mcp
{
"mcpServers": {
"io-scalably-shopify-mcp": {
"command": "uvx",
"args": [
"scalably-shopify-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +3
- Stability: unverified → 0.23 ▲ functional
- 9 Sept 26 50
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/scalably-shopify-mcp@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 33 packages
| Packages resolved | 33 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
shopify_bulk_poll ~168
Poll a bulk operation's status by ID. Statuses: CREATED, RUNNING, COMPLETED, CANCELED, EXPIRED, FAILED. On COMPLETED, the `url` field is a pre-signed JSONL download (valid 7 days). On FAILED, `partialDataUrl` may hold partial results; `errorCode` explains why. Args: operation_id: Global ID of the bulk operation (format: `gid://shopify/BulkOperation/<numeric-id>`). shop: Store alias or domain the bulk op was launched on. Required when multiple stores are configured. api_version: Override API version (default "2026-04").
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | – | – | – |
| operation_id | string | yes | – |
| shop | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
shopify_bulk_query ~220
Launch an async bulk export of a read-only GraphQL query. Use for exporting datasets too large for paginated queries (>10k records, or anything you'd otherwise paginate hundreds of times). Shopify runs the query in the background and produces a JSONL file with all results. Restrictions (enforced by Shopify): - Exactly one top-level connection per query. - Max 5 total connections, max depth 2. - Every nested connection node must select `id` without an alias. - API ≤ 2025-10: one bulk op at a time per shop. API ≥ 2026-01: up to 5. Returns the BulkOperation ID - poll with `shopify_bulk_poll`. Args: query: Read-only GraphQL document with a single root connection. shop: Store alias or domain. Required when multiple stores are configured. api_version: Override API version (default "2026-04").
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | – | – | – |
| query | string | yes | – |
| shop | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
shopify_graphql_introspect ~171
Introspect a Shopify store's Admin GraphQL schema. Pass `type_name` to fetch a single type's fields (cheap, ~50 cost points). Omit it for the full schema type catalog (expensive, ~800 cost points - use sparingly). Args: type_name: GraphQL type name (e.g. "Order", "Product", "Customer"). Must match `[A-Za-z_][A-Za-z0-9_]*`. Omit for full schema. shop: Store alias or domain (see `shopify_list_stores`). Required when multiple stores are configured. api_version: Override API version (default "2026-04").
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | – | – | – |
| shop | – | – | – |
| type_name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
shopify_graphql_query ~371
Execute a read-only GraphQL query against a Shopify store's Admin API. Universal entry point for reading any data the token's scopes permit: products, variants, orders, customers, inventory, fulfillments, discounts, locations, markets, metafields, metaobjects, segments, shop settings, etc. Full GraphQL reference: https://shopify.dev/docs/api/admin-graphql Write mutations are rejected by design. The query string is parsed and validated as read-only before transmission. Idiomatic patterns: - Pagination: `first: <=250`, `after: <cursor>`, read `pageInfo { hasNextPage endCursor }`. - Search: pass a Shopify search string to the `query:` arg on connections, e.g. `orders(first: 100, query: "created_at:>=2026-04-01 financial_status:paid")`. - Money: `totalPriceSet { shopMoney { amount currencyCode } }`. - For datasets >10k records, use `shopify_bulk_query` instead. Args: query: GraphQL document. Must be a `query` or a `fragment`. Subscription and mutation operations are rejected - with one narrow exception, `bulkOperationCancel`. For bulk exports, use `shopify_bulk_query`. variables: Optional variables dict passed as GraphQL `variables`. shop: Store alias (from `shopify_list_stores`) or domain. Required when multiple stores are configured; optional (auto-selected) when there's only one store. api_version: Override API version (default "2026-04"). Format "YYYY-MM".
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | – | – | – |
| query | string | yes | – |
| shop | – | – | – |
| variables | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
shopify_list_stores ~158
List all Shopify stores configured for this agent. Returns a JSON array of `{alias, domain, name, currency, auth_mode}`. The `name` field is the merchant's own shop name from Shopify (fetched once per process, cached). Use this list to match user intent - e.g., a user saying "check the outlet" maps to the store whose `name` or `domain` contains "outlet". If only one store is configured, `shop` can be omitted on tool calls. Args: refresh: If True, bypass the shop-name cache and re-fetch from Shopify. Use after a merchant renames a shop in the Shopify admin.
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
shopify_shopifyql ~388
Run a ShopifyQL analytics query against a Shopify store. ShopifyQL is Shopify's SQL-like reporting language. Requires `read_reports` scope. Consumes the same cost bucket as GraphQL. Syntax: FROM <dataset> SHOW <metric>[, <metric>...] [BY <dimension>] [GROUP BY <dim>] [WHERE <filter>] [SINCE -Nd UNTIL today] [ORDER BY <col> [ASC|DESC]] [LIMIT N] Datasets: sales, orders, products, customers, inventory, sessions. Time tokens: -Nd / -Nw / -Nm / -Nq / -Ny, or named (today, yesterday, this_week, last_week, this_month, last_month, last_year). Examples: - `FROM sales SHOW total_sales GROUP BY day SINCE -7d UNTIL today ORDER BY day ASC` - `FROM sales SHOW total_sales BY product_title ORDER BY total_sales DESC LIMIT 10 SINCE -30d` - `FROM sales SHOW returning_customer_rate GROUP BY month SINCE -6m` - `FROM sales SHOW net_sales SINCE -1q UNTIL today` - `FROM sessions SHOW sessions, conversion_rate GROUP BY referrer_source SINCE -14d` Returns `tableData.columns`, `tableData.rows`, and `parseErrors`. When parsing fails, `tableData` is `null` and `parseErrors` contains a list of human-readable error strings (e.g. "Column 'total_sale' not found"). Args: query: ShopifyQL query string. shop: Store alias or domain. Required when multiple stores are configured. api_version: Override API version (default "2026-04").
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | – | – | – |
| query | string | yes | – |
| shop | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Shopify MCP server?
Shopify MCP is listed in the public MCP registry as io.scalably/shopify-mcp. Read-only Shopify Admin GraphQL MCP: query, introspect, bulk export, ShopifyQL. 6 tools. This page covers its PyPI package (scalably-shopify-mcp).
Is the Shopify MCP server safe to use?
Shopify MCP scores 55 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Shopify MCP server expose?
Shopify MCP exposes 6 tools: shopify_list_stores, shopify_graphql_query, shopify_graphql_introspect, shopify_bulk_query, shopify_bulk_poll, shopify_shopifyql. Their descriptions and schemas cost roughly 1,476 tokens of context every time the server is loaded.
Is the Shopify MCP server still maintained?
Shopify MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Shopify MCP server under?
Shopify MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.