Sfcc MCP Server

MCP server for Salesforce B2C Commerce Cloud development assistance including logs, debugging, and development tools. The sfcc mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

An AI-powered Model Context Protocol (MCP) server that provides comprehensive access to Salesforce B2C Commerce Cloud development tools, documentation, and runtime diagnostics.

• Extensibility — Adding a new tool usually means adding a schema + minimal handler logic (or a new handler if a new domain)
• Security — Tools that require credentials are never exposed when capability flags are false
• Testability — Unit tests target clients & modules; integration/MCP tests validate handler routing and response structure
• Performance — Tail log reads + lightweight caching (cache.ts, log-cache.ts) reduce unnecessary I/O

Its toolset

Everything the assistant can do here goes through one of these:

• OAuth — client-id + client-secret
• Real — time log analysis and job logs (13 tools)
• Call — time Capability Guarding** (src/core/server.ts): Rejects execution of tools that are unavailable in the current mode, so hidden tools are not
• Extensibility — Adding a new tool usually means adding a schema + minimal handler logic (or a new handler if a new domain)
• Security — Tools that require credentials are never exposed when capability flags are false
• Testability — Unit tests target clients & modules; integration/MCP tests validate handler routing and response structure
• Performance — Tail log reads + lightweight caching (cache.ts, log-cache.ts) reduce unnecessary I/O
• macOS — /var/folders/{user-id}/T/sfcc-mcp-logs/
• Linux — /tmp/sfcc-mcp-logs/
• Windows — %TEMP%\sfcc-mcp-logs\
• sfcc-mcp-info.log — General application logs and startup messages
• sfcc-mcp-debug.log — Detailed debug information (only when --debug is enabled)

Configuration

You will need 2 environment variables: SFCC_CLIENT_ID, SFCC_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at aegis on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Sfcc's toolset — OAuth, Real, Call and 11 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Sfcc.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the sfcc mcp server does with a few real requests.