shopify-store-sync-mcp
Related Servers
Alternatives to shopify-store-sync-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceConnects Claude, ChatGPT, Cursor, or any MCP client to a Shopify store, enabling read-only access to themes, Liquid files, catalogue data, and store configuration through 122 tools.2Apache 2.0
- AlicenseCqualityDmaintenanceEnables AI assistants like Cursor or Claude Desktop to fully manage a Shopify store using the Model Context Protocol, with tools for products, orders, customers, inventory, discounts, and analytics.32MIT
- FlicenseNot gradedqualityDmaintenanceAI-powered Shopify Admin via Claude + MCP, enabling full store management through conversation including products, collections, analytics, and bulk operations.-
- AlicenseNot gradedqualityDmaintenanceMCP server that connects Claude to Shopify stores, enabling natural language queries and actions on products, orders, customers, inventory, and sales analytics. Includes a demo mode with bundled fixtures for trying tools without credentials.MIT
- AlicenseAqualityBmaintenanceMCP server for building Shopify stores with AI, letting Claude Code and other clients edit themes, pages, and navigation via the Admin GraphQL API. Credentials stay on your machine as the server runs locally.913 npm3ISC
- AlicenseNot gradedqualityCmaintenanceConnects MCP-compatible clients to a Shopify store's Admin GraphQL API, exposing products, orders, customers, inventory, and sales data as callable tools. It enables natural-language store queries, low-stock and sales summaries, customer support answers, and creation of draft products for review.MIT
TDQS
Scored across 13 tools
Each tool has a distinct role in a clear pipeline: discovery (list_stores, list_resource_types), inspection (snapshot_store, export_snapshot), comparison (diff_stores, compare_item, diff_themes), planning (plan_sync, get_plan), execution (apply_plan, apply_status, cancel_apply) and audit (get_audit_log). The potentially confusable cluster (snapshot vs export vs diff vs compare) is explicitly delimited in every description with 'use X for..., use Y for...' guidance.
Most names follow a predictable verb_noun pattern (list_stores, snapshot_store, export_snapshot, diff_stores, compare_item, apply_plan, get_audit_log). A couple of deviations break the pattern — plan_sync is noun_verb rather than create_plan/plan_changes, and apply_status reads like a status noun rather than get_apply_status — but the overall scheme stays readable.
13 tools is well within the ideal range and each maps to a needed stage of the sync lifecycle; nothing looks redundant or padded. Read-only inspection, planning, applying, monitoring and auditing each justify their slots.
Coverage is strong: discovery, snapshot/export, diff, dry-run planning, gated apply, progress tracking, cancellation and audit logging, plus restore-from-folder via 'dir:<path>' sources. The main gap is diff_themes, which compares theme files but has no corresponding apply tool, so theme changes are a dead end; deletion is also absent, though that is an explicitly stated design choice.