Skip to main content
    Case Study · AI Connector

    Every Client Store in One AI - A Multi-store Shopify Connector

    Every Store, One ConversationNo Disconnecting and ReconnectingMore of the Shopify API

    Company

    A NZ digital agency

    Industry

    Ecommerce and web agency

    What We Built

    A multi-store Shopify connector (MCP server) for Claude

    Connected To

    Every Shopify store the agency manages, its own and its clients'

    The Challenge

    A digital agency looks after Shopify stores for itself and for clients. The team uses Claude to update products, check orders, write content and fix themes. But Shopify's own connector works with one store at a time. Every time someone moved to another client, they had to disconnect, reconnect and sign in again, on every computer.

    Some jobs it couldn't do at all, and any question across all the stores meant asking the same thing store by store.

    What We Built

    One connector for every store. Each tool takes a store name, a list of stores or "all", so the AI works across the whole client list in one conversation. Store logins are kept securely in the cloud, so a store added once is ready on every computer in the team. A new client store is added by sending the merchant a single install link to approve.

    We matched every tool in Shopify's own connector, then went further: theme editing with rollback, bulk operations, file uploads, menus, translations, markets, policies and full Admin API access for anything else.

    91

    Tools across products, orders, content, themes and settings

    0

    Times anyone needs to disconnect and reconnect a store

    1

    Install link for a client to approve a new store

    What It Does

    Built for Looking After Many Stores

    Everything an agency team does in Shopify, across every client, from one AI.

    Every store, one conversation

    Every tool takes a store: one, a list, or all of them. "Which of our stores have products with no images?" checks every store in one go.

    No more reconnecting

    Store logins are kept centrally, so once a store is added it works on every computer in the team, and keeps working without anyone signing in again.

    More of the Shopify API

    Dedicated tools for the everyday jobs, plus full Admin API access for the rest: refunds, order edits, fulfilment, returns, markets, shipping and more.

    Theme work, done safely

    Duplicate the live theme, edit the copy, preview, then publish. Publishing returns a ready-made rollback, and the live theme is protected unless you explicitly allow it.

    Bulk jobs

    Bulk queries and bulk updates across thousands of products, with a dry run first and a report of any rows that failed.

    Confirm before it counts

    Anything destructive, and any change to more than one store, needs an explicit confirm. Shop policies are backed up before they're replaced.

    Compared

    Our Shopify Connector vs Shopify's Own

    Why an agency outgrows the single-store connector.

    Our Shopify Connector vs Shopify's Own
    Our multi-store connectorShopify's connector
    Several stores in one conversationYesNoSwitch store each time
    Run one request across all storesYesNo
    Shared across the team's computersYesNo
    Client stores added by install linkYesNo
    Theme edit, preview, publish and roll backYesNoLimited
    Bulk operations with a dry runYesNo
    Confirm step on destructive and multi-store changesYesNo
    Based on the official Shopify connector tools as at November 2026. We kept Shopify's own developer docs connector installed alongside ours for documentation search.

    Guard Rails for Client Stores

    Working on someone else's store needs care. Changes to more than one store, deletes, theme publishes and policy changes all need an explicit confirm, and nothing is sent without it. The live theme is protected, publishing returns the exact call to roll back, and a policy is saved before it's replaced. Tokens and secrets are never logged or returned to the AI.

    Under the Hood

    • Shopify Admin GraphQL API: pinned to a tested API version, with built-in handling of Shopify's query cost limits.
    • Model Context Protocol: one server used from Claude Desktop and Claude Code on Windows and Mac.
    • AWS: a small install service and an encrypted token store shared by the team.

    The Outcome

    The team moves between client stores mid-conversation, asks questions across every store at once, and does theme and bulk work that used to mean logging into each admin. Nobody disconnects or reconnects anything.

    Looking After More Than One Store?

    We can set up a multi-store connector for your agency or group of brands.

    Talk to us: 04 280 4077

    Free 30-min call · We'll show you 2–3 things to automate first · No obligation

    More Success Stories

    See how we've helped other New Zealand businesses transform with AI automation

    Retro Bowl

    Hospitality

    An AI voice agent answering the phone in a busy eight-lane bowling alley, plus front-counter texting.

    Read case study

    Packaging Products

    E-commerce

    +20% ROAS in month one; social restarted after a 12-month gap.

    Read case study

    Packaging Products Sales Reporting

    E-commerce

    Custom dashboard reveals hidden cash sales patterns and high-value clients.

    Read case study