Shopify▌
by geli2001
Bridge your workflow to Shopify using the Shopify API for seamless product, order, and customer management—all via the S
Bridges to the Shopify GraphQL Admin API, enabling product searches, customer information retrieval, order management, and inventory updates without leaving your workflow.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / E-commerce store owners managing inventory
- / Developers building Shopify integrations
- / Customer service teams accessing order data
- / Marketing teams analyzing product collections
capabilities
- / Search and retrieve product information
- / Manage customer data and tags
- / Query and filter orders
- / Get products by collection or ID
- / Retrieve product variants
- / Execute GraphQL queries against Shopify Admin API
what it does
Connects to your Shopify store's GraphQL API to manage products, customers, orders, and discounts. Enables comprehensive store operations through Claude or other AI assistants.
about
Shopify is a community-built MCP server published by geli2001 that provides AI assistants with tools and capabilities via the Model Context Protocol. Bridge your workflow to Shopify using the Shopify API for seamless product, order, and customer management—all via the S It is categorized under developer tools.
how to install
You can install Shopify in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Shopify is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
Shopify MCP Server
(please leave a star if you like!)
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: shopify-mcp
🚀 Command: shopify-mcp (NOT shopify-mcp-server)
Features
- Product Management: Full CRUD for products, variants, and options
- Customer Management: Load customer data and manage customer tags
- Order Management: Advanced order querying and filtering
- GraphQL Integration: Direct integration with Shopify's GraphQL Admin API
- Comprehensive Error Handling: Clear error messages for API and authentication issues
Prerequisites
- Node.js (version 18 or higher)
- 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.
- From your Shopify admin, go to Settings > Apps and sales channels
- Click Develop apps > Build app in dev dashboard
- Create a new app and configure Admin API scopes:
read_products,write_productsread_customers,write_customersread_orders,write_orders
- Install the app on your store
- 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": [
"shopify-mcp",
"--clientId",
"<YOUR_CLIENT_ID>",
"--clientSecret",
"<YOUR_CLIENT_SECRET>",
"--domain",
"<YOUR_SHOP>.myshopify.com"
]
}
}
}
Static Access Token (legacy):
{
"mcpServers": {
"shopify": {
"command": "npx",
"args": [
"shopify-mcp",
"--accessToken",
"<YOUR_ACCESS_TOKEN>",
"--domain",
"<YOUR_SHOP>.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 shopify-mcp \
--clientId YOUR_CLIENT_ID \
--clientSecret YOUR_CLIENT_SECRET \
--domain your-store.myshopify.com
Static Access Token (legacy):
claude mcp add shopify -- npx 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:
-
Create a
.envfile with your Shopify credentials:Client Credentials:
SHOPIFY_CLIENT_ID=your_client_id SHOPIFY_CLIENT_SECRET=your_client_secret MYSHOPIFY_DOMAIN=your-store.myshopify.comStatic Access Token (legacy):
SHOPIFY_ACCESS_TOKEN=your_access_token MYSHOPIFY_DOMAIN=your-store.myshopify.com -
Run the server with npx:
npx shopify-mcp
Direct Installation (Optional)
If you want to install the package globally:
npm install -g 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-01). Can also be set viaSHOPIFY_API_VERSIONenvironment 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 shopify-mcp, not shopify-mcp-server.
Available Tools
Product Management
-
get-products- Get all products or search by title
- Inputs:
searchTitle(optional string): Filter products by titlelimit(number): Maximum number of products to return
-
get-product-by-id- Get a specific product by ID
- Inputs:
productId(string): ID of the product to retrieve
-
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). Usemanage-product-variantswithstrategy: REMOVE_STANDALONE_VARIANTafterward to create all real variants with prices. - Inputs:
title(string, required): Title of the productdescriptionHtml(string, optional): Description with HTMLhandle(string, optional): URL slug. Auto-generated from title if omittedvendor(string, optional): Vendor of the productproductType(string, optional): Type of the producttags(array of strings, optional): Product tagsstatus(string, optional):"ACTIVE","DRAFT", or"ARCHIVED". Default"DRAFT"seo(object, optional):{ title, description }for search enginesmetafields(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
- Create a new product. When using
-
update-product- Update an existing product's fields
- Inputs:
id(string, required): Shopify product GIDtitle(string, optional): New titledescriptionHtml(string, optional): New descriptionhandle(string, optional): New URL slugvendor(string, optional): New vendorproductType(string, optional): New product typetags(array of strings, optional): New tags (overwrites existing)status(string, optional):"ACTIVE","DRAFT", or"ARCHIVED"seo(object, optional):{ title, description }for search enginesmetafields(array of objects, optional): Metafields to set or updatecollectionsToJoin(array of strings, optional): Collection GIDs to add the product tocollectionsToLeave(array of strings, optional): Collection GIDs to remove the product fromredirectNewHandle(boolean, optional): If true, old handle redirects to new handle
-
delete-product- Delete a product
- Inputs:
id(string, required): Shopify product GID
-
manage-product-options- Create, update, or delete product options (e.g. Size, Color)
- Inputs:
productId(string, required): Shopify product GIDaction(string, required):"create","update", or"delete"- For
action: "create":options(array, required): Options to create, e.g.[{ name: "Size", values: ["S", "M", "L"] }]
- For
action: "update":optionId(string, required): Option GID to updatename(string, optional): New name for the optionposition(number, optional): New positionvaluesToAdd(array of strings, optional): Values to addvaluesToDelete(array of strings, optional): Value GIDs to remove
- For
action: "delete":optionIds(array of strings, required): Option GIDs to delete
-
manage-product-variants- Create or update product variants in bulk
- Inputs:
productId(string, required): Shopify product GIDstrategy(string, optional): How to handle the default variant when creating."DEFAULT"(removes "Default Title" automatically),"REMOVE_STANDALONE_VARIANT"(recommended for full control), or"PRESERVE_STANDALONE_VARIANT"variants(array, required): Variants to create or update. Each variant:id(string, optional): Variant GID for updates. Omit to create newprice(string, optional): Price, e.g."49.00"compareAtPrice(string, optional): Compare-at price for showing discountssku(string, optional): SKU (mapped toinventoryItem.sku)tracked(boolean, optional): Whether inventory is tracked. Setfalsefor print-on-demandtaxable(boolean, optional): Whether the variant is taxablebarcode(string, optional): BarcodeoptionValues(array, optional): Option values, e.g.[{ optionName: "Size", name: "A4" }]
-
delete-product-variants- Delete one or more variants from a product
- Inputs:
productId(string, required): Shopify product GIDvariantIds(array of strings, required): Variant GIDs to delete
Customer Management
-
get-customers- Get customers or search by name/email
- Inputs:
searchQuery(optional string): Filter customers by name or emaillimit(optional number, default: 10): Maximum number of customers to return
-
update-customer- Update a customer's information
- Inputs:
id(string, required): Shopify customer ID (numeric ID only, like "6276879810626")firstName(string, optional): Customer's first namelastName(string, optional): Customer's last nameemail(string, optional): Customer's email addressphone(string, optional): Customer's phone numbertags(array of strings, optional): Tags to apply to the cus
FAQ
- What is the Shopify MCP server?
- Shopify is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Shopify?
- This profile displays 34 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.5★★★★★34 reviews- ★★★★★Lucas Tandon· Dec 24, 2024
I recommend Shopify for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★William Chawla· Dec 20, 2024
According to our notes, Shopify benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Dhruvi Jain· Dec 12, 2024
Shopify is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Noor Diallo· Dec 4, 2024
Shopify has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Evelyn Gonzalez· Dec 4, 2024
Useful MCP listing: Shopify is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Kabir Abbas· Nov 23, 2024
Shopify is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Anaya Verma· Nov 15, 2024
We evaluated Shopify against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Oshnikdeep· Nov 3, 2024
Useful MCP listing: Shopify is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Ganesh Mohane· Oct 22, 2024
Shopify reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Kabir Choi· Oct 14, 2024
We wired Shopify into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
showing 1-10 of 34