StackOne BigCommerce MCP

StackOne's hosted MCP server exposes a large set of prebuilt BigCommerce actions (products, orders, customers and more) to AI agents through StackOne's integration platform.

What it is and why it matters

What it does

• Read and write BigCommerce products, orders and customers through prebuilt actions
• Connect through StackOne's hosted platform rather than running a server yourself
• Combine BigCommerce with other StackOne connectors in one agent
• Manage credentials and permissions in the StackOne dashboard

Best for

Agencies and teams that want BigCommerce admin actions in an agent without building an integration, and already use or can adopt StackOne.

How to connect it

1. Create a StackOne account and open the BigCommerce connector page, as described in the documentation. Check the vendor pricing page, because this is a commercial service.
2. Link your BigCommerce store through the StackOne dashboard. StackOne handles authentication, and the documentation describes per-user OAuth. Use a test or staging store first if you have one.
3. Limit the actions the agent can use. The documentation says you can scope access to exactly what you need. Start with read actions only, such as getting orders, products and customers, and leave out create, update and delete actions.
4. Copy the account ID and the authorization token from your StackOne account. The documentation shows a Claude Desktop JSON configuration. It uses a remote connector with a StackOne endpoint that includes your account ID, plus an Authorization header holding your token. Copy the exact block from the vendor page and do not rewrite it.
5. Other supported clients include Claude Code, Cursor, VS Code and Goose. Follow the vendor's setup guide for your client.
6. Restart the client and run a harmless read prompt, such as asking for store information. Then check the StackOne logs to confirm which actions ran.

Exact commands and addresses change. Use the official documentation for the current steps.

Installation guide for StackOne BigCommerce MCP

Client-by-client steps, what to prepare, the first prompts to run and fixes for common errors.

ClaudeChatGPTGeminiMicrosoft CopilotPerplexityCursorClaude Code

→

Questions you can ask it

• Get the last 20 orders with their status and list any that are still awaiting fulfillment.
• List all products in the catalog that have no brand assigned, with their IDs.
• Show inventory levels at each location for these 10 SKUs and flag anything below 5 units.
• List all coupons in the store and tell me how many there are. Do not change anything.

What it cannot do

• It does not run on your own infrastructure. The server is hosted by StackOne, and requests pass through its platform.
• It is limited to the 120 actions listed. Anything else needs a custom action built with StackOne's Connector Builder.
• It does not make write actions safe on its own. Deleting, repricing or adjusting inventory still needs your own review, and the documentation does not describe an undo.

Staying safe

• Start with read-only actions. The tool list includes permanent deletes for products, customers, brands, categories and coupons. It also includes inventory adjustments and order updates. Enable these only for supervised tasks, and ideally on a test store first.
• Treat the StackOne token as a secret. Anyone holding the account ID and token can reach the connected store. Keep the token out of shared files and rotate it if it leaks. Use the StackOne dashboard to manage permissions and credentials.
• Store data, including customer personal information, passes through a third-party platform. Review StackOne's security, privacy and data handling terms, and check whether PII redaction is available for your plan before connecting customer data. Prompt injection scanning is described, but customer-written content such as reviews or notes should still be treated as untrusted.

Watch out for: Third-party platform with write access: review exactly which actions are enabled and where store data flows. Commercial service with its own pricing.

Frequently asked questions