Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Shopify

by kisasaversion 1.2.0i★ –iRuns on your computer
Registry nameio.github.kisasa/shopify-mcp

Install

Overview

Description from the maker (original English)

Shopify Admin API tools: products, media, orders, customers, inventory, and sales channels

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Online shops & payments
  • You need to fill in: MYSHOPIFY_DOMAIN, SHOPIFY_CLIENT_SECRET, SHOPIFY_ACCESS_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: MYSHOPIFY_DOMAIN, SHOPIFY_CLIENT_ID, SHOPIFY_CLIENT_SECRET, SHOPIFY_ACCESS_TOKEN, SHOPIFY_API_VERSION

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "shopify": {
      "command": "npx",
      "args": [
        "-y",
        "@kisasa/shopify-mcp"
      ],
      "env": {
        "MYSHOPIFY_DOMAIN": "your-value",
        "SHOPIFY_CLIENT_ID": "your-value",
        "SHOPIFY_CLIENT_SECRET": "your-value",
        "SHOPIFY_ACCESS_TOKEN": "your-value",
        "SHOPIFY_API_VERSION": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add shopify --env MYSHOPIFY_DOMAIN=your-value --env SHOPIFY_CLIENT_ID=your-value --env SHOPIFY_CLIENT_SECRET=your-value --env SHOPIFY_ACCESS_TOKEN=your-value --env SHOPIFY_API_VERSION=your-value -- npx -y @kisasa/shopify-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "shopify": {
      "command": "npx",
      "args": [
        "-y",
        "@kisasa/shopify-mcp"
      ],
      "env": {
        "MYSHOPIFY_DOMAIN": "your-value",
        "SHOPIFY_CLIENT_ID": "your-value",
        "SHOPIFY_CLIENT_SECRET": "your-value",
        "SHOPIFY_ACCESS_TOKEN": "your-value",
        "SHOPIFY_API_VERSION": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "shopify": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@kisasa/shopify-mcp"
      ],
      "env": {
        "MYSHOPIFY_DOMAIN": "your-value",
        "SHOPIFY_CLIENT_ID": "your-value",
        "SHOPIFY_CLIENT_SECRET": "your-value",
        "SHOPIFY_ACCESS_TOKEN": "your-value",
        "SHOPIFY_API_VERSION": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • MYSHOPIFY_DOMAIN required env
    Your store's myshopify.com domain
  • SHOPIFY_CLIENT_ID env
    Client ID of a Dev Dashboard app (use with SHOPIFY_CLIENT_SECRET, or set SHOPIFY_ACCESS_TOKEN instead)
  • SHOPIFY_CLIENT_SECRET secret env
    Client secret of a Dev Dashboard app
  • SHOPIFY_ACCESS_TOKEN secret env
    Static Admin API access token (shpat_...) for legacy custom apps, instead of client ID/secret
  • SHOPIFY_API_VERSION env
    Shopify Admin API version

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account kisasa, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Online shops & paymentsi

  • More stars than 0% of the other 2547 servers in this category
  • Published to the registry more recently than 78% of the other 2547 servers in this category
  • Basic checks equal to or better than 100% of the other 2547 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Shopify safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: MYSHOPIFY_DOMAIN, SHOPIFY_CLIENT_SECRET, SHOPIFY_ACCESS_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.2.0) reached the registry 8 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Stripe MCP

by stripe

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

Runs in the cloud★ 2,043MITUpdated 12 months ago
Install

MCP Cn Commerce

by TonyWang-hub

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

Runs on your computer★ 96MITUpdated 29 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Shopify MCP Server

MCP Server for Shopify API, enabling interaction with store data through GraphQL API. This server provides tools for managing products, customers, orders, and more.

📦 Package Name: `@kisasa/shopify-mcp` 🚀 Command: `shopify-mcp` (NOT `shopify-mcp-server`)

Built on lucasjahn/shopify-mcp, itself a fork of GeLi2001/shopify-mcp. See Credits.

Features

  • Product Management: Full CRUD for products, variants, and options, including variant images and inventory policy (8 tools)
  • Product Media: Attach images to products by URL and check processing status (2 tools)
  • Sales Channel Publishing: List sales channels and publish or unpublish products on them (4 tools)
  • Customer Management: Full CRUD, merge, and address management (8 tools)
  • Order Management: Smart lookup, cancel, close/open, mark as paid, fulfillment, refunds (10 tools)
  • Metafield Management: Get, set, and delete metafields on any resource (3 tools)
  • Collection Management: List collections and get collection details with products (2 tools)
  • Configuration & Discovery: Shop info, metafield definitions, locations, markets (5 tools)
  • Inventory & Pricing: Set quantities and unit costs, view levels/items, price lists, detailed variants (6 tools)
  • Tag Management: Add/remove tags on any taggable resource, including bulk operations (2 tools)
  • Enhanced Order Tools: Transactions, fulfillment orders, refund details (3 tools)
  • Field Selection: All GET tools support a fields parameter to fetch only the data you need
  • Count-Only Mode: List tools support countOnly to get result counts without fetching data
  • Pagination & Sorting: Cursor-based pagination and sort keys on all list queries
  • Advanced Filtering: Pass-through Shopify query syntax for all list endpoints
  • GraphQL Integration: Direct integration with Shopify's GraphQL Admin API (2026-10)
  • Comprehensive Error Handling: Clear error messages for API and authentication issues

Prerequisites

  1. Node.js (version 18 or higher)
  2. A Shopify store with a custom app (see setup instructions below)

Setup

Authentication

This server supports two authentication methods:

Option 1: Client Credentials (Dev Dashboard apps, January 2026+)

As of January 1, 2026, new Shopify apps are created in the Dev Dashboard and use OAuth client credentials instead of static access tokens.

  1. From your Shopify admin, go to Settings > Apps and sales channels
  2. Click Develop apps > Build app in dev dashboard
  3. Create a new app and configure Admin API scopes. The core scopes are:
  • read_products, write_products
  • read_customers, write_customers
  • read_orders, write_orders

Some tools need additional scopes. Add only the ones for features you use:

ScopesNeeded for
read_all_ordersOrders older than 60 days (otherwise order tools only see recent orders)
read_inventory, write_inventoryget-inventory-levels, inventory-set-quantities, update-inventory-item
read_locationsget-locations, get-inventory-levels
read_marketsget-markets
read_draft_orders, write_draft_orderscreate-draft-order, complete-draft-order
read_merchant_managed_fulfillment_orders, write_merchant_managed_fulfillment_ordersget-fulfillment-orders, create-fulfillment
read_publications, write_publicationsget-publications, get-product-publications, publish-product, unpublish-product

For every tool, the full list is:

   read_products,write_products,read_customers,write_customers,read_orders,write_orders,read_all_orders,read_inventory,write_inventory,read_locations,read_markets,read_draft_orders,write_draft_orders,read_merchant_managed_fulfillment_orders,write_merchant_managed_fulfillment_orders,read_publications,write_publications

After changing scopes, release a new app version, approve it on the store, and restart the MCP server so it fetches a token with the new scopes.

  1. Install the app on your store
  2. Copy your Client ID and Client Secret from the app's API credentials

The server will automatically exchange these for an access token and refresh it before it expires (tokens are valid for ~24 hours).

Option 2: Static Access Token (legacy apps)

If you have an existing custom app with a static shpat_ access token, you can still use it directly.

Usage with Claude Desktop

Client Credentials (recommended):

{

"mcpServers": { "shopify": { "command": "npx", "args": [ "@kisasa/shopify-mcp", "--clientId", " ", "--clientSecret", " ", "--domain", " .myshopify.com" ] } } }

Client Credentials via environment variables (keeps secrets out of the command line):

{

"mcpServers": { "shopify": { "command": "npx", "args": ["-y", "@kisasa/shopify-mcp"], "env": { "MYSHOPIFY_DOMAIN": " .myshopify.com", "SHOPIFY_CLIENT_ID": " ", "SHOPIFY_CLIENT_SECRET": " " } } } }

To connect more than one store, add one entry per store with a different name (e.g. "shopify-store-a", "shopify-store-b").

Static Access Token (legacy):

{

"mcpServers": { "shopify": { "command": "npx", "args": [ "@kisasa/shopify-mcp", "--accessToken", " ", "--domain", " .myshopify.com" ] } } }

Locations for the Claude Desktop config file:

  • MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%/Claude/claude_desktop_config.json
Usage with Claude Code

Client Credentials:

claude mcp add shopify -- npx @kisasa/shopify-mcp \

--clientId YOUR_CLIENT_ID \ --clientSecret YOUR_CLIENT_SECRET \ --domain your-store.myshopify.com

Static Access Token (legacy):

claude mcp add shopify -- npx @kisasa/shopify-mcp \

--accessToken YOUR_ACCESS_TOKEN \ --domain your-store.myshopify.com

Alternative: Run Locally with Environment Variables

If you prefer to use environment variables instead of command-line arguments:

  1. Create a .env file with your Shopify credentials:

Client Credentials:

   SHOPIFY_CLIENT_ID=your_client_id

SHOPIFY_CLIENT_SECRET=your_client_secret MYSHOPIFY_DOMAIN=your-store.myshopify.com

Static Access Token (legacy):

   SHOPIFY_ACCESS_TOKEN=your_access_token

MYSHOPIFY_DOMAIN=your-store.myshopify.com

  1. Run the server with npx:
   npx @kisasa/shopify-mcp
Direct Installation (Optional)

If you want to install the package globally:

npm install -g @kisasa/shopify-mcp

Then run it:

shopify-mcp --clientId=<ID> --clientSecret=<SECRET> --domain=<YOUR_SHOP>.myshopify.com
Additional Options
  • --apiVersion: Specify the Shopify API version (default: 2026-10). Can also be set via SHOPIFY_API_VERSION environment variable.

⚠️ Important: If you see errors about "SHOPIFY_ACCESS_TOKEN environment variable is required" when using command-line arguments, you might have a different package installed. Make sure you're using @kisasa/shopify-mcp, not shopify-mcp-server or the unscoped shopify-mcp.

Available Tools (52)

Shared Capabilities

All list query tools (get-products, get-customers, get-orders, get-customer-orders, get-collections) support:

  • Cursor-based pagination: after / before (cursor strings), with pageInfo in the response (hasNextPage, hasPreviousPage, startCursor, endCursor)
  • Sorting: sortKey (enum specific to each resource) and reverse (boolean)
  • Advanced filtering: query or searchQuery parameter accepting Shopify query syntax
  • Field selection: fields parameter to fetch only specific fields, reducing response size
  • Count-only mode: countOnly parameter returns { count: N } without fetching any resource data — useful for sizing queries before paginating
Product Management (8 tools)
  1. `get-products`
  • Get all products or search by title with pagination and sorting
  • Inputs:
  • searchTitle (string, optional): Filter products by title (wraps in title:*...*)
  • limit (number, default: 10): Maximum number of products to return
  • query (string, optional): Raw Shopify query string (e.g. "status:active vendor:Nike tag:sale")
  • sortKey (string, optional): One of CREATED_AT, ID, INVENTORY_TOTAL, PRODUCT_TYPE, PUBLISHED_AT, RELEVANCE, TITLE, UPDATED_AT, VENDOR
  • reverse (boolean, optional): Reverse the sort order
  • after / before (string, optional): Pagination cursors
  • fields (array, optional): Fields to fetch. Available: id, title, description, handle, status, createdAt, updatedAt, totalInventory, vendor, productType, tags, mediaCount, priceRange, media, variants (first 10, with id, title, price, inventoryQuantity, sku, barcode, inventoryPolicy)
  • countOnly (boolean, optional): Return only { count: N }
  1. `get-product-by-id`
  • Get a specific product by ID with full details including SEO, options, media, variants, and collections
  • Inputs:
  • productId (string, required): Shopify product GID
  • Returns: productType, descriptionHtml, seo, options (with optionValues), media (images), variants, collections, tags, vendor, price range, inventory
  1. `create-product`
  • Create a new product. When using productOptions, Shopify registers all option values but only creates one default variant (first value of each option, price $0). Use manage-product-variants with strategy: REMOVE_STANDALONE_VARIANT afterward to create all real variants with prices.
  • Inputs:
  • title (string, required): Title of the product
  • descriptionHtml (string, optional): Description with HTML
  • handle (string, optional): URL slug. Auto-generated from title if omitted
  • vendor (string, optional): Vendor of the product
  • productType (string, optional): Type of the product
  • tags (array of strings, optional): Product tags
  • status (string, optional): "ACTIVE", "DRAFT", or "ARCHIVED". Default "DRAFT"
  • seo (object, optional): { title, description } for search engines
  • metafields (array of objects, optional): Custom metafields (namespace, key, value, type)
  • productOptions (array of objects, optional): Options to create inline, e.g. [{ name: "Size", values: [{ name: "S" }, { name: "M" }] }]. Max 3 options.
  • collectionsToJoin (array of strings, optional): Collection GIDs to add the product to
  1. `update-product`
  • Update an existing product's fields
  • Inputs:
  • id (string, required): Shopify product GID
  • title (string, optional): New title
  • descriptionHtml (string, optional): New description
  • handle (string, optional): New URL slug
  • vendor (string, optional): New vendor
  • productType (string, optional): New product type
  • tags (array of strings, optional): New tags (overwrites existing)
  • status (string, optional): "ACTIVE", "DRAFT", or "ARCHIVED"
  • seo (object, optional): { title, description } for search engines
  • metafields (array of objects, optional): Metafields to set or update
  • collectionsToJoin (array of strings, optional): Collection GIDs to add the product to
  • `collectionsToLeav

Only the beginning is shown; read the rest in the repo

Ask PopNx