Toolsets & Tools
The B2C DX MCP Server provides six toolsets with specialized tools for different B2C Commerce development workflows.
Overview
Toolsets are collections of related tools that work together to support specific development workflows. The server automatically enables toolsets based on your project type, or you can manually select toolsets using the --toolsets flag.
Available toolsets:
- CARTRIDGES - Cartridge deployment and code version management
- DIAGNOSTICS - Script debugger, log inspection, and bundled documentation
- MRT - Managed Runtime bundle operations
- PWAV3 - PWA Kit v3 development tools
- SCAPI - Salesforce Commerce API discovery
- STOREFRONTNEXT - Storefront Next development tools
Note: With auto-discovery, the SCAPI and DIAGNOSTICS toolsets are always included. When using --toolsets or --tools, only the specified toolsets/tools are enabled.
CARTRIDGES
Cartridge development, deployment, and code version management.
Status: ✅ Generally Available
Auto-enabled for: Cartridge projects (detected by .project file)
Tools
| Tool | Description | Documentation |
|---|---|---|
cartridge_deploy | Deploy cartridges to a B2C Commerce instance | View details |
DIAGNOSTICS
Script debugger, runtime log inspection, and bundled Script API / XSD documentation lookup.
Status: ✅ Generally Available
Always enabled - Base toolset available for all projects. The log and debugger tools also appear in CARTRIDGES and SCAPI; the documentation tools appear in every toolset.
Script Debugger
| Tool | Description | Documentation |
|---|---|---|
debug_start_session / debug_end_session / debug_list_sessions | Manage SDAPI debugger sessions | View details |
debug_set_breakpoints | Set breakpoints in cartridge scripts | View details |
debug_wait_for_stop / debug_continue / debug_step_into / debug_step_over / debug_step_out | Control execution flow | View details |
debug_get_stack / debug_get_variables / debug_evaluate | Inspect stack frames, variables, and evaluate expressions | View details |
debug_capture_at_breakpoint | One-shot capture of stack + variables at a breakpoint | View details |
Logs
| Tool | Description | Documentation |
|---|---|---|
logs_list_files | List log files on the instance via WebDAV | View details |
logs_get_recent | Fetch recent log entries in a single request | View details |
logs_watch_start / logs_watch_poll / logs_watch_stop / logs_watch_list | Buffered log watch lifecycle so entries aren't missed between calls | View details |
Documentation
| Tool | Description | Documentation |
|---|---|---|
docs_search / docs_read / docs_list | Search and read bundled Script API documentation | View details |
docs_schema_search / docs_schema_read / docs_schema_list | Search and read bundled XSD schemas | View details |
MRT
Managed Runtime operations for PWA Kit and Storefront Next deployments.
Status: ✅ Generally Available
Auto-enabled for: PWA Kit v3 and Storefront Next projects
Tools
| Tool | Description | Documentation |
|---|---|---|
mrt_bundle_push | Build, push bundle (optionally deploy) | View details |
PWAV3
PWA Kit v3 development tools for building headless storefronts.
Status: ✅ Generally Available
Auto-enabled for: PWA Kit v3 projects (detected by @salesforce/pwa-kit-* dependencies, @salesforce/retail-react-app, or ccExtensibility field in package.json)
Tools
| Tool | Description | Documentation |
|---|---|---|
pwakit_get_guidelines | Get PWA Kit v3 development guidelines and best practices | View details |
scapi_schemas_list | List or fetch SCAPI schemas (standard and custom). Use apiFamily: "custom" for custom APIs. | View details |
scapi_custom_api_generate_scaffold | Generate a new custom SCAPI endpoint (schema, api.json, script.js) in an existing cartridge. | View details |
scapi_custom_apis_get_status | Get registration status of custom API endpoints (active/not_registered). Remote only, requires OAuth. | View details |
mrt_bundle_push | Build, push bundle (optionally deploy) | View details |
SCAPI
Salesforce Commerce API discovery and exploration.
Status: ✅ Generally Available
Always enabled - Base toolset available for all projects.
Tools
| Tool | Description | Documentation |
|---|---|---|
scapi_schemas_list | List or fetch SCAPI schemas (standard and custom). Use apiFamily: "custom" for custom APIs. | View details |
scapi_custom_api_generate_scaffold | Generate a new custom SCAPI endpoint (schema, api.json, script.js) in an existing cartridge. | View details |
scapi_custom_apis_get_status | Get registration status of custom API endpoints (active/not_registered). Remote only, requires OAuth. | View details |
STOREFRONTNEXT
Storefront Next development tools for building modern storefronts.
Status: 🚧 Preview — requires --allow-non-ga-tools flag.
Auto-enabled for: Storefront Next projects (detected by @salesforce/storefront-next* dependencies, package name starting with storefront-next, or workspace packages with these indicators)
Tools
| Tool | Description | Documentation |
|---|---|---|
sfnext_get_guidelines | Get Storefront Next development guidelines and best practices | View details |
sfnext_start_figma_workflow | Workflow orchestrator for Figma-to-component conversion. Parses Figma URL, returns step-by-step instructions for subsequent tool calls | View details |
sfnext_analyze_component | Analyze design and discovered components to recommend REUSE, EXTEND, or CREATE strategy | View details |
sfnext_match_tokens_to_theme | Map design tokens to existing theme tokens in app.css with confidence scores and suggestions | View details |
sfnext_add_page_designer_decorator | Add Page Designer decorators to Storefront Next components | View details |
sfnext_configure_theme | Get theming guidelines, questions, and WCAG color validation for Storefront Next | View details |
scapi_schemas_list | List or fetch SCAPI schemas (standard and custom). Use apiFamily: "custom" for custom APIs. | View details |
scapi_custom_api_generate_scaffold | Generate a new custom SCAPI endpoint (schema, api.json, script.js) in an existing cartridge. | View details |
scapi_custom_apis_get_status | Get registration status of custom API endpoints (active/not_registered). Remote only, requires OAuth. | View details |
mrt_bundle_push | Build, push bundle (optionally deploy) | View details |
Figma-to-component tools (sfnext_start_figma_workflow, sfnext_analyze_component, sfnext_match_tokens_to_theme) require additional setup: an external Figma MCP server and a valid Figma URL with node-id. See Figma-to-Component Tools Setup for prerequisites and configuration.
Tool Deduplication
Some tools appear in multiple toolsets (for example, mrt_bundle_push, scapi_schemas_list, scapi_custom_api_generate_scaffold, scapi_custom_apis_get_status). When using multiple toolsets, tools are automatically deduplicated, so you'll only see each tool once.
Next Steps
- Configuration - Configure credentials, environment variables, MCP flags, toolset selection, and logging
- Installation - Set up the MCP server
- MCP Server Overview - Learn more about the MCP server