mcpField
B
b2c-job

b2c-job

github.com/salesforcecommercecloudCloud & DevOps5794 installsUpdated today
Repository

About b2c-job

A skill for running, waiting on, and inspecting existing Salesforce B2C Commerce jobs with the `b2c` CLI. It also covers site archive import and export, while directing MCP users to a code-mode reference for job operations.

Key features

  1. 01Run jobs and optionally wait
  2. 02Search executions and inspect logs
  3. 03Pass parameters or system-job bodies
  4. 04Import and export site archives

Use cases

  1. 01Running a scheduled or system job
  2. 02Checking failed job executions
  3. 03Importing or exporting site data

MCP support

No dedicated MCP job tool is available. In MCP sessions, the skill directs users to start, wait for, and review jobs in code mode; the CLI handles archive transfer and terminal use.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/salesforcecommercecloud/b2c-developer-tooling --skill b2c-job

After installing, type/b2c-jobin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

evals/
trigger-evals.json
references/
EXPORT.md
IMPORT.md
RUN-AND-MONITOR.md

Details

From the project README

Run and Monitor Jobs

Use b2c job for existing jobs. To create job steps or author jobs.xml, use b2c:b2c-custom-job-steps. If b2c is unavailable, use npx @salesforce/b2c-cli.

Configuration and tool choice

CLI and MCP share configuration: SFCC_* variables (including project .env), project/shared dw.json, and plugins; package.json provides nonsecret defaults. Use --project-directory when running outside the target project. Inspect with b2c setup inspect --json or MCP config_inspect; both mask secrets by default. Override configured values only when needed. For resolution issues, use b2c-cli:b2c-config.

No dedicated MCP job tool exists. In an MCP session, start, wait for, and review jobs in code mode (skill://mcp/b2c-mcp-scapi/references/jobs.md); use the CLI for archive transfer (import/export) and when running from a terminal.

Run and inspect

b2c job run my-job --wait --timeout 600
b2c job run my-job --wait -P key=value
b2c job search --job-id my-job --count 5
b2c job wait my-job execution-id --timeout 600
b2c job log my-job --failed

Rebuild a search index (system jobs take --body, never -P):

b2c job run sfcc-search-index-product-full-update --wait --body '{"site_scope":["MySite"]}'

job run returns immediately unless --wait is supplied. For raw system-job bodies, search indexing, standard step choices, execution deletion, and backend configuration: run and monitor. Deletion removes completed execution records; it does not cancel jobs.

Site archives

b2c job import ./archive --show-log
b2c job import ./storefront-export.zip --wait-for-storefront
b2c job export --site MySite --site-data campaigns_and_promotions --output ./export
b2c job export --storefront my-storefront --output ./export
b2c job export --all --output ./full-export

Import/export wait by default and transfer files over WebDAV. Jobs prefer SCAPI (sfcc.jobs.rw for writes, sfcc.jobs for reads); --api-backend auto falls back on supported SCAPI rejections. See the backend section in the run/monitor reference if access fails. Check job outcome before retrying a write.

Read only the relevant reference:

  • Import remote archives or directory subsets: import options.
  • Choose export data units or output paths: export.
  • Author/validate XML and verify imported settings: b2c-cli:b2c-site-import-export.
  • Apply ordered, tracked migrations: b2c-cli:b2c-import-set-migrations.

Output

Normal CLI output suffices for status. For scripting, save large --json results to a file and print selected fields; keep the exit code and inspect failures. See export, section compact-results. Avoid dumping full execution records or reading both JSON and human output for the same result.

Comments

Markdown supported