ecompick.
For makers中文Submit a tool

Popular seller tasks

Product & keyword researchListings & product copyProduct photosProduct video & ad creativeAdvertising & PPCEmail & marketing

BigCommerce API MCP

List products with documented filtering and pagination

BigCommerceOpen source
#mcp
Visit website

Overview

This community server exposes BigCommerce catalog, customer and order APIs to an assistant. Read access is the default, with write tools registered only when explicitly enabled.

Who it suits

BigCommerce teams with API-account access who want a local assistant connection for catalog and order investigations, with writes disabled until intentionally configured.

Who it may not suit

Users seeking an official BigCommerce-hosted OAuth service or a connector for a store running on an unrelated platform.

Seller use cases

  • List filtered products with pagination to investigate a catalog segment rather than assuming the first page is complete.
  • Read an order and its purchased items to trace a customer or fulfillment question.
  • Prepare a targeted catalog change, enabling write tools only for the operation and account permissions you actually need.

What you can do

  • List products with documented filtering and pagination. ↗
  • Inspect orders and their purchased line items. ↗
  • Enable selected catalog and customer writes through configuration. ↗

What you need

  • Node.js 20+, store hash and an API account with the required scopes.

Install

Local stdio

git clone https://github.com/isaacgounton/bigcommerce-api-mcp.git
cd bigcommerce-api-mcp
npm install
cp .env.example .env
# Configure the required environment variables before starting.
npm start
Installation source ↗

Permissions & data

The Node server calls api.bigcommerce.com. BIGCOMMERCE_ENABLE_WRITES controls write registration; use read-only API scopes for analysis.

Project info

Maintainer
isaacgounton
GitHub stars at check date
5
Last commit
2026-10-02
License
MIT (stated in README)
Last checked
2026-10-30
GitHub ↗

Pricing at a glance

The README identifies an MIT-licensed community server. Running it requires your Node environment and BigCommerce account; no managed hosting or AI-client subscription is included in that license.

Open source

Good to know

Write registration and API-account scopes are separate controls. Enabling BIGCOMMERCE_ENABLE_WRITES does not grant missing API permissions, and broad credentials should not be used merely to simplify a read-only analysis.

Alternatives to BigCommerce API MCP

GeLi2001 uses Shopify Admin GraphQL and exposes Shopify-specific mutations; this server uses BigCommerce’s resource model and opt-in writes.

Saleor MCP offers a read-only surface for Saleor instances; BigCommerce’s community connector can also register supported writes.

Wix MCP adds documentation discovery and Wix site actions through a hosted service instead of a local BigCommerce API wrapper.

Frequently asked questions

Are writes active after a default install?

Read access is the default. The project documents an explicit environment setting to register write tools, in addition to the underlying API account’s permissions.

What identifies the store connection?

The setup requires a store hash and API credentials. Keep both associated with the intended BigCommerce store when configuring multiple environments.

Can a product-list response represent the whole catalog?

The connector documents pagination and filters. Check the query scope and continue through the required pages before presenting a total or making a bulk-change plan.

Is this server run by BigCommerce?

It is a community implementation. The source code calls BigCommerce APIs, but installation, runtime maintenance, and the choice of credentials remain the responsibility of the team running it.

Checked against the official site on 2026-10-30 · Official source ↗

Sources