The B2C MCP panel is the workspace control center for connecting an AI app, choosing tool access, generating SFCC guidance, and inspecting requests. Open it with MCP Workspace in the B2C MCP view of the Intellij SFCC sidebar. It opens as the SFCC MCP Workspace editor tab

Open the MCP WorkspaceBrowse tools from StartChoose an AI appCreate the config

storefront

SFCC MCP Workspace.mcp.json

SFCC MCP for this workspace

Ready for AI tools in storefront

running

SFCC tools for your AI

This local Model Context Protocol (MCP) server starts automatically when enabled and ready, covering every open folder and linked cartridge. Connect Codex, Claude Code, Cursor, Copilot, or another MCP client, then ask in natural language.

Connect AISetup guide

Workspace

1 folder · 3 cartridges

storefront/Users/dev/storefrontReveal

Cartridge priorityapp_custom:int_payment:app_storefront_base(3)

ConnectionSandbox 01

Instance hostzzrx-001.dx.commercecloud.salesforce.com

Code versionversion2

Local server

running

MCP addresshttp://127.0.0.1:51734/mcp

Activity0 requests · 0 subscriptions

Last successNo requests yet

ProtectionLocal only · token off

Loggingmetadata only

View activity Server details

Tools & access

218 / 218 enabled · Review tools

90Local tools102Instance tools26Guarded actions0Disabled

Full access. Instance tools need an active connection. Guarded actions require explicit confirmation.

Read code. Trace routes, overrides, templates, and cartridge priority.Plan & validate. Find edit targets and check source, XML, and SCAPI changes.Inspect an instance. Read sites, code versions, remote files, and deployment state.Debug. Trace logs to source and inspect breakpoints, frames, and variables.

Runs on this computer. Tool results go to your AI app and may reach its model provider. Keep this VS Code workspace open while using MCP.

Tools & access

Your AI chooses tools automatically. Search to inspect access and prerequisites. Guarded changes require explicit confirmation.

Change access level

All toolsUnderstand codePlan and changeOperate an instanceDiagnose and debug

CategoryAll categories (218)hook.Any statusAny profileAny riskCatalog order

sfcc-full218 enabled · Codex: no published tool limit

Enable safe shown tools4 of 218 tools · 4 enabledClear filtersView selected toolEnable all shown…Reset overrides to profile

AvailableToolUsed forAction typeNeeds

Hook Searchintellijsfcc.hook.searchUse this to find system or custom hook declarations and scripts before implementing or editing SFCC hooks.Hookslocalproject · default

Hook Detailsintellijsfcc.hook.detailsUse this to inspect one hooks.json hook declaration before editing hook behavior. Returns hook type, source file paths, script/action references, cartridge context, and source offsets when available.Hookslocalproject · default

Hook Implementationsintellijsfcc.hook.implementationsUse this to list every indexed script/action implementation for a hook across cartridges. Prefer it before adding duplicate hooks or changing hook order/override behavior.Hookslocalproject · default

SCAPI Hook Contextintellijsfcc.scapi.hook.contextUse this before editing SCAPI hook endpoint code or Custom SCAPI implementation handlers. Combines rest-apis context, operationId, endpoint contract, relevant @types/scapi payload types, and required MCP workflow.SCAPI / Custom APIlocalproject · default

Connect your AI app

Choose an app and configuration target. Keep this VS Code workspace open while using MCP.

Setup guide

AI appClaude Code · Setup available · verification required

Codex · Setup available · verification required

Claude Code · Setup available · verification required

OpenCode · Setup available · verification required

Cursor · Setup available · verification required

Antigravity · Bridge available

Junie · Bridge available

Claude Code configuration

/Users/dev/storefront/.mcp.jsonSave configuration inClaude Code project MCP config · project · foundProject files: storefront

Hosted HTTPstdio bridgeCopy configOpen config

Existing files are opened for review, never merged automatically.

json468 B

