Skip to content
View as Markdown
View as Markdown

MCP Server

The B2C DX MCP Server enables AI assistants (like Claude Code, Cursor, GitHub Copilot, and others) to help with B2C Commerce development tasks. It provides toolsets for SCAPI, CARTRIDGES, MRT, PWAV3, and STOREFRONTNEXT development.

Quick Start

  1. Install — set up the MCP server for your client. See the Installation Guide for Claude Code, Cursor, GitHub Copilot, and other clients.

  2. Configure credentials — create a dw.json or .env file in your project root. No changes to mcp.json needed.

  3. Start using tools — the server auto-detects your project type and enables relevant toolsets.

For authentication setup instructions, see the Authentication Setup guide which covers API client creation, WebDAV access, SCAPI authentication, and MRT API keys.

Project Type Detection

The SCAPI and DIAGNOSTICS toolsets are always enabled. On top of those, the server analyzes your project directory and enables additional toolsets based on what it finds:

Project TypeDetectionToolsets Added
Cartridges.project file in a cartridge directoryCARTRIDGES
SFRAAn app_storefront_base cartridge (or paths.base in package.json)CARTRIDGES
PWA Kit v3@salesforce/pwa-kit-* or @salesforce/retail-react-app dependency, or ccExtensibility in package.jsonPWAV3, MRT
Storefront Next@salesforce/storefront-next-dev dependency or a package name starting with storefront-next, in the root or a workspace packageSTOREFRONTNEXT, MRT, CARTRIDGES
No project detectedNo B2C markers found(base only)

Every configuration also includes the always-on base toolsets (SCAPI + DIAGNOSTICS). Hybrid projects (e.g. cartridges + PWA Kit) get the union of the matching rows. You can also manually select toolsets.

Plugins

The MCP server uses the B2C CLI under the hood, so CLI plugins automatically extend MCP functionality. See the CLI Plugin documentation for details.

Next Steps

Released under the Apache-2.0 License.