Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect BigCommerce to Claude Code

Have Claude edit products and move orders along in BigCommerce. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect BigCommerce to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect BigCommerce, you add a BigCommerce MCP server: a small hosted service that exposes BigCommerce's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own BigCommerce account. No API keys pasted into config files.

claude mcp add --transport http bigcommerce https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in BigCommerce once connected?

Full read-write BigCommerce access lets Claude update product titles, prices, and descriptions, adjust inventory and variants, create and edit orders, update order status and add shipments, and tag or note customers. The merchandising and order work that used to mean clicking through the control panel happens where the store already runs, with your approval.

  • Update a product's name, description, price, or custom fields
  • Adjust inventory levels for products and variants across locations
  • Create or edit an order and apply a manual discount before it is placed
  • Change an order's status and attach shipment tracking once you approve
  • Add tags or notes to a customer record for segmentation
  • Find every low-stock product and propose restock changes

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same BigCommerce access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the BigCommerce API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when BigCommerce changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build BigCommerce connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same BigCommerce connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own BigCommerce account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on BigCommerce's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to BigCommerce?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the BigCommerce account it signs in with. Revoking access is one click in BigCommerce.

More on the BigCommerce connector

BigCommerce connector for claude.aiShopify + Claude CodeWooCommerce + Claude CodeMagento + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us