# sfcc-dev-mcp [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/taurgis/sfcc-dev-mcp  
**GitHub Stars:** 28  
**npm Downloads (last month):** 173  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/sfcc-dev-mcp

## Description
MCP server for Salesforce B2C Commerce Cloud development assistance

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "sfcc-dev-mcp": {
    "command": "npx",
    "args": ["-y","aegis"],
    "env": {
      "SFCC_HOSTNAME": "",
      "SFCC_USERNAME": "",
      "SFCC_PASSWORD": "",
      "SFCC_CLIENT_ID": "",
      "SFCC_CLIENT_SECRET": ""
    }
  }
}
```

**Requires environment variables:** `SFCC_HOSTNAME`, `SFCC_USERNAME`, `SFCC_PASSWORD`, `SFCC_CLIENT_ID`, `SFCC_CLIENT_SECRET` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What sfcc-dev-mcp MCP server does

The sfcc-dev-mcp MCP server connects an MCP client to Salesforce B2C Commerce Cloud development resources and, when configured, an SFCC instance. Its documentation features cover SFCC API classes and methods, Storefront Reference Architecture material, and ISML elements with examples and usage guidance.

It also provides development and diagnostic operations. Documentation-only mode includes cartridge generation and agent-instruction bootstrap features. Credentialed mode adds log and job-log analysis, system object definitions, code-version management, and script-debugger access. The server exposes only the capabilities available in the active configuration.

## How it works

Run the package with npx as an MCP stdio server. Without credentials, it offers 18 documentation-oriented tools and local project utilities. With valid SFCC credentials, it can expose up to 40 tools, including operations that require access to the instance.

Credential discovery follows a fixed order: an explicit `--dw-json` path takes precedence, followed by SFCC environment variables, then `dw.json` files found through MCP workspace roots. Workspace discovery is refreshed when the client reports changed roots. VS Code users can therefore open a workspace containing `dw.json` and start the server without passing a file path.

Tool calls are checked against runtime schemas before dispatch. Validation covers required fields, types, enums, numeric and integer limits, string constraints, and unknown object keys. Calls can respond to cancellation signals and can emit progress notifications when the client supplies a progress token.

## Setup and configuration

For documentation access, configure the client to run `npx sfcc-dev-mcp` with no credentials. Full instance access requires a hostname and at least one complete authentication pair: username and password, or client ID and client secret. Store credentials in `dw.json`, pass its path with `--dw-json`, or use the supported environment variables.

Optional storefront username and password values support script-debugger triggers for Basic-Auth storefronts. OAuth-only configurations may undergo a WebDAV capability check before log, job-log, or script-debugger tools are exposed.

## Tools and capabilities

The sfcc-dev-mcp MCP server groups its tools into these supported areas:

- SFCC API, SFRA, and ISML documentation search and lookup
- Log monitoring, error analysis, and job-log analysis
- System object and site-preference definitions
- Code-version management
- Script-debugger endpoint execution and inspection
- Cartridge structure generation within permitted workspace paths
- AGENTS.md and bundled-skill installation or merging

Generated files are restricted to workspace roots, or to the current working directory when workspace roots are unavailable. Home-directory fallback is blocked.

## Limitations and notes

Live diagnostics and instance operations require appropriate SFCC configuration; documentation mode does not require credentials. If a hostname is supplied, credentials must include a complete supported pair, and credentials without a hostname are not valid. The server no longer searches the current working directory for `dw.json` by default, so clients should provide workspace roots or use an explicit path. Backend errors are sanitized before being returned as MCP tool responses.

_Full upstream README: https://allmcps.com/mcp/sfcc-dev-mcp/readme_