Shopify's official Claude connector or a read-only relay: which one, for what

Claude's connector directory (claude.com/connectors/shopify, read on September 13, 2026) lists a Shopify connector marked "Made by Shopify" and added in April 2026.

Its tool list reads the store (products, orders, customers, inventory, collections, analytics) and writes to the admin: create-product, update-product, set-inventory, create-discount, create-collection, upload-image, bulk-update-product-status, and graphql_mutation.

If you want to create a product, adjust stock or launch a discount from a conversation, that is the tool you want. Shopify builds it, for Shopify.

BoostEcom's Shopify MCP, a read-only relay, deliberately does less:

• one endpoint per store, https://boostecom.app/api/mcp/v1/<STORE_ID>;
• read-only: every mutation, and any GraphQL document the relay cannot classify, is refused before it reaches Shopify, and each attempt is journaled;
• tools gated by scope, registered only when they clear the consented scope and the store's Shopify scopes, so a refused tool never shows up in the client's list. The tools and scopes reference lists every one;
• four documented clients, Claude, ChatGPT, Claude Code and Cursor, all signing in over OAuth; a static key covers CI and headless runs.

| | Shopify's official connector | BoostEcom relay | |---|---|---| | Built by | Shopify | BoostEcom | | Writes to the admin | yes | no, refused before Shopify | | Clients | Claude's directory | Claude, ChatGPT, Claude Code, Cursor | | Reach | per its own authorization screen | one endpoint per store, tools filtered by scope |

This is not about quality. It is about the pen: one hands it to your assistant, the other doesn't have one.

Worth saying out loud, because it would be easy to assume otherwise: the relay does not read the market.

BoostEcom does run an intelligence graph, where twenty-plus probes turn any public storefront into a record (stack, ads, traffic, reviews, emails). On the relay, one scope reads the record BoostEcom holds on your own store's domain, over OAuth only. Other stores, rankings and the rest of the market are not on the relay: Intelligence has its own read-only API, with a separate bei_ key. Connecting your assistant to the relay connects it to your store, not to the market.

And the relay will not write in place of the official connector. BoostEcom's writes go through the dashboard chat, behind human approval.

• You want the assistant to change the store: the official connector.
• You want an assistant that reads and cannot break anything: for a freelancer you are letting into the store, a code editor, a CI job, or just asking questions with no risk attached: the relay.
• Both: they are two separate connectors and they do not exclude each other. The pen on one side, risk-free reading on the other.

To connect the relay, each client has one guide, and only one: Claude, ChatGPT, Claude Code and Cursor. The broader question of which assistant to pick, and what each path costs you, is in Connect Shopify to Claude or ChatGPT.

• Sources: the Shopify connector's page in Claude's directory, read on September 13, 2026 (an external source that can change after that date); for our relay, the code and the public MCP server, tools and scopes and Intelligence API pages.
• Automation: an AI assistant drafted the first pass and pulled the tool list from the official page.
• Not verified: I have not tested the official connector. I do not describe its permission model in detail, its rate limits, or its availability in ChatGPT: I found no official source I could cite.
• A correction along the way: our internal notes dated this connector to May 2026. The official page says April 2026.
• What I added: the review and the call to publish.

Verified on September 13, 2026.