Shopify MCP vs. Steward: which one fits a team running a store?
Shopify Dev MCP, Storefront MCP, community admin servers or Steward? What each is for, and why store teams need shared access and approvals.
There is more than one “Shopify MCP”
If you search for “Shopify MCP”, you will find several very different things under the same name. At the time of writing, these are the main ones:
- Shopify Dev MCP: an official server for developers. It gives coding assistants such as Claude Code or Cursor access to Shopify’s documentation and API schemas. It is for building apps and themes, not for managing your store’s data.
- Storefront, Customer Account and Checkout MCP: official servers for shopping agents that serve your customers. They help an AI sell your products, not help your team run the business.
- Community admin MCP servers: open-source or hosted servers that connect an AI app to your store’s Admin API with your credentials.
- Shopify’s own apps for Claude and ChatGPT: official connectors that let a merchant manage a store from a personal chat. We compare them in separate articles on Claude and ChatGPT.
If your goal is “my team should be able to ask questions about our store and prepare changes safely”, the relevant comparison is between community admin MCP servers, the official chat apps and Steward.
What a community admin MCP server does
A community Shopify MCP server typically runs on your computer or a hosting service. You give it a store address and Admin API credentials, then connect it to your AI app. The AI receives tools such as “get orders”, “update product” or “delete product”.
That is powerful, and it is also where the questions start:
- Changes are live immediately. If the AI misunderstands “update all summer products”, the update is already in your store.
- The credentials belong to the setup, not to people. Everyone using the configuration has the same rights.
- There is no team view. What one person asked and changed is stored in their own chat app.
- You maintain it. API versions, scopes and errors are your responsibility.
What a store team actually needs
A store with more than one person has roles. A marketing manager edits product content. A customer-service agent looks up orders. The owner approves discounts and refunds. An agency may need limited access for a project.
For AI to be helpful and safe in that setting, you need:
- One connection with per-person rights, rather than one shared key.
- A review step before anything changes, with mandatory review for sensitive actions.
- A shared history of questions, proposals and decisions.
- Honest limits when data is incomplete, such as Shopify’s default order history window.
How Steward handles Shopify
Your app, your scopes
Steward connects through a Shopify app your organization owns. You choose its scopes in the Shopify Dev Dashboard, and Steward detects the granted access automatically. With Client ID and secret, Steward renews short-lived access tokens itself and never displays your credentials again.
Two locks on every request
Project roles. Viewers follow results, Contributors use configured connections and prepare changes, and Managers approve. Invited project members need no separate connection grant.
Some actions always need a human
Refunds, payment capture, order cancellation, fulfillment actions, publishing, deletion and customer notifications always require approval in Steward, even in Automatic mode. Credential administration, app billing, code injection and arbitrary webhooks are blocked entirely.
Bulk work with a full review
Updating 5,000 products is a different risk from updating five. Steward’s bulk work validates every row before anything starts. It lets the approver download the complete input, not just a preview, and reports the result for every chunk.
Honest data limits
Shopify normally provides only the last 60 days of orders unless your app has read_all_orders. Steward tells you when a result is limited, so a “year-over-year” report is not quietly based on two months.
Shopify MCP options and Steward side by side
| Shopify Dev MCP | Community admin MCP | Steward | |
|---|---|---|---|
| Made for | Developers building apps | One person managing a store | Teams running a store |
| Reads store data | Not its purpose | Yes | Yes |
| Changes store data | No | Yes, usually immediately | Yes, as reviewed proposals by default |
| Per-person rights | — | No, shared credentials | Project roles: Viewer, Contributor, Manager |
| Always-review actions | — | Not typical | Refunds, cancellations, publishing, deletion and more |
| Bulk changes | — | Varies | Fully reviewable bulk proposals |
| Shared history | — | No | Project conversations with approvals |
What your team can ask
Which products sold fewer than five units in the last 30 days but have more than 100 in stock?
Show this week’s orders that are paid but not yet fulfilled, oldest first.
Draft a 15 % discount for the “Winter” collection, valid from Friday to Sunday, and show it to me before creating it.
Prepare SEO titles and meta descriptions for all products in “New arrivals” that are missing them.
Which one should you choose?
- Building a Shopify app or theme? Use Shopify Dev MCP.
- Building a shopping assistant for customers? Look at Shopify’s Storefront and Checkout MCP.
- Running a store alone and comfortable with live changes? A community server or Shopify’s chat apps can work well.
- Running a store as a team, with different roles and a need to review changes? That is what Steward is for.
Get started
Follow Connect Shopify, choose scopes with the task-to-scope table, and invite your team with the right permissions.