B2C CLI, MCP and Tooling SDK

The B2C developer tools for B2C Commerce streamline developer workflows through a CLI, Agent Skills, and IDE extensions. With these tools, you and your coding agent can build, deploy, and operate on B2C Commerce instances, Managed Runtime (MRT), and On-Demand Sandboxes (ODS).

Code versions, cartridges, jobs, sandboxes, Managed Runtime, SLAS, eCDN, logs, and more are all first-class operations you can run from a terminal, a CI pipeline, or a conversation with your coding agent—without clicking through a UI. The B2C Commerce Developer Tooling project is an open-source monorepo that packages that access into components you can mix and match.

Core Components

B2C CLI — an oclif-based command line interface that is the core tool for day-to-day B2C Commerce development: code deployment, job execution, sandbox management, SLAS, eCDN, Managed Runtime (MRT), and more.
Agent Skills — preconfigured skills that give your coding agent live, context-aware expertise in working with B2C Commerce, with the CLI as its primary interface to the platform.
B2C Tooling SDK — a Node.js library for authentication, code deployment, and instance management that you can embed directly in scripts, CI jobs, and custom tools.
B2C DX MCP Server — a Model Context Protocol server that complements the skills with project-aware tools for MCP-first clients.
IDE Extensions — editor integrations (VS Code and others) built on the same CLI and SDK, so the same workflows are available wherever you write code.

Humans, agents, and pipelines all run the same B2C Commerce workflows. The platform doesn’t change—only the surface does.

Use Cases

Here are some common tasks you can run end-to-end using the B2C Commerce CLI, which help you to quickly provision credentials, configure your environment, and manage platform resources:

Create a SLAS client (private) for Shopper APIs:

1b2c slas client create --name "MyApp" --channels RefArch --scopes sfcc.shopper-products,sfcc.shopper-product-search --redirect-uri http://localhost:3000/callback

Update stored credentials and instance settings (guided setup): b2c setup
Set environment variables for scripted workflows (realm, instance, shortcode): export SFCC_REALM_ID=zzte SFCC_INSTANCE_ID=001 SFCC_SCAPI_SHORTCODE=kv7kzm78
Create a Managed Runtime (MRT) project (verify exact flags with help): b2c mrt project create --name "my-storefront" Or view options: b2c mrt project create --help

Installation & Setup

The B2C Commerce Developer Tooling can be used as a global command-line tool or integrated into your project as an SDK.

Prerequisites

Before installation, ensure your environment meets the minimum requirements for Node.js and package management. For detailed installation instructions, command references, and getting started guides, visit the official B2C Developer Tooling Documentation Site.

1. Install the B2C CLI

Install the CLI globally to access B2C Commerce operations from any terminal:

1npm install -g @salesforce/b2c-cli

If you use pnpm, you can use pnpm add -g @salesforce/b2c-cli.

Note

2. Install the Tooling SDK

If you’re building custom scripts or integrations, add the SDK to your project’s dependencies:

1pnpm add @salesforce/b2c-tooling-sdk

3. Initialize Setup

Run the interactive setup to configure the CLI with your instance and Account Manager credentials:

1b2c setup

4. Verify Installation

Once installed, verify the CLI is ready for use by checking the version:

1b2c --version

Contributing & Extension

If you wish to contribute to the tools, report issues, or use the SDK to build custom integrations, refer to the B2C Developer Tooling GitHub Repository. The repository includes detailed information on:

Monorepo Structure: How the CLI and SDK packages interact.
Development Workflow: Local setup using pnpm, running in development mode, and testing.
API Reference: Auto-generated TypeDoc documentation for the SDK modules (Auth, Instance, Platform, and Operations).
Contribution Guidelines: How to submit pull requests and use Changesets for versioning.

Support & Feedback

License: Apache-2.0
Security: Report concerns to security@salesforce.com.
Community: Provide feedback via GitHub Issues or the Unofficial Slack.