B2C MCP is the plugin's own MCP server. It gives an AI agent what the IDE knows about your SFCC project: the cartridge path, types, routes, hooks, logs, the debugger and your instances. The agent works within the preset you pick, and every change to an instance starts as a plan the server checks before it runs
Connect Agents
Connect Claude Code, Codex, Cursor, GitHub Copilot, Junie, Gemini CLI, OpenCode or any MCP client to B2C MCP, with what each config field means
Tools & Presets
The ten B2C MCP toolsets, the risk of each tool, the presets that decide what agents may do, the Tools tab and Block Writes Now
Instances
How a B2C MCP agent picks an instance, what it sees about your connections, work across several instances, and what production and sandboxes take
Files & Deploys
What a B2C MCP agent may do on WebDAV root by root, uploads and bulk uploads, deploys to one or several instances, and code versions
Debugging with Agents
What a B2C MCP agent can drive in your script and pipeline debug session, where it works, agent breakpoints, captures and evaluate
Plans & Safety
How B2C MCP plans a change, what the server checks before it runs, how to stop agents, the audit log and how credentials stay out
Skills
The 23 SFCC skills that teach an agent the B2C MCP tool order and the rules that bite, four ways to add them, agent formats and updates
What Agents Can Do
Prompts that work with B2C MCP and the tools each one runs, from checking for errors to shipping a fix, sandboxes and live debugging
Activity & Analytics
Watch every B2C MCP request with what it sent and got back, the agents connected now, plans and the audit log, then read timings and context cost
Open it
The B2C MCP button sits on the right bar, after B2C Metadata. It appears in projects with SFCC code, like B2C Credentials, see Projects without SFCC code
| From | How |
|---|---|
| The tool window bar | Click B2C MCP |
| The Tools menu | Tools › Salesforce B2C Commerce › B2C MCP › Open B2C MCP |
| Find Action | Press Cmd+Shift+A (Ctrl+Shift+A) and type Open B2C MCP |
| Getting Started | The setup step Connect AI agents has Open B2C MCP and Connect Agent, see Use Getting Started |
Tools menu
Tools › Salesforce B2C Commerce › B2C MCP holds the server's actions. Find Action finds them too
| Action | What it does |
|---|---|
| Open B2C MCP | Opens the tool window |
| Connect Agent… | Sets up an AI agent to use this project's server, see Connect Agents |
| Start B2C MCP Server | Starts the server |
| Stop B2C MCP Server | Stops the server and disconnects every agent |
The title bar
The server's actions sit in the tool window's title bar, so every tab shows them
| Part | What it does |
|---|---|
| Start B2C MCP Server, Stop B2C MCP Server | Starts or stops the server. Stopping disconnects every agent |
| Connect Agent… | Lists the agents. Pick one to set it up, see Connect Agents |
| Gear menu | Show Guide and Settings… |
While the server isn't running, a line over every tab says why, such as The server is stopped, so agents cannot connect, with Start. It hides while the server runs
The preset and Block Writes Now sit on the Tools tab, next to the tools they change, see The Tools tab
The tabs
| Tab | What it shows |
|---|---|
| Server | The server's state, its URL and port, and every agent you connect, see Server tab |
| Tools | Every tool by toolset, with its risk and its numbers, see The Tools tab |
| Activity | Every request as it arrives, the agents connected now, plans and the audit log, see Activity |
| Analytics | Calls, errors, latency and context cost per tool and agent, see Analytics |
Server tab
The B2C MCP Server card sits at the top. Beside the B2C MCP mark it shows the server's state and what it means for agents, such as Running · 2 agents connected or The server is stopped, so agents cannot connect, with Start, or Stop and Restart, right under it. Hover the state for when the server started and the address it listens on. When the server could not start, the reason shows in red
Under the state, a row for each value. Hover the help icon after a value for what it means
| Row | What it shows | Action |
|---|---|---|
| URL | The address of this project's server, such as http://127.0.0.1:64780/mcp/p/3f9a1c7e. Agents also need a client key of their own, so connect them with Connect Agent | Copy at the start of the field |
| Port | The port the server listens on. When it was taken, the port the server took instead | Apply after you type another port. Agents connected on the old port need their config again |
| Other projects | Other open projects the server serves |
Connect an Agent comes next:
- MCP name: the name agents list this project under, so you can ask for work "in acme"
- Agent: a selector with every agent and its status. Open it to see each agent's client ID, where its config goes and its open sessions, and hover the selector or an agent to see its card at once: why it has its status and where its config goes
- Under the selector: Connect Agent… for the picked agent, Add SFCC Skills…, Revoke Client Key, Renew All Client Keys… and How client keys work, which shows what a client key does, see Client keys. Each name sits above its field at any width. The buttons sit two to a row in even columns from the left, or one under another in a narrow tool window, so nothing is cut
Sessions are on the Activity tab and instances on the Analytics tab
Guide
The first time B2C MCP opens, a few tips walk you through it, each pointing at its part and scrolling it into view: the server's state, its URL, the Agent selector, Connect Agent…, how client keys work, the preset, the tool checkboxes and their risks on Tools, then Activity and Analytics. The first time Connect Agent… opens, four more tips show the agent, its tools, instances and skills, the four ways to connect and Test Connection. Click Next, or Skip Guide to end them all. Show Guide in the gear menu runs both again, and Show tips in the tool window in Settings turns them off
Gear menu
The tool window's gear menu has Show Guide, which runs the tips again, and Settings…, which opens Settings
Notifications
B2C MCP notifications use the Intellij SFCC MCP group, which you can quiet in Settings › Appearance & Behavior › Notifications
| Notification | When | Actions |
|---|---|---|
| The B2C MCP server could not start | The ports are taken or the process failed, with the reason | Try Again, Open Settings |
| Claude Code connected to B2C MCP, for example | An agent connects to this project for the first time | Add SFCC Skills while that agent has no SFCC skills in the project, Don't Ask Again, Disconnect, Open Settings |
| B2C MCP refused and the tool | The Tools access, an instance the agent may not reach, or Block Writes Now refused a destructive call. Once per session and tool | Show Activity |
How it works
The agent connects
The agent calls this project's URL over HTTP with the client key from its config, which Connect Agent wrote, copied or ran for it. The server answers only on 127.0.0.1, and the IDE's own token never leaves the IDE
It starts with the project
The first call is intellijsfcc_project_context. It returns the cartridges, the active instance and the next tools for the task you gave
It reads proof from the IDE
Cartridge order, module.superModule, types, routes, hooks and templates come from the IDE's indexes, so the agent edits the copy that runs instead of guessing
It plans a change
A change to an instance starts as a plan: a preview of every file, code version or sandbox it touches. Nothing changes yet
It runs the plan
intellijsfcc_mutation_execute runs the plan when the agent's tools and instances allow it. The server checks the plan again first, see Plans & Safety
It checks the result
The agent verifies its work, such as new errors in the Log Center after an upload. Every upload, deploy, delete and activation also shows in B2C Sync Log
Where the data is kept
Everything stays on this computer and nothing is sent anywhere. No file holds a credential
| What | Where | How to remove it |
|---|---|---|
| Plans | <IDE system folder>/intellij-sfcc/mcp/plans/ | They expire after 15 minutes |
| The audit log of every write | <IDE system folder>/intellij-sfcc/mcp/audit/, one file a month | Kept 90 days |
| Analytics | <IDE system folder>/intellij-sfcc/mcp/analytics/, one file a day | Clear Analytics on Analytics, or a shorter Keep daily analytics: |
| Requests and their payloads | <IDE system folder>/intellij-sfcc/mcp-activity/, one folder per project | Purge on Activity, or a shorter Keep requests for: |
| The bridge and the endpoint file | <IDE system folder>/intellij-sfcc/mcp/. Only you can read the endpoint file | Kept by the IDE |
| The lock file | .intellij-sfcc/mcp-jetbrains.json in the project, while the server runs | Removed when the server stops |
| The skills manifest | .intellij-sfcc/agent-files.json in the project, see Skills | Delete it with the skills |
| Agent configs | The file Write Config wrote, such as .mcp.json | Delete the server's entry |
License
Agents need a valid license or trial. Without one, the server lists no tools and tells the agent why, and the License row reads No license or trial: the server lists no tools, see Purchase & License
Settings
Open Settings › Tools › Intellij SFCC › MCP Server. The settings apply to every project
| Setting | Default | What it does |
|---|---|---|
| Start the server: | When a B2C Commerce project opens | Or Only when I start it, or When the IDE starts |
| Port: | 64780 | When it is taken, the next free port up to 64799 is used |
| Keep port 64780 for agent configs | On, after the first start | Agent configs keep working after a restart while the port stays the same |
| Preset: | SFCC read only | Which tools agents see, the same as on the Tools tab, see Presets |
| Custom toolsets: | None | The toolsets of the Custom preset |
| Custom maximum risk: | Read only | Read only, Local writes, Plans or Everything, used when the preset is Custom |
| Tools turned off: | None | One tool name per line, off on top of the preset |
| Block Writes Now | Off | Agents get read tools only until you turn this off |
| JSON text for clients: | None | Client names, separated by commas, that get the JSON envelope as text instead of compact text |
| Shared sandbox tag: | shared | A sandbox with this tag gets a warning in its plans, and its instance writes count as Live change |
| Keep request and response payloads | On | Activity shows what each request sent and got back, redacted. A payload that holds a stored credential is never written. Turning this off deletes the stored payloads and keeps the rows |
| Keep requests for: | 30 days | 1, 7, 30, 90 or 365 days, or Until the size limit |
| Maximum size per project: | 256 MB | At this size the oldest payloads are deleted first, then the oldest rows |
| Keep daily analytics: | 30 days | 1, 7, 30 or 90 days |
| Also serve the tools through the IDE MCP server | Off | For agents already set up with the IDE MCP server. The same tools and rules apply |
| Log the MCP protocol | Off | Writes every message to idea.log, redacted. For troubleshooting only |
| Show tips in the tool window | On | Shows the Guide |
Keyboard
B2C MCP has no default keys. Assign your own to Open B2C MCP, Connect Agent…, Start B2C MCP Server and Stop B2C MCP Server in Settings › Keymap
Troubleshooting
| Symptom | What to do |
|---|---|
| No B2C MCP button | The project has no SFCC code yet, see Projects without SFCC code |
| The state reads Stopped | Click Start. To start it with the project, pick When a B2C Commerce project opens in Start the server: |
| The state reads Error | The Process row says why: no server for this system, a damaged copy, security software blocks it, or every port from 64780 to 64799 is taken. Fix the cause, then click Restart |
| The server keeps ending | It restarts after 0.5, 1, 2, 5 and 10 s, and gives up after five quick ends. The Process row shows why, with Restart |
| Port 64780 is taken | The server takes the next free port up to 64799. Agents that use the bridge find it on their own |
| The agent sees no tools | Check the license. While the IDE is closed, the bridge answers with no tools and tries again every 5 s |
| A tool is missing | It is off or not in the preset, see Tools & Presets. Agents can't turn tools on |
The agent reports risk-not-allowed | The Tools access, the agent's own tools or instances, or Block Writes Now leaves the call out, see Connect Agents |
| The bridge is not installed yet. Start the server to install it | Click Start, then open Connect Agent again |
| Writes stopped working | Block Writes Now is on. Turn it off on the Tools tab |