b2c-config
Installation
SKILL.md
B2C Config Skill
For routine inspection, call config_inspect or b2c setup inspect directly;
no skill read is required. Keep secrets redacted; manually reading dw.json is usually unnecessary. Read the relevant section
here when configuring sources or diagnosing unexpected/missing values.
| Task | CLI | MCP | Preference / difference | Fallback |
|---|---|---|---|---|
| Inspect resolved configuration | b2c setup inspect |
config_inspect |
Either; same resolver, redacted by default. MCP accepts per-call project/instance overrides. | Inspect source files only for edits or unresolved issues. |
| Change configuration or authenticate | b2c setup, b2c auth |
No configuration-writing equivalent | CLI; inspect command help for the requested operation. | Edit the intended configuration source. |
If b2c is unavailable, use npx @salesforce/b2c-cli.
How the CLI Discovers Configuration
The CLI automatically detects instance hostname, credentials, tenant ID, MRT API key, and other settings from multiple sources. You usually do not need to pass --server, --client-id, --client-secret, --username, --password, --tenant-id, --short-code, or --api-key as flags — the CLI picks them up from the environment or config files.
Sources, in resolution order (highest priority first):