Skip to content
Custom Connectors

Connect Shopify to Claude Code

Have Claude edit products, move inventory, and fulfill orders in Shopify. From the terminal, inside the sessions where you already work.

How do you connect Shopify to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Shopify, you add a Shopify MCP server: a small hosted service that exposes Shopify's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Shopify account. No API keys pasted into config files.

claude mcp add --transport http shopify https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Shopify once connected?

Full read-write Shopify access lets Claude update product titles, prices, and descriptions, adjust inventory across locations, create and edit draft orders, mark orders fulfilled, and reply to or tag customers. The merchandising and order work that used to mean clicking through the admin happens where the store already runs.

  • Update a product's title, description, price, or tags
  • Adjust inventory levels for variants across store locations
  • Create a draft order and apply a discount before it is sent
  • Mark an order fulfilled and attach tracking once you approve
  • Add tags or notes to a customer record for segmentation
  • Publish or unpublish a product to a sales channel

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Shopify access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Shopify API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Shopify changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Shopify connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Shopify connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Shopify account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Shopify's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Shopify?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Shopify account it signs in with. Revoking access is one click in Shopify.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.