Install AI Tools

B2C Commerce tools, documentation, and skills for your assistant.

Claude

Using Claude Desktop? See Claude Desktop (Cowork) setup.

Install the plugin Recommended

bash
claude plugin marketplace add SalesforceCommerceCloud/b2c-developer-tooling
claude plugin install b2c-dx-mcp@b2c-developer-tooling

Start a new Claude Code session. To install for the current project only, run it from your project directory with --scope project.

Manual MCP setup
bash
claude mcp add --transport stdio --scope user b2c-dx-mcp -- npx -y @salesforce/b2c-dx-mcp@latest

Start a new session. To configure the current project only, run it from your project directory with --scope project. See Claude Code MCP setup.

Codex/ChatGPT

Using the ChatGPT desktop app (ChatGPT Work)? See ChatGPT Work setup.

Install the plugin Recommended

bash
codex plugin marketplace add SalesforceCommerceCloud/b2c-developer-tooling
codex plugin add b2c-dx-mcp@b2c-developer-tooling

Start a new Codex session in your project. Codex plugins also work in ChatGPT Work.

Manual MCP setup
bash
codex mcp add b2c-dx-mcp -- npx -y @salesforce/b2c-dx-mcp@latest

Or add this to ~/.codex/config.toml (or $CODEX_HOME/config.toml if customized):

toml
[mcp_servers.b2c-dx-mcp]
command = "npx"
args = ["-y", "@salesforce/b2c-dx-mcp@latest"]

Start a new session. See Codex MCP configuration.

VS Code

Install in VS Code

Install the plugin Recommended

  1. Open the Command Palette (Cmd/Ctrl+Shift+P) and run Chat: Install Plugin from Source.
  2. Enter SalesforceCommerceCloud/b2c-developer-tooling.
  3. Select b2c-dx-mcp and follow the installation prompts.
  4. Start a new chat in GitHub Copilot.
Manual MCP setup

Add this to .vscode/mcp.json in your workspace:

json
{
  "servers": {
    "b2c-dx-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@salesforce/b2c-dx-mcp@latest"]
    }
  }
}

See VS Code MCP setup.

Copilot CLI setup

Cursor

Install in Cursor

Reload the MCP server in Cursor after installation.

Manual MCP setup

Add this to .cursor/mcp.json in your project:

json
{
  "mcpServers": {
    "b2c-dx-mcp": {
      "command": "npx",
      "args": ["-y", "@salesforce/b2c-dx-mcp@latest"]
    }
  }
}

For all projects, use ~/.cursor/mcp.json instead.

See Cursor's MCP documentation.

OpenCode

Add this to opencode.json in your project:

json
{
  "mcp": {
    "b2c-dx-mcp": {
      "type": "local",
      "command": ["npx", "-y", "@salesforce/b2c-dx-mcp@latest"],
      "enabled": true
    }
  }
}

Restart OpenCode. For all projects, use ~/.config/opencode/opencode.json. See OpenCode MCP setup.

Gemini

Run:

bash
gemini mcp add --scope user b2c-dx-mcp -- npx -y @salesforce/b2c-dx-mcp@latest

Start a new Gemini CLI session. To configure the current project only, run it from your project directory with --scope project. See Gemini CLI MCP setup.

No separate skills plugins needed.

Other clients and manual setup →
Agentic B2C Developer Toolkit

Appearance

View as Markdown
View as Markdown

@salesforce/b2c-tooling-sdk / operations/mrt / MrtRedirectView

Interface: MrtRedirectView ​

Defined in: packages/b2c-tooling-sdk/src/operations/mrt/redirect.ts:639

A single redirect row, normalized across the legacy and SCAPI backends so the CLI renders one shape regardless of backend.

The two backends identify a redirect differently: the legacy MRT Cloud API keys a redirect by its from_path, while the SCAPI Environments API assigns a UUID redirectId and treats the source path as an ordinary (mutable) field. id therefore carries the backend-appropriate identifier to pass back to get/update/delete — the from_path on legacy, the UUID on SCAPI — while source always holds the human-readable source path. On legacy the two are equal; on SCAPI they differ.

Properties ​

backend ​

backend: MrtBackend

Defined in: packages/b2c-tooling-sdk/src/operations/mrt/redirect.ts:659

Backend that produced this row.

createdAt? ​

optional createdAt: string

Defined in: packages/b2c-tooling-sdk/src/operations/mrt/redirect.ts:655

Creation timestamp (ISO 8601), when present.

createdBy? ​

optional createdBy: string

Defined in: packages/b2c-tooling-sdk/src/operations/mrt/redirect.ts:657

Email of the user who created the redirect, when present.

destination ​

destination: string

Defined in: packages/b2c-tooling-sdk/src/operations/mrt/redirect.ts:645

The destination path or URL (legacy to_url / SCAPI destination).

forwardQuerystring? ​

optional forwardQuerystring: boolean

Defined in: packages/b2c-tooling-sdk/src/operations/mrt/redirect.ts:649

Whether the incoming query string is forwarded to the destination.

forwardWildcard? ​

optional forwardWildcard: boolean

Defined in: packages/b2c-tooling-sdk/src/operations/mrt/redirect.ts:651

Whether a trailing wildcard match on the source is forwarded to the destination.

httpStatusCode? ​

optional httpStatusCode: number

Defined in: packages/b2c-tooling-sdk/src/operations/mrt/redirect.ts:647

HTTP status code (301 or 302), when reported.

id ​

id: string

Defined in: packages/b2c-tooling-sdk/src/operations/mrt/redirect.ts:641

Identifier for get/update/delete: the from_path on legacy, the UUID on SCAPI.

source ​

source: string

Defined in: packages/b2c-tooling-sdk/src/operations/mrt/redirect.ts:643

The source path that triggers the redirect (legacy from_path / SCAPI source).

status? ​

optional status: string

Defined in: packages/b2c-tooling-sdk/src/operations/mrt/redirect.ts:653

Human-readable publishing status, when the backend reports one.