Shopify-operations-mcp Server

Safe-write Shopify operations: plan-before-execute writes with out-of-band approval and audit.

Local serverstdio

What is the Shopify-operations-mcp Server?

Shopify-operations-mcp is an MCP integration. Safe-write Shopify operations: plan-before-execute writes with out-of-band approval and audit.

Packages and local setup

The published npm package is shopify-operations-mcp, version 0.1.2. Its declared MCP transport is stdio.

The package declares SHOPIFY_STORE_DOMAIN (required): The myshopify.com store domain, e.g. my-store.myshopify.com. Overrides shopify.storeDomain from the config file.; SHOPIFY_ADMIN_TOKEN (required): Shopify Admin API access token. Required and only ever read from the environment — never from the config file.; SHOPIFY_CONFIG: Path to a config.json with shopify/plans/approvalServer/protectedTags settings. Defaults to ./config.json in the working directory.; SHOPIFY_PLAN_TTL_MS: How long a plan token stays valid before it must be executed or expires, in milliseconds. Default 60000.; SHOPIFY_APPROVAL_SERVER_PORT: Port the localhost human-approval HTTP server binds to (127.0.0.1 only). Default 4319.; SHOPIFY_PROTECTED_TAGS: Comma-separated tags that plans may never modify; any plan touching an item carrying one is refused. Default do-not-touch.; SHOPIFY_CALLER_ID: Identity recorded as the caller on every audit log row. Default unknown.; SHOPIFY_AUDIT_PATH: File path for the tamper-evident JSONL audit log. Default shopify-operations-audit.jsonl in the working directory..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related payments & commerce MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
SHOPIFY_STORE_DOMAINThe myshopify.com store domain, e.g. my-store.myshopify.com. Overrides shopify.storeDomain from the config file.Yes
SHOPIFY_ADMIN_TOKENShopify Admin API access token. Required and only ever read from the environment — never from the config file.Yes
SHOPIFY_CONFIGPath to a config.json with shopify/plans/approvalServer/protectedTags settings. Defaults to ./config.json in the working directory.Optional
SHOPIFY_PLAN_TTL_MSHow long a plan token stays valid before it must be executed or expires, in milliseconds. Default 60000.Optional
SHOPIFY_APPROVAL_SERVER_PORTPort the localhost human-approval HTTP server binds to (127.0.0.1 only). Default 4319.Optional
SHOPIFY_PROTECTED_TAGSComma-separated tags that plans may never modify; any plan touching an item carrying one is refused. Default do-not-touch.Optional
SHOPIFY_CALLER_IDIdentity recorded as the caller on every audit log row. Default unknown.Optional
SHOPIFY_AUDIT_PATHFile path for the tamper-evident JSONL audit log. Default shopify-operations-audit.jsonl in the working directory.Optional