shopify-admin-mcp
MCP server for Shopify's Admin GraphQL API: typed tools for common store tasks, raw GraphQL for everything else, and live schema search so your AI assistant works against the exact API your store serves. Targets API version .
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y @acodera/[email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add acodera-shopify-admin-mcp -- npx -y @acodera/shopify-admin-mcp@1.13.0รันในเทอร์มินัล
{ "mcpServers": { "acodera-shopify-admin-mcp": { "command": "npx", "args": [ "-y", "@acodera/[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
MCP server for Shopify's Admin GraphQL API: typed tools for common store tasks, raw GraphQL for everything else, and live schema search so your AI assistant works against the exact API your store serves. Targets API version .
MCP server providing full access to Shopify's Admin GraphQL API with schema introspection
--theme-dir, theme writes send files by filename and a pull tool copies them back, so file content never has to pass through the conversation.mcp.json for youshpat_ tokensRun the setup wizard in your project folder:
npx -y @acodera/shopify-admin-mcp@latest setup
It runs on macOS, Linux and Windows. It checks your Node.js version, then asks what to set up:
.mcp.json. Theme edits are turned off (--disable-theme-writes), so the assistant can read themes but not change them; everything else, such as products and metafields, can be changed. Local files, such as product images, are uploaded from ./uploads, which setup creates, unless .mcp.json already sets an upload folder../theme and writes CLAUDE.md, THEME.md and customizations.md from acoderacom/claude-horizon, with the store and live theme filled in to CLAUDE.md. It switches on what CLAUDE.md describes: live theme writes, theme files from ./theme, uploads from ./uploads, and the Shopify Dev MCP. The store's live theme must be a Horizon version the template supports (listed in its versions.json), and the project gets that exact version. Otherwise setup says which version to switch to and stops without writing .mcp.json. Since the Shopify theme store only installs the newest Horizon, it offers to save an upload-ready horizon-<version>.zip for Online Store → Themes → Add theme → Upload zip file.--lock-themes), so the server refuses any change to the live theme and any theme create, duplicate, rename, delete or publish: you publish the copy yourself. Setup writes CLAUDE.md (no mockup rules) and customizations.md from the template's live-site/ folder with the store and the copy's name, version and ID filled in, a blank THEME.md, and an empty ./theme. Then, by hand: download the copy (⋯ → Download theme file) and unzip it into ./theme, and, when you want, ask Claude to learn the theme: it writes THEME.md from ./theme, which stays blank until then. Store data such as products and menus is shared with the live site, so changes to it still show at once; CLAUDE.md has Claude ask first. Running setup again keeps ./theme, THEME.md and the chosen copy unless you change them.Current values are prefilled and other servers are kept. Setup doesn't ask about the other options, such as read-only mode, toolsets or raw GraphQL; set them in .mcp.json by hand. Running "Connect to a store only" again keeps them; both theme design modes set the ones CLAUDE.md depends on. The secret is saved in plain text, so the file is added to .gitignore in a git repo and, on macOS and Linux, written readable only by you. Windows has no such file mode, so the file gets its folder's permissions: keep the project inside your user folder, where other users can't read it. Restart Claude Code (or run /mcp) to connect.
With Claude Code:
claude mcp add shopify \
-e SHOPIFY_STORE=mystore.myshopify.com \
-e SHOPIFY_CLIENT_ID=your_client_id \
-e SHOPIFY_CLIENT_SECRET=your_client_secret \
-- npx -y @acodera/shopify-admin-mcp
Or in .mcp.json, or the Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"shopify": {
"command": "npx",
"args": ["-y", "@acodera/shopify-admin-mcp"],
"env": {
"SHOPIFY_STORE": "mystore.myshopify.com",
"SHOPIFY_CLIENT_ID": "${SHOPIFY_CLIENT_ID}",
"SHOPIFY_CLIENT_SECRET": "${SHOPIFY_CLIENT_SECRET}"
}
}
}
}
For a legacy token, set SHOPIFY_ACCESS_TOKEN instead of the client ID and secret. Claude Code expands ${VAR} from your shell, so .mcp.json can be committed without secrets; Claude Desktop doesn't, so write the values there directly.
shop_not_permitted. In setup, choose Client ID and secret, approved in the browser. It prints a redirect URL, http://localhost:3457/auth/callback, to add to the app's version in the Dev Dashboard (then release the version), opens Shopify's approval page, and exchanges the approval for an offline access token that lasts until the app is uninstalled or its secret is rotated. The client secret is only used for the approval; .mcp.json gets the access token.shpat_ token of an existing custom app.Grant only the scopes for the tools you use:
Customer names, emails, phone numbers, and addresses are protected customer data, which your app must also be approved for.
Always available: shopify_graphql (any query or mutation; queries only in read-only mode), shopify_schema_search, and shopify_schema_details. The rest are grouped into toolsets, all registered by default:
A few inputs follow API 2026-10: collections define their products with sources (see CollectionCreateSourceTargetInput in shopify_schema_details), shopify_inventory_adjust needs the quantity you expect before the change (changeFromQuantity), and a discount takes one kind of eligibility (customerIds, customerSegmentIds, or marketIds) and items by collection or by product, not both.
Theme files are usually edited in a local copy of the theme first. Sending a file's content through shopify_theme_files_upsert makes the assistant write out the whole file, which takes minutes for a large section. With --theme-dir pointing at the local copy:
shopify_theme_files_upsert sends a file given only its filename from that folder: text as text, anything else as base64. When Shopify's write job is done, it reports for each file whether Shopify stored it as sent. Shopify regenerates JSON files such as templates (adding its header and reformatting them), so a file it returns changed is replaced in the folder with Shopify's copy.shopify_theme_files_pull copies files or patterns such as sections/* from a theme into the folder, up to 50 per call, and returns only filenames and checksums. Files that already match are left alone.Files passed with content, contentBase64 or url work as before.
--read-only) registers only tools that read data and rejects mutations in raw GraphQL. The document is parsed, so comments or extra operations can't slip one through. Use it whenever the assistant doesn't need to change the store: product descriptions and customer notes are written by other people and can carry instructions.--toolsets products,orders) shorten the tool list, but raw GraphQL can still reach anything your scopes allow. Add --disable-raw-graphql to keep the assistant to the selected toolsets. Either way, the app's scopes are the real limit.MAIN) theme are refused, including through raw GraphQL, where themePublish is refused too. Duplicate the theme, edit the copy, and publish it from the Shopify admin, or start with --allow-live-theme-writes.--disable-theme-writes: the theme write tools are left out, and raw GraphQL refuses every theme mutation (file writes, themeCreate, themeUpdate, themeDelete, themeDuplicate, themePublish) whichever theme it targets. It overrides --allow-live-theme-writes, and setup's "Connect to a store only" mode turns it on.--lock-themes: theme files can still be edited, but shopify_theme_duplicate and shopify_theme_delete are left out, and raw GraphQL refuses themeCreate, themeDuplicate, themeUpdate, themeDelete and themePublish, so copies can't be deleted or renamed and nothing can be published. Setup's "Full theme edit live site" mode turns it on.--theme-dir) is the only place theme files are sent from and pulled into. Paths that lead outside it, symlinks included, and files outside the theme's own folders (assets, blocks, config, layout, locales, sections, snippets, templates) are refused.--upload-dir (setup sets ./uploads in both modes). shopify_file_upload then accepts files inside that folder (symlinks resolved), as well as public URLs that Shopify fetches itself.*.myshopify.com, and the server warns when secrets are passed as flags, since other processes can see them.Every option works as a flag after the package name (in args) or as an environment variable (in env):
For example: "args": ["-y", "@acodera/shopify-admin-mcp", "--read-only", "--toolsets", "products,orders,customers"].
true or 1. When an option is set both ways, the flag wins; for on/off options, either one turns it on.${VAR}, $VAR) count as not set, so one config can list both auth methods. If both are filled in, the access token is used.--upload-dir and --theme-dir, since MCP clients start the server from their own working directory.--api-version, raw GraphQL works but some tools may not. The server logs a warning if Shopify serves a different version than the one requested.The server introspects the live schema in the background once it connects. shopify_schema_search finds types, queries, and mutations by keyword, and shopify_schema_details shows a type's fields or an operation's arguments. Deprecated fields are left out, which steers the assistant toward the current API.
git clone https://github.com/acoderacom/shopify-admin-mcp.git
cd shopify-admin-mcp && git checkout dev && npm install
npm run build # or `npm run dev` to rebuild on change
npm test # unit tests; live tests skip themselves without credentials
npm run lint # type-check src and tests
Requires Node.js 22.12 or later. Setting SHOPIFY_STORE and credentials also runs the live tests; adding SHOPIFY_TEST_WRITES=1 runs write tests that create and then delete [MCP test] data, so only use it with a development store.
To contribute, branch from dev, add a changeset with npx changeset (not needed for docs, tests, or CI), and open a pull request into dev. Releases merge dev into main; the workflow then opens a Version Packages pull request, and merging it publishes to npm through trusted publishing with provenance.
MIT. See LICENSE.
Originally created by Colby McHenry as shopify-graphql-admin-mcp, and maintained by acoderacom.
MCP server providing full access to Shopify's Admin GraphQL API with schema introspection
{ "mcpServers": { "acodera-shopify-admin-mcp": { "command": "npx", "args": [ "-y", "@acodera/[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
@acodera/shopify Admin ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-11 MCP server providing full access to Shopify's Admin GraphQL API with schema introspection