shopify-mcp
An MCP server providing six scoped tools for Shopify's Admin API, enabling natural-language querying of chargebacks, orders, refunds, customers, and revenue.
README
Shopify MCP Server
A Model Context Protocol (MCP) server that gives Claude — or any MCP-compatible AI client — six scoped tools for a Shopify store's Admin API. Ask plain-English questions about chargebacks, orders, refunds, customers, and revenue; get answers grounded in live store data.
Ships with a mock-data mode enabled by default. Clone, pip install, run, and see Claude answering questions end-to-end — no store or credentials required.
What it does
Six tools, each a small Python function with a docstring the model reads:
| Tool | What it does |
|---|---|
get_disputes(status?, limit=25) |
List chargebacks and inquiries, optionally filtered by status |
chargeback_rate(days=30) |
Dispute count / order count over N days as a percentage — with a healthy / watch / high risk flag |
get_orders(status?, limit=25) |
Recent order feed, most recent first |
search_customers(query, limit=10) |
Lookup by email, name, or phone |
get_refunds(order_id?, limit=25) |
Refund history for one order or store-wide |
dispute_details(dispute_id) |
Full case data for a single dispute — status, reason, amount, evidence deadline |
Under the hood: standard Shopify Admin REST API against 2025-07. No third-party integrations, no hidden state — the server holds no data, just proxies queries.
Quickstart — mock mode (no store needed)
git clone https://github.com/weli-dev/shopify-mcp
cd shopify-mcp
pip install -r requirements.txt
python src/server.py
You'll see shopify-mcp starting: MOCK MODE (no live store). Every tool call returns realistic sample data — enough to demo the pattern to a stakeholder without touching a real store.
Quickstart — live Shopify data
Create a Shopify Admin API access token (Settings → Apps → Develop apps → create app → grant scopes). Then:
export SHOPIFY_STORE_URL="your-store.myshopify.com"
export SHOPIFY_ADMIN_TOKEN="shpat_..."
python src/server.py
The server prints LIVE (your-store.myshopify.com) and hits the real Admin API on every tool call. Read-only scopes are enough for the six tools included.
Connect it to Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"shopify": {
"command": "python",
"args": ["/absolute/path/to/shopify-mcp/src/server.py"],
"env": {
"SHOPIFY_STORE_URL": "your-store.myshopify.com",
"SHOPIFY_ADMIN_TOKEN": "shpat_..."
}
}
}
}
Restart Claude Desktop. Ask "What's our chargeback rate over the last 30 days?" — watch Claude call chargeback_rate, then call get_disputes on its own to explain the drivers.
Example session (mock mode)
You: What's our chargeback rate this month, and what's driving it?
Claude: Chargeback rate over the last 30 days: 1.21% (5 disputes / 412 orders).
That flags as "watch" — above the 0.9% comfort zone but not yet in the
1.5%+ range where payment processors intervene.
Driver breakdown from get_disputes:
• 2 chargebacks marked fraudulent ($399.99 combined)
• 1 chargeback for product_not_received ($245.00)
• 1 chargeback for credit_not_processed ($199.99)
• 1 chargeback for duplicate ($67.25)
Two of the five are still needs_response — evidence deadlines are
2026-07-20 and 2026-08-14. Want me to pull dispute_details on those
so you can prep evidence?
That's the whole pattern: the model chains its own tool calls, grounds every claim in live data, and asks a useful follow-up.
Why this pattern matters
MCP is the emerging standard for giving AI models safe, scoped access to real systems — CRMs, ecommerce platforms, databases, internal APIs. This repo is a minimal, honest reference implementation for the Shopify layer: read-only, no hidden magic, one file to audit.
The same shape scales to production: add tools for create_evidence, issue_refund, update_order when you're ready to grant write access; wrap them in whatever approval flow your ops team requires. The pattern doesn't change — just what the tools do.
Built by
I build AI-agent and automation systems — Claude Code / MCP integrations, LLM-into-workflow tooling, and scripts that kill repetitive work for ecommerce operators. If you need a custom MCP wired into your Shopify (or Stripe, or CRM, or database), that's the work I do.
- Upwork: its_weli on Upwork
- Contact: hello@weli.build
- Site: weli.build
License
MIT — use it, fork it, ship it.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。