What Is the Shopify MCP Connector?The Shopify MCP Connector gives AI assistants controlled access to Shopify Admin data and operations across multiple connected stores.Instead of creating and managing a separate custom app, client ID, and secret for every merchant, stores can be connected through Satva’s Shopify Partner app and accessed through one controlled MCP environment.Teams can ask questions about products, orders, customers, inventory, fulfillments, refunds, and other Shopify Admin data in natural language. Where write access is enabled, the connector can also perform approved actions.For businesses that need broader Shopify connectivity beyond MCP-based access, Satva also builds custom integrations connecting Shopify with ERP, CRM, accounting, warehouse, payment, and other business systems.The flow is straightforward: Shopify Stores → Satva Partner App → MCP Connector → AI Assistant → Data or Approved ActionSign in, connect the handle, ask one key covering every Ready store
Step 1Connect Shopify to MCP Without Creating a Custom AppThe setup is a store handle and a Google sign-in. That is the whole of it. You type the handle, not a client ID. The .myshopify.com is already printed next to the field. Nothing is copied out of your Shopify admin, and nothing is pasted into ours. One Partner app covers every store. Satva’s shared Shopify app handles OAuth, so no custom app sits in your admin and no secret ages quietly in a password manager. There is nothing to install. The connector is reachable through Obot and nowhere else. Point Cursor, Claude Desktop, or VS Code straight at the server and the answer is 403. Approve once, and the store reads Ready. Ready is the only state that matters. The list tells you which stores are Ready and which need reconnecting before you ask them anything. Removing a store unlinks that one and leaves every other store working. A store handle and a Google sign-in. No custom app to create.
Step 2Manage Multiple Shopify Stores Through One MCP ConnectionConnect as many stores as you run. The same key and the same chat reach all of them. One key covers every Ready store in the same chat. Name the store in the question. Or leave it out, and the one you set as default answers. Similar names are not a guessing game. Ask for the list of connected stores and pass the exact .myshopify.com domain instead of the name. For teams operating several commerce systems or client storefronts, a broader multi-platform architecture can also connect Shopify with other ecommerce channels and back-office applications. Token health is a question you can ask. A store summary checks every connection, so run it before a reporting run, not during one. A dead token is one store’s problem. Reconnect that store; every other Ready store keeps answering while you do. Regenerating your key invalidates the old one. Paste the new key into Obot and every store comes back with it.
Step 3Shopify Admin Actions With Controlled Write Access and Audit Logs82 tools across the Shopify Admin GraphQL API. Most of them read. The ones that write do real things to a real shop, and that is better said here than in a post-mortem. Products, orders, customers, inventory, fulfillments, and refunds. Plus collections, draft orders, discounts, pages, B2B companies, webhooks, and returns. Draft orders for phone and wholesale sales. Build the order, add the line items, and complete it when the customer pays. Fulfill an order with a tracking number and notify the customer in the same conversation where you asked which orders were still unfulfilled. The destructive tools are genuinely destructive. Deleting a product, canceling an order, issuing a refund, and merging customers all reach live commerce. Demos run on a development store, and we scope write access when we deploy. Every call is written to the tenant activity feed. That is the difference between an assistant you can hand to an operations team and one you cannot. Products, orders, fulfillments, and refunds. Every call is written to the activity feed.
Ten things to type on day oneThese are the prompts we use in the demo. Nothing is rephrased for the website.Once your stores are connected, the Shopify MCP Connector can answer questions and perform approved actions like these in plain English. “Which stores are connected?”: every store on the key, and which one is the default “Shop snapshot”: name, plan, and currency for that store “List products”: the first page of products with prices “List open orders”: unfulfilled or unpaid “Create a product”: a demo product, saved as a draft. “Look up a customer”: found by email, with their orders. “Create a draft order”: a phone-sale draft for one SKU “Fulfill an order”: a test order marked shipped, with tracking. “Inventory by location”: stock for one product at each location “Abandoned checkouts”: the recovery list
Under the hood82 tools across the Shopify Admin GraphQL API. Products, orders, customers, inventory, fulfillments, refunds, collections, draft orders, discounts, pages, B2B companies, webhooks, and returns, multi-store on one SatvaUserKey, targeted with store=. One shared Partner app, so no custom app, client ID, ID, or secret. Every call is written to the tenant activity feed. Obot-only, with direct callers refused.Type the store handle. That is the whole setup.