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
Install — set up the MCP server for your client. See the Installation Guide for Claude Code, Cursor, GitHub Copilot, and other clients.
Configure credentials — create a
dw.jsonor.envfile in your project root. No changes tomcp.jsonneeded.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 Type | Detection | Toolsets Added |
|---|---|---|
| Cartridges | .project file in a cartridge directory | CARTRIDGES |
| SFRA | An 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.json | PWAV3, MRT |
| Storefront Next | @salesforce/storefront-next-dev dependency or a package name starting with storefront-next, in the root or a workspace package | STOREFRONTNEXT, MRT, CARTRIDGES |
| No project detected | No 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.
Storefront Next sfnext_* tools are deprecated
The legacy Storefront Next MCP tools (sfnext_*) are not compatible with the Storefront Next 1.0 GA release and have been superseded by the storefront-next and storefront-next-figma agent-skills plugins. They no longer auto-enable for Storefront Next projects and have moved to the opt-in STOREFRONTNEXT_DEPRECATED toolset. Install the skills plugins instead — see the Agent Skills guide.
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
- Installation Guide - Set up Claude Code, Cursor, GitHub Copilot, or other MCP clients
- Configuration - Configure credentials, environment variables, MCP flags, toolset selection, and logging
- Toolsets & Tools - Explore available toolsets and tools
- CLI Reference - Learn about the B2C CLI commands
- API Reference - Explore the SDK API