home / mcp / bigcommerce mcp server

BigCommerce MCP Server

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "isaacgounton-bigcommerce-api-mcp": {
      "command": "node",
      "args": [
        "mcpServer.js"
      ],
      "env": {
        "BIGCOMMERCE_API_KEY": "your_api_key_here",
        "BIGCOMMERCE_STORE_HASH": "your_store_hash_here"
      }
    }
  }
}

You have a dedicated MCP server that lets you query and manage your BigCommerce data through a streamlined, client-friendly interface. This server exposes three core capabilities—products, customers, and orders—while providing robust filtering, error handling, and Docker-ready deployment so you can integrate with MCP clients like Claude Desktop and Cline with ease.

How to use

You connect to the BigCommerce MCP Server from an MCP client and start by discovering the available tools. Once discovered, you can call the tools to retrieve products, search customers with advanced filters, and obtain orders with customer-product relationships. Use the client’s tooling to send requests and view structured responses in a way that supports interactive AI-assisted workflows.

How to install

Prerequisites: you need Node.js (v18+ required, v20+ recommended), npm (comes with Node), and a BigCommerce store with API credentials.

Step 1. Clone the project and install dependencies.

git clone https://github.com/isaacgounton/bigcommerce-api-mcp.git
cd bigcommerce-api-mcp
npm install

Step 2. Configure your BigCommerce credentials. Create a .env file in the project root and add your store hash and API key.

BIGCOMMERCE_STORE_HASH=your_store_hash_here
BIGCOMMERCE_API_KEY=your_api_key_here

Step 3. Start the server locally in stdio mode to begin serving MCP requests.

node mcpServer.js

Configuration and deployment notes

Environment variables are the primary means to configure this server. You can provide credentials via a .env file or set them in your deployment environment.

If you prefer Docker for production, you can build and run a container with the provided Docker commands and compose support.

Testing and validation

Verify that the server starts correctly and tool discovery works by running the server in stdio mode and testing a couple of actions locally.

# Start server (stdio mode)
node mcpServer.js

# Example: confirm there is a running MCP server by checking your terminal output

Notes on usage with MCP clients

This server is designed to integrate with Claude Desktop, Cline, and other MCP clients. Ensure your client is configured with the correct command and environment variables so it can spawn or connect to the local stdio server.

Security and credentials

Keep your BigCommerce credentials secure. Do not commit your .env file to version control. Use environment-based secrets in production and rotate credentials as needed.

Troubleshooting

If the server fails to start, verify that Node.js is installed, the environment variables are present, and there are no port or file permission conflicts in the deployment environment.

Available tools

get_all_products

Retrieve products from your BigCommerce store with advanced filtering options and required parameter store_Hash.

get_all_customers

Search and filter customers with advanced options including email, name, company, and more, with required parameter store_Hash.

get_all_orders

Access orders with optional filters and the ability to view related customer-product data, using required parameter store_Hash.