1{

2 "mcpServers": {

3 "intellijsfcc_storefront_a41630bf": {

4 "type": "http",

5 "url": "http://127.0.0.1:51734/mcp",

6 "headers": {

7 "X-Intellij-SFCC-MCP-Workspace-Root": "/Users/dev/storefront",

8 "X-Intellij-SFCC-MCP-Workspace-Name": "storefront",

9 "X-Intellij-SFCC-MCP-Response-Profile": "anthropic",

10 "X-Intellij-SFCC-MCP-Provider": "anthropic",

11 "X-Intellij-SFCC-MCP-Agent-Family": "claude-code"

12 }

13 }

14 }

15}

1{

2 "mcpServers": {

3 "intellijsfcc_storefront_a41630bf": {

4 "type": "http",

5 "url": "http://127.0.0.1:51734/mcp",

6 "headers": {

7 "X-Intellij-SFCC-MCP-Workspace-Root": "/Users/dev/storefront",

8 "X-Intellij-SFCC-MCP-Workspace-Name": "storefront",

9 "X-Intellij-SFCC-MCP-Response-Profile": "anthropic",

10 "X-Intellij-SFCC-MCP-Provider": "anthropic",

11 "X-Intellij-SFCC-MCP-Agent-Family": "claude-code"

12 }

13 }

14 }

15}

main

The sidebar view

The B2C MCP view in the Intellij SFCC sidebar is a compact status card for the workspace server. Its title bar has Pick Agent / IDE Config and Open SFCC MCP Workspace

The status row shows the server state and the action that fits it:

Running gets an extra line when something needs attention, for example when no SFCC cartridges were detected or the server still runs although intellij-sfcc.mcp.enabled is off. Restart server sits next to the main action while the server runs or does not respond

Below the status are the server URL with Copy URL and the tool access profile, with Customize tool access… to open the tool policy in Settings. The context rows show the Instance of the active connection, its Site and code version, the Workspace, and Activity: requests in flight, the time of the last call, or No agent calls yet

Connect AI… and Pick Agent / IDE Config open the same picker. Choose an AI app, then Copy hosted HTTP config, Copy stdio bridge config, or Open or create project config file. MCP Workspace opens the full panel described below

Without active Intellij SFCC access the view shows SFCC MCP requires an active Intellij SFCC access with the button for your next step (Sign In, Choose a Plan, Renew Subscription or View Assigned Seat, and Open Dashboard when access could not be checked), Sync Access once you are signed in, and Stop local MCP. The Command Palette offers Intellij SFCC: Start SFCC MCP Server, Stop SFCC MCP Server, Restart SFCC MCP Server, Connect AI to SFCC MCP, Open SFCC MCP Workspace, and Open SFCC MCP Activity

Start

Start summarizes the included workspace folders and linked cartridges, the local server, and tool access. Its main action adapts to the server state, such as starting the server or opening Connect AI

The four workflow shortcuts lead to filtered tool lists:

These shortcuts help you find tools. Review a tool's availability and prerequisites before expecting the agent to use it

Connect AI

Choose an AI app to see its generated configuration, available transports, supported destinations, and verification steps

The setup summary keeps separate facts visible: whether a file was found, whether this panel copied or created the current setup, transport compatibility, protocol observations, and recent activity. A Stale status means connection or authentication details changed after the recorded setup, so generate the configuration again

For app-specific destinations and skills, see Codex, Claude Code, Cursor, or GitHub Copilot

Tools & Access

Search by task, tool name, or category. Use Understand code, Plan and change, Operate an instance, or Diagnose and debug to narrow the catalog, then select a tool to inspect its details

The table shows Available, Tool, Used for, Action type, and Needs. Those distinctions help explain why a tool is listed but cannot yet run: it may be disabled, require an active connection, or depend on a running debugger

• Change access level opens the profile settings
• Enable safe shown tools applies to the currently displayed safe tools
• Enable all shown… is a separate bulk action
• Reset overrides to profile restores the selected profile's tool choices
• Clear filters restores the full catalog view

