Use the extension's workspace MCP server from GitHub Copilot in VS Code. Generate scoped SFCC instructions for recurring tasks and keep the workspace open while Copilot calls the extension's tools
Connect from B2C MCP
Select GitHub Copilot
Open B2C MCP → Connect AI and choose GitHub Copilot. Check Start for the included folders and local server status
Choose a configuration target
Select project .vscode/mcp.json or an available VS Code user MCP target. The workspace configuration uses a top-level servers object. Copy the entry generated for this workspace
Create or review the setup
Choose an available Hosted HTTP or stdio bridge transport. Use Create config for a missing supported target. Existing files open without being modified; use Copy config to review and merge the generated entry
Verify in VS Code
Run MCP: List Servers from the Command Palette. Follow the panel's instructions to restart the server from VS Code MCP controls, then ask Copilot to run the safe verification prompt. 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.The returned folders should match this workspace. A configuration file alone does not confirm that Copilot has called the server
Built-in Copilot tools
Use the SFCC MCP server first. The extension also registers four language model tools directly with VS Code as a fallback for workspaces without it. They need no MCP configuration: switch Copilot Chat to agent mode and keep them selected in the chat tools picker, where they are grouped under the extension's name. Reference one in a prompt with # and its name, for example #intellijsfcc_cartridges_list
The four tools hide once an Intellij SFCC MCP server is declared in the workspace .vscode/mcp.json or in the VS Code user mcp.json, so Copilot does not get the same check twice. Remove that server entry and they come back
| Tool | Reference name | What it returns |
|---|---|---|
| Is SFCC Project? | intellijsfcc_is_sfcc_project | Whether the open workspace is an SFCC project, based on its detected cartridges |
| Get Cartridges List | intellijsfcc_cartridges_list | The project's cartridges, B2C modules, and global modules with their paths and counts |
| Get File Top Override | intellijsfcc_get_file_top_override | Whether a file is overridden in a higher-priority cartridge, and which file to edit instead |
| Custom SCAPI Endpoint Pattern | intellijsfcc_custom_scapi_endpoint_pattern | A guide to custom SCAPI endpoints: the api.json, schema.yaml, and script files and the two implementation patterns to match |
While a tool runs, Copilot shows its progress message, such as Checking if file is overridden in other cartridges.... All tools except Is SFCC Project? need active Intellij SFCC access. On a paused device every tool answers with the pause reason instead of running
These four tools cover the most common checks. The SFCC MCP server gives Copilot the full catalog of project, sandbox, log, and debugger tools, these checks included
Generate scoped instructions
In Skills & Guidance, select GitHub Copilot / VS Code and the destination project. Find a skill, inspect its details and preview, then select Add to project
For SFRA Controller Routes & Overrides, the output is:
.github/instructions/sfcc-sfra-controller-routes.instructions.mdThe generated file includes an applyTo pattern and the SFCC task workflow. The controller skill applies to controller JavaScript files under cartridge/controllers/. Existing instruction files are preserved
For common guidance across SFCC tasks, choose GitHub Copilot instructions in Project instruction file. It writes .github/copilot-instructions.md, which contains the base workspace and MCP workflow. Topic instructions and the base file have separate destinations and serve different scopes
Try an SFRA task
Use the SFRA controller instructions to explain Product-Show.
Confirm the SFCC workspace, list its indexed implementations, and show
the effective cartridge owner, module.superModule chain, and middleware
order. Include source locations. Do not edit or deploy anything.Once the target is clear, ask for the specific source change and a diagnostics check. Activity lets you review which MCP tools were used
Troubleshooting
| Symptom | Next step |
|---|---|
| The server is missing from VS Code | Check .vscode/mcp.json was selected for this workspace, then use MCP: List Servers |
| The server entry exists but no requests appear | Restart it through VS Code MCP controls and run the verification prompt in Copilot |
| Tools changed but Copilot still sees the old list | Review Tools & Access and restart the client MCP connection |
| A scoped instruction is not used | Check its applyTo pattern and destination against the file and project being edited |
| An instruction file did not change | Open the installed file and compare the preview; the extension does not overwrite it |
| A built-in tool replies that Intellij SFCC access is required | Select Sync Access in the Account panel, then ask again |