b2c-config

# MCP Configuration For MCP installation or tool selection, see [server setup](skill://mcp/server/SKILL.md). ## Inspect resolved values Call `config_inspect` directly with the task's absolute `projectDirectory`. No prior skill read is required. Secrets are masked by default (`unmask: false`). The result includes effective values, contributing sources, warnings, and `resolution` identifying the selected project, configuration file, and instance. Use the returned hostname, site, tenant, and other configured values. Report missing values rather than inventing them. Inspection does not verify remote credentials or connectivity. Reading `dw.json` manually is usually unnecessary: it may not be the selected file or contain the effective values. Avoid dumping configuration files or the environment to discover credentials. Inspect source files only for a requested edit or a specific issue the resolved output cannot explain. Set `unmask: true` only when the user explicitly requests secret values. ## Where configuration comes from MCP tools use the same resolver as the CLI. Value precedence, highest first: launch overrides/environment (including project `.env`), high-priority config plugins, `dw.json`, `~/.mobify` (MRT key), low-priority config plugins, then `package.json` under `b2c` for non-sensitive defaults. - Project: per-call `projectDirectory`, then server `--project-directory` / `SFCC_PROJECT_DIRECTORY`, then server working directory. The agent's project may differ from the server's working directory; pass it explicitly. - Primary file: per-call `configPath`, startup `--config` / `SFCC_CONFIG`, project `.env` `SFCC_CONFIG`, project `dw.json`, then shared global default. Relative `configPath` resolves from `projectDirectory`. - Instance: `instanceName` selects a named instance from the primary/shared catalog; otherwise configured active/default selection applies. Override only to select another target; use `resolution` to confirm it. - Configuration files are reloaded for each configuration-dependent tool call. Restart MCP after changing launch flags or its process environment. Existing debugger sessions retain their selected target. ## Setup and access Separate missing local values from missing external grants. `config_inspect` cannot create an API client, assign roles, or validate remote access. Explain the specific Account Manager, Business Manager, or Runtime Admin step when needed; changing a local scope list does not grant permission. When docs tools are available, use `docs_read({query: ID})` for these known IDs: | Need | Documentation ID / relevant topic | | ---------------------------------------------------- | ----------------------------------------------------------------- | | MCP credentials or project selection | `mcp-configuration` | | Configuration fields and precedence | `guide-configuration` | | Account Manager client, roles, scopes, tenant filter | `guide-authentication` / Account Manager and SCAPI Authentication | | BM WebDAV access key or MRT API key | `guide-authentication` / WebDAV Access or Managed Runtime API Key | | Debugger permission or MCP safety restriction | `mcp-security` | | SLAS client administration, when requested | `cli-slas` / required roles and client setup | For another setup question, `docs_search({query: "<specific setup issue>", category: "tooling"})`, then read the returned ID. Use available categories; tool/topic selection can exclude these docs. Public links below remain alternatives. Read only relevant pages; follow returned `nextOffset` when the needed topic lies later in an article. ## CLI, when requested From the same project, `b2c setup inspect --json` uses the same resolver and default masking. Match the environment, `--config`, and `--instance` selections when comparing results. For CLI setup or configuration commands, consult [b2c-cli/b2c-config](skill://b2c-cli/b2c-config/SKILL.md) when the broader skill collections are enabled, or the shared configuration documentation below. For authentication specifically, `skills_read({id: "b2c-cli/b2c-config", section: "authentication"})`. CLI browser-login instructions do not enable SCAPI Admin code-mode user auth. ## Further reading Read only for the configuration issue at hand: - [MCP configuration](https://salesforcecommercecloud.github.io/b2c-developer-tooling/mcp/configuration) - [Shared configuration and precedence](https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/configuration) - [Authentication setup](https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/authentication)