Next to the search, Category and four menus narrow the list further:

Select a row, or use View selected tool, to open its Tool details, Behavior, and Requirements & activation. When Enable all shown… includes plan or guarded execute tools, a confirmation counts them before Enable Tools applies the change

After changing access, follow the selected client's refresh instructions. A client can keep an older tool list until its MCP connection refreshes

Skills & Guidance

Skill format selects the agent's native output format. Save project files in selects the destination workspace folder. Search by topic, task, trigger, MCP tool, or plugin feature, then inspect a skill and use Add to project. Existing files are preserved; installed skills offer Open installed

Pick your agent's formatFind a skillReview and add it

storefront

SFCC MCP Workspace

SFCC MCP for this workspace

Ready for AI tools in storefront

running

SFCC tools for your AI

This local Model Context Protocol (MCP) server starts automatically when enabled and ready, covering every open folder and linked cartridge. Connect Codex, Claude Code, Cursor, Copilot, or another MCP client, then ask in natural language.

Connect AISetup guide

Workspace

1 folder · 3 cartridges

storefront/Users/dev/storefrontReveal

Cartridge priorityapp_custom:int_payment:app_storefront_base(3)

ConnectionSandbox 01

Instance hostzzrx-001.dx.commercecloud.salesforce.com

Code versionversion2

Local server

running

MCP addresshttp://127.0.0.1:51734/mcp

Activity0 requests · 0 subscriptions

Last successNo requests yet

ProtectionLocal only · token off

Loggingmetadata only

View activity Server details

Tools & access

218 / 218 enabled · Review tools

90Local tools102Instance tools26Guarded actions0Disabled

Full access. Instance tools need an active connection. Guarded actions require explicit confirmation.

Read code. Trace routes, overrides, templates, and cartridge priority.Plan & validate. Find edit targets and check source, XML, and SCAPI changes.Inspect an instance. Read sites, code versions, remote files, and deployment state.Debug. Trace logs to source and inspect breakpoints, frames, and variables.

Runs on this computer. Tool results go to your AI app and may reach its model provider. Keep this VS Code workspace open while using MCP.

Skills & guidance

Built-in guidance is already available through MCP. A skill is an instruction file for recurring SFCC tasks; adding one does not change your instance.

Setup guide

Format & destination

Skill formatClaude Code skill

All supported agent styles

Codex / Agent Skills

OpenCode native skill

Claude Code skill

Cursor Rules

GitHub Copilot / VS Code

Gemini CLI context

Antigravity / Gemini context

JetBrains Junie guidelines

Trae IDE AGENTS-compatible

Cline rules

Roo Code rules

OpenClaw AGENTS-compatible

Hermes Agent AGENTS-compatible

Kimi Code Agent Skills

Generic Agent Skills

Save project files instorefront · /Users/dev/storefront

Destination pattern: .claude/skills/<skill>/SKILL.md · Existing files are opened or skipped and are never overwritten.

Project instruction file

Instruction formatCodex skillCopyAdd to project

Optional base instructions for using this workspace MCP.

Adds instructions at .agents/skills/sfcc-lsp/SKILL.md

Repo-scoped Codex skill. Keep this committed with SFCC projects that should always use the MCP gate.

TopicAll topics (37)controllerCopy full catalogAdd selected topicAdd all skills…

4 of 37 skills · Claude Code skill formatClear filters

Performance Guardrails & Hot PathsPerformance & Limits

Protect controller, model, hook, service, template, and job hot paths from excessive API calls, logging, remote calls, and slow loops.

3 files · Available to add

.claude/skills/sfcc-performance-guardrails/SKILL.md

Add to projectCopy

View details

Security Hardening & Secret BoundariesSecurity & Risk

Harden controllers, templates, services, hooks, and logs with server-side validation, authorization, CSRF, output encoding, and strict secret redaction.

3 files · Available to add

.claude/skills/sfcc-security-hardening/SKILL.md

Add to projectCopy

View details

