Plan order and customer reporting
Prepare mappings for supported order and customer objects, with store identifiers and an explicit destination.
Your connection path
Your assistant works through your Stacksync workspace and its available connections.
“Plan an order-reporting replica”
Stacksync MCP · Commerce
Use Stacksync MCP to prepare Shopify order and product syncs, inspect connector actions and investigate failed updates. Start with the store connection and supported objects, then choose the data and write direction needed for the commerce workflow.
01 / The connection
Use Stacksync MCP to prepare Shopify order and product syncs, inspect connector actions and investigate failed updates. Start with the store connection and supported objects, then choose the data and write direction needed for the commerce workflow. Choose an AI client below to get started with the Stacksync MCP server.
The server belongs to Stacksync. The available Shopify operations depend on your connection, permissions, and connector modules.
Explore the Shopify connector →02 / Capabilities
Choose the connection path that fits the job. Your assistant inspects the available tools before configuring or running an action.
Prepare mappings for supported order and customer objects, with store identifiers and an explicit destination.
Discover available Shopify modules and their input forms before proposing a product or variant operation.
Review failed records, connection access and object mappings before retrying an order or product update.
03 / Setup
Connect the MCP server first. Then connect Shopify using the requirements below.
Connect Claude on the web or desktop to Stacksync through a custom connector and browser sign-in.
Open Customize → Connectors, select + Add, then Add custom connector. Name it Stacksync and use the server URL below.
https://mcp.stacksync.com/mcp Select Connect, complete the Stacksync sign-in in your browser and choose the default workspace. Clear Make changes on the consent screen if you only want read access.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Shopify connection and capabilities.
Add the remote Stacksync server to Claude Code and authenticate from its MCP menu.
Run the command below. Add --scope user if you want the connection available across your projects.
claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp Open Claude Code, run /mcp, select stacksync and complete the Stacksync sign-in. Choose the workspace you want requests to use by default.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Shopify connection and capabilities.
Add Stacksync as a custom MCP app in ChatGPT and sign in with OAuth.
Open Settings → Apps → Advanced settings and turn on Developer mode. If the option is unavailable, check the account or workspace policy with your administrator.
Select Create app, name it Stacksync, enter the server URL below and choose OAuth. Complete the Stacksync sign-in and select your default workspace.
https://mcp.stacksync.com/mcp Select Stacksync from the chat tools menu so the conversation can use its tools. Signing in to ChatGPT itself does not sign you in to Stacksync.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Shopify connection and capabilities.
Configure Stacksync in Codex with a remote MCP URL and an explicit OAuth login.
Add the Stacksync endpoint to your Codex MCP configuration.
codex mcp add stacksync --url https://mcp.stacksync.com/mcp Run the login command and complete the Stacksync browser sign-in. Select a default workspace; restart your Codex session if the tools are not yet listed.
codex mcp login stacksync Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Shopify connection and capabilities.
Use Stacksync from Cursor by adding a remote server to its MCP configuration.
Merge this stacksync entry into the mcpServers object in ~/.cursor/mcp.json. Preserve any servers you already use.
{
"mcpServers": {
"stacksync": {
"url": "https://mcp.stacksync.com/mcp"
}
}
} Open Cursor’s MCP settings, select Connect beside stacksync and finish the Stacksync sign-in in your browser.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Shopify connection and capabilities.
Connect Stacksync to GitHub Copilot Chat in VS Code using an HTTP MCP server.
Run the command below. Alternatively, add a stacksync entry with type http and this URL under servers in your project’s .vscode/mcp.json.
code --add-mcp '{"name":"stacksync","type":"http","url":"https://mcp.stacksync.com/mcp"}' Open Copilot Chat in Agent mode. Start stacksync from the tools picker and complete the Stacksync browser sign-in.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Shopify connection and capabilities.
Add Stacksync to Cascade with Windsurf’s serverUrl configuration and OAuth sign-in.
In the Cascade panel, open the … menu and select Open MCP config file. Merge this entry into mcp_config.json without removing other servers.
{
"mcpServers": {
"stacksync": {
"serverUrl": "https://mcp.stacksync.com/mcp"
}
}
} Save the configuration. Cascade opens the Stacksync sign-in flow the first time it uses the server. Choose your default workspace.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Shopify connection and capabilities.
Connect the Gemini command-line client to Stacksync through remote HTTP MCP and browser authorization.
Run the following command in your terminal to add the HTTP server.
gemini mcp add --transport http stacksync https://mcp.stacksync.com/mcp Start Gemini CLI, run the command below and finish the Stacksync sign-in in your browser.
/mcp auth stacksync Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Shopify connection and capabilities.
04 / Put it to work
Example prompts for Shopify. The outcomes describe what to expect, not results from your account. Review the proposed configuration before running it.
Inspect my Shopify and database connections and any existing order sync. Discover the available order and customer fields, then propose a one-way reporting replica with store IDs, stable record keys and the minimum customer data needed. Show the initial-copy scope and permissions before creating or starting anything.
A store-specific order reporting plan with explicit customer-data boundaries.
Inspect the available Shopify actions and the connection to the store I choose. Determine whether the product lookup and update needed for my request are supported. Show the required identifiers and a proposal for the selected fields only, keeping product and variant identifiers distinct. Do not update the store until I confirm the exact changes.
A product action proposal based on available modules and correct record identifiers.
Inspect my Shopify sync issues and current table mappings. Group failures by access, field validation or unsupported operations, and show affected record IDs. Propose the smallest correction and explain the consequences of retrying or ignoring each group. Do not replay, resolve or change records automatically.
A targeted commerce sync recovery plan with the affected records identified.
05 / Before you run
OAuth access follows your Stacksync role. Choose read-only access during sign-in when appropriate. Workspace owners can enable “Ask before every change”; it is a configurable setting. Direct connector actions also follow gateway policies.
Read about permissions and approvals ↗06 / Common questions
The published list includes products, product media, variants, orders, customers and abandoned checkouts. Confirm that the connected store exposes the fields and permissions required for your mapping.
No. Syncing an object and invoking a direct action are different capabilities. Inspect live modules before promising refunds, fulfillment changes or another specific operation.
Yes. Start by selecting only the fields needed for the report and verify the Shopify connection’s access. The sample prompts ask for those boundaries before proposing a sync.
Reviewed · Product documentation and connector references
Keep building