Use Claude Code with the extension's SFCC tools to inspect project context, trace cartridge overrides, and check a change. The workspace server runs inside your open VS Code workspace; generated Claude skills provide the task guidance.
Connect from B2C MCP
Select Claude Code
Open B2C MCP → Connect AI and choose Claude Code. Check Start for the included workspace folders and local server status.
Choose a target and transport
The project target is .mcp.json, using a top-level mcpServers object. The panel can also open an existing ~/.claude.json user target. Choose the available Hosted HTTP or stdio bridge transport and follow its compatibility guidance.
Save the workspace entry
Use Create config for a missing project configuration. Existing files are opened without being changed; use Copy config to review and merge the generated entry.
Reload and verify
Use /mcp or restart Claude Code, as shown by the panel. You can also use the generated claude mcp list check. Run the safe verification prompt, then confirm the request in B2C MCP → Activity.
Use intellijsfcc.project.context and tell me whether this is an SFCC
workspace, all included workspace folders, and the detected cartridge
count. Do not change files or remote state.Check the returned folders before continuing. Keep the workspace open for later tool calls.
Generate Claude skills
Open Skills & Guidance, select Claude Code skill, and choose Save project files in. Search for SFRA Controller Routes & Overrides, review its details and preview, then select Add to project.
.claude/skills/sfcc-sfra-controller-routes/
SKILL.md
references/mcp-tool-map.md
scripts/print-mcp-workflow.mjsThe package contains the task instructions, MCP tool reference, and a helper that prints the workflow gates and recommended tools. Existing files are preserved.
The separate Project instruction file → Claude Code skill option adds the common SFCC MCP workflow at .claude/skills/sfcc-lsp/SKILL.md. The selector also offers Claude Code plugin skeleton with a manifest, MCP configuration placeholders, a base skill, and a README for completing that setup.
Try an SFRA task
Use the SFRA controller skill to explain how Product-Show is extended
in this workspace. Confirm the project, show the effective route owner,
follow module.superModule, and explain the middleware order with source
locations. Do not change files or remote state.Claude Code may discover some MCP tools through ToolSearch instead of showing every tool immediately. Ask for the SFCC task or tool you need, and use Tools & Access to confirm it is available on the server.
Troubleshooting
| Symptom | Next step |
|---|---|
| The MCP entry does not appear | Check the target selected in Connect AI, then use /mcp or restart Claude Code. |
| A tool list looks incomplete | Check server access first; deferred tool discovery can also affect the visible list. Refresh through /mcp after an access change. |
| The project is wrong | Compare the verification result with Start and use this workspace's generated configuration. |
| Configuration or authentication changed | Regenerate the setup and make a fresh verification request. |
| A skill already exists | Use Open installed and merge any desired changes from the preview. |
