在 Shopify 管理员中，转到**“设置”** > “应用和销售渠道”
单击**“开发应用程序”** （您可能需要先启用开发人员预览）
单击**“创建应用程序”**
为您的应用设置名称（例如“Shopify MCP Server”）
点击配置管理 API 范围
选择以下范围：
- read_products ， write_products
- read_customers ， write_customers
- read_orders ， write_orders
点击**“保存”**
点击**“安装应用程序”**
单击**“安装”**即可让应用访问您的商店数据
安装后，您将看到您的Admin API 访问令牌
复制此令牌 - 您将需要它进行配置

与 Claude Desktop 一起使用

将其添加到您的claude_desktop_config.json中：

{
  "mcpServers": {
    "shopify": {
      "command": "npx",
      "args": [
        "shopify-mcp",
        "--accessToken",
        "<YOUR_ACCESS_TOKEN>",
        "--domain",
        "<YOUR_SHOP>.myshopify.com"
      ]
    }
  }
}

Claude 桌面配置文件的位置：

MacOS： ~/Library/Application Support/Claude/claude_desktop_config.json
Windows： %APPDATA%/Claude/claude_desktop_config.json

替代方案：使用环境变量在本地运行

如果您更喜欢使用环境变量而不是命令行参数：

使用您的 Shopify 凭据创建一个.env文件：

SHOPIFY_ACCESS_TOKEN=your_access_token
MYSHOPIFY_DOMAIN=your-store.myshopify.com

使用 npx 运行服务器：
```
npx shopify-mcp-server
```

直接安装（可选）

如果要全局安装该包：

npm install -g shopify-mcp-server

然后运行它：

shopify-mcp-server --accessToken=<YOUR_ACCESS_TOKEN> --domain=<YOUR_SHOP>.myshopify.com

可用工具

产品管理

get-products
- 获取所有产品或按标题搜索
- 输入：
  - searchTitle （可选字符串）：按标题过滤产品
  - limit （数量）：返回的最大产品数量
get-product-by-id
- 通过 ID 获取特定产品
- 输入：
  - productId （字符串）：要检索的产品的 ID

客户管理

get-customers
- 获取客户或按姓名/电子邮件搜索
- 输入：
  - searchQuery （可选字符串）：按姓名或电子邮件过滤客户
  - limit （可选数字，默认值：10）：返回的最大客户数量
update-customer
- 更新客户信息
- 输入：
  - id （字符串，必需）：Shopify 客户 ID（仅限数字 ID，例如“6276879810626”）
  - firstName （字符串，可选）：客户的名字
  - lastName （字符串，可选）：客户的姓氏
  - email （字符串，可选）：客户的电子邮件地址
  - phone （字符串，可选）：客户的电话号码
  - tags （字符串数组，可选）：应用于客户的标签
  - note （字符串，可选）：关于客户的注释
  - taxExempt （布尔值，可选）：客户是否免税
  - metafields （对象数组，可选）：用于存储附加数据的客户元字段
get-customer-orders
- 获取特定客户的订单
- 输入：
  - customerId （字符串，必需）：Shopify 客户 ID（仅限数字 ID，例如“6276879810626”）
  - limit （可选数字，默认值：10）：返回的最大订单数量

订单管理

get-orders
- 通过可选过滤获取订单
- 输入：
  - status （可选字符串）：按订单状态过滤
  - limit （可选数字，默认值：10）：返回的最大订单数量
get-order-by-id
- 通过ID获取特定订单
- 输入：
  - orderId （字符串，必需）：完整的 Shopify 订单 ID（例如，“gid://shopify/Order/6090960994370”）
update-order
- 使用新信息更新现有订单
- 输入：
  - id （字符串，必需）：Shopify 订单 ID
  - tags （字符串数组，可选）：订单的新标签
  - email （字符串，可选）：更新客户电子邮件
  - note （字符串，可选）：订单备注
  - customAttributes （对象数组，可选）：订单的自定义属性
  - metafields （对象数组，可选）：排序元字段
  - shippingAddress （对象，可选）：送货地址信息

调试

如果遇到问题，请检查 Claude Desktop 的 MCP 日志：

tail -n 20 -f ~/Library/Logs/Claude/mcp*.log

