Name: Commerce Cloud MCP Server
Author: brinzl

LABSCO SUMMARY

The OCAPI import is a real setup step, and nothing works before it.

The endpoints this server needs are off by default in Business Manager, so a correct build with correct credentials still returns nothing until the configuration files are pasted in. Once past that, the interesting capability is the write side: turning a design image into a content asset body, or product images into a description, and putting the result back — which is what separates it from a read-only catalog browser.

What it is

A Node server connecting an AI client to a Salesforce Commerce Cloud instance over OCAPI. It reads catalog and order data, and — the part that distinguishes it — writes generated content back: a product description built from product images, or a content asset body built from a design image.

What you get

Product details fetched from Commerce Cloud
Product updates: generate descriptions from images and write the product details back automatically
Order analysis, for questions about purchase behaviour rather than one order at a time
Custom objects — read, write and create
Content assets fetched, and content bodies generated from design images and written back
Site preferences, promotions and campaigns, and job configurations are listed as future work, not shipped

Requirements

Node.js version 22 or higher, Git, and a Salesforce Commerce Cloud instance with OCAPI access. Clone, npm install, copy .env.example to .env and fill in your Commerce Cloud credentials, then npm run build. Before it will work you must import the OCAPI configurations from the repository's data/ocapi directory into Business Manager under Administration → Site Development → Open Commerce API Settings, choosing the Shop or Data API type for each file — those settings enable the endpoints the server calls. Point your client at dist/index.js with an absolute path.

Setup effort

Build from source — git clone https://github.com/brinzl/commercecloud-mcp-server.git

See installation options

USE CASES

01

Writing product copy from the images

Generate the description from the product images and update the record in place.

02

Asking what the orders say

Analyse order patterns for purchase behaviour instead of exporting a report.

03

Turning a design into a content asset

Generate the content body from the design image and write it to the asset.

04

Working with custom objects

Read, create and write custom objects from the conversation.

BEFORE YOU INSTALL

What to know first

Requires

Node.js 22 or later

Where it runs

The documented client runs the server on your machine.

INSTALLATION

Connect your client

You clone and build this one yourself.

Server setup

TERMINAL

git clone https://github.com/brinzl/commercecloud-mcp-server.git
cd commercecloud-mcp-server
npm install
cp .env.example .env

Edit the .env file with your Salesforce Commerce Cloud credentials.

TERMINAL

npm run build

Import the OCAPI configuration files in the data/ocapi directory into Business Manager: Administration > Site Development > Open Commerce API Settings; for each JSON file, select the API type (Shop/Data), paste the file's contents into the configuration field and click "Save".

MCP Clients

Claude Desktop

CLAUDE DESKTOP · JSON

{
  "mcpServers": {
    "commercecloud": {
      "command": "node",
      "args": [
        "<YOUR_PATH_TO_COMMERCECLOUD_MCP_SERVER>/dist/index.js"
      ]
    }
  }
}

Commerce Cloud MCP Server