Log inSubmit server

Hidden while we check this listing

Our automated checks found a problem, so this listing is out of search, browse and the API until it clears. It comes back on its own once the problem is fixed.

  • Package deprecated on the registry
Own this project? Claim it
Sfcc Dev MCP logo

Sfcc Dev MCP

Provides SFCC documentation, diagnostics, debugging, code-version, and cartridge tools through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Sfcc Dev MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "sfcc-dev-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "aegis"
      ],
      "env": {
        "SFCC_HOSTNAME": "YOUR_VALUE_HERE",
        "SFCC_USERNAME": "YOUR_VALUE_HERE",
        "SFCC_PASSWORD": "YOUR_VALUE_HERE",
        "SFCC_CLIENT_ID": "YOUR_VALUE_HERE",
        "SFCC_CLIENT_SECRET": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y aegis

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 8d ago.

Overview

The sfcc-dev-mcp MCP server exposes Salesforce B2C Commerce Cloud documentation, development utilities, and credentialed runtime diagnostics to MCP clients. It runs through npx in documentation-only mode or loads SFCC credentials from dw.json, environment variables, or MCP workspace roots for additional tools. Use it to search SFCC, SFRA, and ISML references, inspect logs and system objects, manage code versions, generate cartridges, or run script-debugger operations. Tool availability is filtered according to the configured credentials and capability checks.

Use cases

  • Search SFCC API, SFRA, and ISML documentation
  • Analyze SFCC logs and job logs
  • Generate a cartridge structure in a workspace
  • Inspect system objects and site preferences
  • Run credentialed script-debugger operations

Key features

  • SFCC, SFRA, and ISML documentation lookup
  • Credentialed log and job-log analysis
  • System object and code-version tools
  • Script-debugger endpoint access
  • Workspace-safe cartridge generation
  • Runtime argument validation with progress and cancellation support

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · aegis (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars28Stargazers on the source repository.
npm downloads173Package downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Sfcc Dev MCP works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Sfcc Dev MCP

sfcc-dev-mcp is an MCP server that connects AI clients to Salesforce B2C Commerce Cloud development resources and configured SFCC instances. Its main tools search SFCC, SFRA, and ISML documentation, analyze logs, inspect system objects, manage code versions, generate cartridges, and run script-debugger operations.

Run it through npx by configuring an MCP client with command `npx` and argument `sfcc-dev-mcp`. No package installation is required for the documented setup. Use the same configuration without credentials for documentation-only access, or add `--dw-json` for instance-related tools.

Yes, sfcc-dev-mcp supports VS Code workspace discovery. Open a workspace containing a `dw.json` file and run the server without the `--dw-json` argument; the server can discover credentials through MCP workspace roots.

Configure credentials with an explicit `--dw-json` path, supported environment variables, or a `dw.json` file in an MCP workspace root. A hostname and either username/password or client-id/client-secret are required for credentialed access.

Yes, log and job-log analysis are available when valid SFCC credentials enable the corresponding capabilities. Documentation-only mode does not include live log access, while full mode exposes real-time error monitoring and job-log tools.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSfcc Dev MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/sfcc-dev-mcp?style=directory)](https://allmcps.com/mcp/sfcc-dev-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/sfcc-dev-mcp"><img src="https://allmcps.com/api/badge/sfcc-dev-mcp?style=directory" alt="Sfcc Dev MCP on AllMCPs" /></a>