SFRA Controller Routes & OverridesSFRA Runtime

Create, replace, append, or debug SFRA routes using endpoint indexes, override chains, module.superModule, exact middleware order, and Log Center validation.

3 files · Available to add

.claude/skills/sfcc-sfra-controller-routes/SKILL.md

Add to projectCopy

View details

Classic Controllers, SFRA Controllers & Migration BoundariesSFRA Runtime

Handle SFRA and legacy controller patterns, route lookup, middleware chains, response/view data, SiteGenesis migration boundaries, and safe endpoint ownership decisions.

3 files · Available to add

.claude/skills/sfcc-classic-and-sfra-controllers/SKILL.md

Add to projectCopy

View details

1---

2name: sfcc-sfra-controller-routes

3description: "Use when an SFCC task involves SFRA Controller Routes & Overrides, especially server.get or server.post. Do not use for non-SFCC work or without this workspace's Intellij SFCC MCP server."

4when_to_use: "Use for server.get; server.post; server.replace; server.extend; module.superModule; Checkout-PromoCredit in a Salesforce B2C Commerce project when the workspace-scoped Intellij SFCC MCP server is available."

5---

6

7# SFRA Controller Routes & Overrides

8

9Category: SFRA Runtime

10Claude note: this project skill intentionally does not set `allowed-tools` because MCP server names are workspace-scoped and may vary.

11

12## When To Use

13- server.get

14- server.post

15- server.replace

16- server.extend

17- module.superModule

18- Checkout-PromoCredit

19

20## When Not To Use

21- Do not use for non-SFCC work or general JavaScript/TypeScript tasks without Salesforce B2C Commerce context.

22- Do not continue when `intellijsfcc.project.context` cannot prove that the current workspace or file is inside one of `structuredContent.data.workspaceFolders`; switch to the matching workspace-scoped MCP server first.

23

24## Mandatory MCP Gates

25- Call `intellijsfcc.project.context` first. Use only the `intellijsfcc.*` MCP server started for the currently opened workspace, and verify the workspace or current file is inside one of `structuredContent.data.workspaceFolders`.

26- Call `intellijsfcc.task.plan` before edits and follow required `structuredContent.nextTools`.

SFRA Controller Routes & Overrides (Claude Code skill) created (3 files, 0 already existed).

main

Add selected topic generates the chosen topic's skills. Add all skills… generates the full catalog in the selected format. Both show the workspace and destination before writing

The separate Project instruction file control adds optional base guidance for using the workspace MCP. It has its own Instruction format selector and Copy / Add to project actions

See Skills & Guidance for concrete package layouts and an SFRA controller example

Activity

Activity lists recent requests and failures. Start here when an agent cannot discover tools, receives an error, or seems to be using the wrong project

1. Run the safe verification prompt from Connect AI
2. Find the new request by its timestamp and inspect its result
3. Use Show errors only to narrow failures, or clear filters if an expected request is hidden
4. Use Copy redacted diagnostics when you need a compact diagnostic report

Request history demonstrates past use. An idle server or an earlier success does not establish that a client is currently connected

The tab is made of these cards:

The Activity tab shows a red badge with the number of recent errors

Open detailed viewer opens the SFCC MCP Activity tab. It charts requests by source over time, lists every logged request page by page, and shows the metadata of the one you select. Its toolbar has Refresh, Open Latest Log, Locate Logs, Export, and Clear Logs. Export saves a redacted sfcc-mcp-activity-redacted.json that leaves out captured payloads and session identifiers

Settings

Settings contains the server controls, authentication configuration, tool policy, client refresh guidance, and activity capture settings. Use the server controls to start, stop, or restart the workspace server when needed

Request metadata is always logged on this computer. Complete payload capture under Diagnostic logging also stores full requests and responses, unredacted, for 15 minutes, Until MCP restart, or Indefinite (advanced). Leave it Off unless you are troubleshooting, because captured payloads can contain source code, tokens, and passwords

Troubleshooting