BigCommerce API MCP Server
This MCP server gives an AI assistant read access to BigCommerce catalog, customers, and orders, with optional write access when enabled.
Read and filter products with sorting, pagination, and optional store hash
Fetch a single product by ID, optionally with variants and images
List and filter customers by ID, email, name, company, phone, group, dates, and more
List and filter orders by customer, status, date range, totals, channel, payment method, and more
Fetch a single order by ID and view its line items/products
Resolve category and brand names to IDs for product filtering
If
BIGCOMMERCE_ENABLE_WRITES=true: create/update products, create/update customers, and update order status/notes/messageServe over stdio or streamable HTTP with optional bearer-token auth and origin protection
Provides comprehensive tools for managing BigCommerce stores, including retrieving and filtering products, managing customers with advanced search options, and accessing order data with customer-product relationship capabilities through the BigCommerce REST API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@BigCommerce API MCP Server show me all orders from the last week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
BigCommerce MCP Server
An MCP server for the BigCommerce REST API. Gives an AI assistant read access to your catalog, customers and orders — and, when you turn it on, the ability to change them.
Tools
Read
Tool | What it does |
| List products with filtering, sorting and pagination |
| One product by ID, optionally with variants and images |
| List customers by ID, email, name, company or date range |
| List orders by customer, status, date range or total |
| One order by ID |
| An order's line items — what was actually bought |
| Resolve category names to the IDs product filters need |
| Resolve brand names to the IDs product filters need |
Write — requires BIGCOMMERCE_ENABLE_WRITES=true
Tool | What it does |
| Create a catalog product |
| Update price, stock, visibility, categories… |
| Create a customer record |
| Update a customer's details |
| Change status, staff notes or customer message |
Write tools aren't registered at all unless enabled, so a default deployment can't modify your store even if someone reaches its endpoint.
npm run list-tools prints the tools and parameters as currently configured.
Related MCP server: commercetools Commerce MCP
Setup
Needs Node 20+.
git clone https://github.com/isaacgounton/bigcommerce-api-mcp.git
cd bigcommerce-api-mcp
npm install
cp .env.example .envThen fill in .env:
BIGCOMMERCE_STORE_HASH=your_store_hash_here
BIGCOMMERCE_API_KEY=your_api_key_hereGet both from BigCommerce admin → Settings → API accounts → Create
API account. Grant Products, Orders and Customers — read-only unless you
plan to enable writes. .env.example documents every supported variable.
Running
npm start # stdio — Claude Desktop, Cline, local clients
npm run start:http # streamable HTTP — remote clients and agent runtimesHTTP mode serves POST /mcp, plus unauthenticated GET /health and /info.
The SSE transport was removed in favour of Streamable HTTP, which replaced it in the MCP spec. Point any client still using
/sseat/mcp.
Claude Desktop
In claude_desktop_config.json (use absolute paths — which node):
{
"mcpServers": {
"bigcommerce": {
"command": "/absolute/path/to/node",
"args": ["/absolute/path/to/bigcommerce-api-mcp/mcpServer.js"],
"env": {
"BIGCOMMERCE_STORE_HASH": "your_store_hash",
"BIGCOMMERCE_API_KEY": "your_api_key"
}
}
}
}Over HTTP
curl -X POST http://127.0.0.1:3000/mcp \
-H "Authorization: Bearer $MCP_AUTH_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Security
Anyone who can call /mcp acts with your store's API credentials.
HOST— binds to127.0.0.1by default. Set0.0.0.0only when you mean to expose it, and put it behind a proxy or firewall when you do.MCP_AUTH_TOKEN— when set, every/mcprequest must carryAuthorization: Bearer <token>. Comparison is timing-safe. Set it whenever the server is reachable beyond localhost.ALLOWED_ORIGINS— requests carrying anOriginheader are refused unless listed here, which blocks DNS-rebinding attacks where a page you visit drives your local server. Non-browser clients send noOriginand are unaffected.BIGCOMMERCE_ENABLE_WRITES— leave off if the assistant only reads.Scopes — give the API account the narrowest scopes that work. A read-only token can't be widened by a bug in this server.
Docker
docker build -t bigcommerce-mcp .
docker run --rm -p 3000:3000 --env-file .env bigcommerce-mcpThe image sets HOST=0.0.0.0 so the published port is reachable. Set
MCP_AUTH_TOKEN before exposing the container.
Development
npm test # protocol, auth, origin, discovery and spec conformance — no credentials needed
npm run test:live # smoke-test read tools against a real store (needs .env)
npm run sync-spec # refresh the query-parameter fixture from BigCommerce's OpenAPI specsnpm test checks every query parameter a tool declares against BigCommerce's
published specs. This matters because BigCommerce ignores unknown query
parameters rather than rejecting them — an invented filter silently returns
unfiltered data, which is worse than an error.
To add a tool, drop a file under tools/bigcommerce/<group>/ exporting an
apiTool — it's discovered automatically. lib/bigcommerce.js handles
credentials, query building, errors and parsing, so a tool is usually just a
path and a schema; copy tools/bigcommerce/catalog/list-brands.js. Set
writes: true on anything that mutates the store.
MIT
Available Tools
3 toolsget_all_customersC
Get all customers from the BigCommerce API with comprehensive filtering options (email, name, company, phone, customer group, dates, pagination). Store hash is automatically retrieved from environment variables.
Inputs: company, customer_group_id, date_created, date_created_max, +15 more.
get_all_ordersB
Get all orders from the BigCommerce API. Can filter by customer_id to get products associated with specific customers through their order history. Store hash is automatically retrieved from environment variables.
Inputs: cart_id, channel_id, customer_id, email, +15 more.
get_all_productsC
Get all products from the BigCommerce API. Store hash is automatically retrieved from environment variables.
Inputs: store_Hash.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose targeting different BigCommerce resources: customers, orders, and products. There is no overlap in functionality, and the descriptions specify unique filtering capabilities where applicable, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern with 'get_all_' prefix followed by the resource name (customers, orders, products). This predictable naming scheme enhances readability and usability across the tool set.
With only 3 tools, this server feels under-scoped for a BigCommerce API integration. A typical e-commerce platform requires more operations like creating, updating, or deleting resources, making this set too limited for comprehensive agent workflows.
The tool set is severely incomplete, covering only read operations (get_all) for three core resources. There are significant gaps in CRUD coverage—no create, update, or delete tools—which will likely cause agent failures when attempting full e-commerce management tasks.
Maintenance
Related MCP Connectors
AI-powered commerce API for luxury skincare shopping. Enables AI agents to search products, browse collections, manage shopping carts, and generate checkout URLs for the Regenique Elegance Shopify store.
Manage your NanoCart store from any AI agent: products, orders, coupons, subscribers, reports.
Connect AI to store orders, products and inventory with scoped access and human approvals.
Enable AI assistants to interact seamlessly with Feeef e-commerce stores, products, and orders usi…
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage BareCommerceCore e-commerce stores through 46 tools covering products, orders, customers, categories, pages, media, webhooks, and analytics. Uses secure OAuth authentication without requiring API keys in chat.6 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with commercetools APIs to manage products, categories, orders, carts, and customer data. It provides a comprehensive set of tools for both read-only and full-access operations through secure authentication methods.4MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI to view and manage e-commerce data such as products, orders, and coupons, and perform actions like updating prices, stock, and generating sales reports.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with WooCommerce stores via the WooCommerce REST API, supporting operations like listing products, orders, and customers.308 npmMIT