执照

麻省理工学院

Available Tools

5 tools

get-customersD

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No
`searchQuery`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-ordersD

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No
`status`	No		any

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-product-by-idD

ParametersJSON Schema

Name	Required	Description	Default
`productId`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-productsD

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No
`searchTitle`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

update-orderD

ParametersJSON Schema

Name	Required	Description	Default
`customAttributes`	No
`email`	No
`id`	Yes
`metafields`	No
`note`	No
`shippingAddress`	No
`tags`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

5 tool updatesv1.0.0Apr 2, 2025
- First observedget-customers
- First observedget-orders
- First observedget-product-by-id
- First observedget-products
- First observedupdate-order

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.8/5.0

Scored 2026-04-18 10:40 across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose targeting specific Shopify resources: customers, orders, products, and order updates. There is no overlap in functionality, making it easy for an agent to select the correct tool for each task without confusion.

Naming Consistency4/5

The naming follows a consistent verb-noun pattern with hyphens (e.g., get-customers, update-order), which is predictable and readable. The minor deviation is that 'get-product-by-id' includes a preposition, slightly breaking the pure verb-noun style, but overall the pattern is clear and mostly uniform.

Tool Count3/5

With 5 tools, the count is reasonable for a Shopify integration, but it feels borderline thin for covering the domain comprehensively. While core read operations are present, the scope might benefit from additional tools for full CRUD or lifecycle coverage, such as creating or deleting resources.

Completeness2/5

The tool set has significant gaps for a Shopify server, focusing heavily on read operations (get-customers, get-orders, get-products) with only one update tool (update-order). Missing are create and delete operations for customers, orders, and products, as well as other common actions like inventory management or webhook handling, which limits agent workflows and could lead to failures in broader tasks.

Maintenance

ActivityInactive

ResponsivenessUnresponsive

Resources

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

Shopify B
io.github.pipeworx-io
Shopify MCP Pack — wraps the Shopify Admin REST API (2024-01)
E-commerce & Retail App Automation Cloud Platforms
412
SternifyOAuth
com.sternify.app
Manage a Shopify store's Sternify bundles, gifts, upsells, banners and reviews via OAuth.
E-commerce & Retail Marketing
1
Shopify Remote MCP Server A
com.hasdata
The public product catalogue and collections of any Shopify storefront, as structured JSON.
E-commerce & Retail Research & Data Web Scraping
218
ecwid A
io.usefulapi
Read store products, orders, customers, categories and coupons; adjust inventory and update orders.
E-commerce & Retail CRM
122

Related MCP Servers

Shopify MCP Server
E-commerce & Retail App Automation
amir-bengherbi
A
license
B
quality
D
maintenance
Enables interaction with Shopify store data using the GraphQL API, supporting product, customer, and order management with comprehensive error handling.
Updated 2 years ago (2025-01-27 22:57 UTC)
15
125 npm
18
MIT
Shopify MCP Server
E-commerce & Retail Databases Data Platforms
rezapex
-
license
Not graded
quality
Not graded
maintenance
Enables interaction with Shopify store data via GraphQL API, providing tools for managing products, customers, orders, discounts, and more with robust error handling.
Updated 2 years ago (2025-03-24 22:58 UTC)
125 npm
30
-
Shopify MCP Server
E-commerce & Retail App Automation
therealhexi
A
license
Not graded
quality
D
maintenance
Enables interaction with Shopify stores through GraphQL API, providing tools for managing products, customers, orders, and more.
Updated 2 years ago (2025-02-04 22:27 UTC)
125 npm
10
MIT
Shopify MCP Server
E-commerce & Retail Developer Tools RAG Systems
luckyfarnon
A
license
C
quality
D
maintenance
Enables interaction with Shopify store data through GraphQL API, providing tools for managing products, customers, orders, blogs, and articles.
Updated a year ago (2025-06-08 02:30 UTC)
15
2,216 npm
4
MIT

Shopify MCP 服务器

特征

先决条件

设置

Shopify 访问令牌

与 Claude Desktop 一起使用

替代方案：使用环境变量在本地运行

直接安装（可选）

可用工具

产品管理

客户管理

订单管理

调试

执照

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches