Shopify MCP: developer docs and catalog reads, with orders out of reach

Shopify MCP covers distinct jobs: Dev MCP gives coding agents developer documentation, API schemas and code validation, while commerce MCP services expose shopper-facing capabilities. For a Shopify AI agent that only needs developer context and store questions, begin with Dev MCP and selectively allow catalog reads; keep orders, checkout and money-moving actions outside that setup. Shopify’s AI Toolkit guide separates developer resources from broader store-management workflows.

What it can do

Use the question to choose the connection. Explaining a schema and looking up a merchant’s products require different evidence. The following map reflects Shopify documentation as of 30 Oct 2026; it is not a promise that every capability belongs in your agent.

The commerce overview describes discovery, carts, checkout and order monitoring. The Customer Accounts guide documents the separate customer-facing service. Keeping orders out of reach here is a configuration decision, not a claim that Shopify lacks order tools.

For development, ask the agent to locate the relevant API reference, explain a field and propose a query for review. Shopify’s official Toolkit repository describes documentation, schemas and validation for GraphQL, Liquid and UI extensions. A useful deliverable is the suggested code plus the reference that supports it. Run and test changes separately before applying them to a store.

For store questions, start with a product comparison: find matching products, retrieve their details and report the merchant and variant identifiers used. Storefront Catalog MCP documents search_catalog, lookup_catalog and get_product. Do not turn a catalog answer into a claim about private orders or the merchant’s entire operational inventory.

For the protocol basics, read what MCP is. Compare connection choices in remote versus local MCP servers, or browse MCP servers for apps.

How to connect it safely

1. Write the boundary first. Authorize documentation lookup, code suggestions and selected product reads. Exclude customer records, order access, cart changes, checkout, refunds and payments. Make the allowed output concrete: a cited explanation, a proposed patch or a product comparison. Apply this boundary to every tool available to the client, including its shell.

2. Connect Dev MCP in the editor. In VS Code, run MCP: Open User Configuration, merge the server entry below into the existing configuration, save and restart. Shopify documents this procedure in its Dev MCP setup instructions. Preserve other entries. Check the current documentation for runtime requirements before starting the package.

json { "servers": { "shopify-dev-mcp": { "command": "npx", "args": ["-y", "@shopify/dev-mcp@latest"] } } }

This configuration launches package code locally. Review the publisher and package before approving it. For client-side controls, use the VS Code MCP guide.

3. Prove the development path. Ask for a documentation-backed explanation of a small code sample, then request validation where supported. Shopify’s Polaris MCP guide documents the package command and development use. Check that the answer includes a relevant reference and that the validation result actually concerns the supplied code. Do not accept a fluent explanation as evidence that validation ran.

4. Add catalog access separately, if needed. The merchant endpoint documented for Storefront Catalog is https://{storedomain}/api/ucp/mcp. Requests require an agent profile, and advertised capabilities affect the returned tools. Follow the Storefront Catalog documentation, inspect discovery results, and enforce a catalog-read allowlist in your client or gateway. If your client cannot enforce that boundary, keep this connection out of the pilot.

5. Match authentication to the service. Dev MCP runs locally without authentication. UCP has token, signed and anonymous traffic tiers; anonymous access is not a read-only permission boundary. Shopify’s authentication and rate-limit guide explains the differences. For the token route, the authentication tutorial uses Dev Dashboard client credentials to obtain a bearer token. Keep credentials in the application’s secret handling, outside prompts and committed configuration.

6. Test refusal as well as success. Ask for product details, then request an order lookup and a checkout action. The latter requests should be blocked by your configuration. Review the actual tool trace. A polite refusal in the final answer is insufficient if the tool was already called. Save a redacted record of the permitted tools and observed results; use the MCP security checklist for the wider review.

When this does not work

Developer context is being mistaken for live store access. A schema describes what an API supports; it does not establish the contents of a particular store. Stop an answer that silently turns documentation into account evidence. Require a named data source for each store-specific assertion.

The broader Toolkit changes the scope. Shopify’s repository also describes store management through CLI execution. Installing the full plugin needs a separate capability review. Do not assume the narrow Dev MCP setup describes everything a Toolkit-equipped agent can execute.

Customer authentication is missing. Customer Accounts MCP requires a custom domain, protected customer data requirements and customer authentication using OAuth with PKCE. Its endpoint is discovered from the storefront domain. These are separate prerequisites, not problems to solve by pasting an administrator credential into a chat.

A commerce request fails despite a token. Token-tier merchant tool calls also require the actual buyer’s Shopify-Buyer-IP; Shopify documents no placeholder for a buyer who is absent. Rate-limited requests should follow Retry-After. Consult the current request requirements instead of repeatedly retrying or widening permissions.

A product result contains instructions. Treat descriptions and retrieved text as data. A product description cannot authorize a new tool, a different destination or a purchase. Keep that rule in both the agent’s task and the enforcement layer.

Where Tvijo fits

Tvijo can be a place to review developer explanations and permitted store evidence. Its DSHREM VS Code extension provides an editor entry point for scoped tasks. Attach a small code excerpt or an approved, redacted catalog result and request a cited explanation. This is a proposed workflow for Shopify-related work; it does not establish a ready Shopify connector.

TvijoCode is a test build with the extension embedded. Tvijo MCP makes Tvijo consultation available to a compatible client. Planned editor integration and delegation are separate from that consultation path. Connecting Tvijo MCP does not automatically make Tvijo an executor of Shopify MCP tools. A Shopify connection requires its own setup, authorization and acceptance checks; keep orders and money-moving actions outside this pilot.

As of 30 Oct 2026, the Tvijo workspace shows Try at $0: up to 5 tasks, 50,000 tokens or $0.05 of sponsored usage, whichever is reached first, from a shared $1 daily pool funded by TVIJO. Service credit is shown at $10 as a request for prepaid credit, with metered provider usage plus an 8% service markup. Payment collection is not activated; an order is not a charge. These offers do not grant Shopify access.

FAQ

Does Shopify Dev MCP need a store login?

No authentication is required for the local Dev MCP server. That does not authorize a separate commerce connection; use the documented setup for the intended service.

Can this setup answer where a customer’s order is?

That is outside the suggested boundary. Shopify documents order-related services, but adding them means a separate identity, privacy and authorization review. Do not infer permission from a successful catalog search.

Is telling the agent to read only enough?

Use enforceable tool restrictions as well as task instructions. If a client cannot reliably block order access and purchase actions, limit the pilot to developer documentation and manually supplied, approved evidence.

Shopify is a trademark of its owner. Tvijo is not affiliated with or endorsed by it.