Cursor

Connect Cursor to the SFCC workspace server and generate project rules for recurring cartridge tasks. Keep the VS Code workspace hosting MCP open while you work in Cursor.

Connect from B2C MCP

Select Cursor

Open B2C MCP → Connect AI and choose Cursor. Confirm the included workspace folders and local server state in Start.

Choose the configuration destination

Select project .cursor/mcp.json or user ~/.cursor/mcp.json in Save configuration in. The generated configuration uses a top-level mcpServers object and a workspace-scoped server name.

Follow the transport offered by the panel. Hosted HTTP connects directly to the local server; stdio bridge forwards through the generated local command. With local-token authentication, the panel directs Cursor to use the bridge.

Save and verify

Use Create config for a missing file, or Open config and Copy config to review an existing entry. Refresh MCP servers in Cursor settings or restart Cursor, then run the safe verification prompt. Check the new request in B2C MCP → Activity.

Safe verification prompt

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 generated setup also lists cursor-agent mcp list-tools as its CLI check. Confirm the workspace folders in the tool response before continuing.

Generate Cursor project rules

In Skills & Guidance, select Cursor Rules and the destination project. Search for a task, open View details and Open preview, then use Add to project.

For SFRA Controller Routes & Overrides, the output is:

Project-relative destination

.cursor/rules/sfcc-sfra-controller-routes.mdc

This is one MDC file with a description, applicable file globs, alwaysApply: false, the SFCC workflow, and an inline MCP tool map. The controller rule targets controller JavaScript files under cartridge/controllers/.

For common MCP guidance, choose Cursor Rules in the separate Project instruction file selector. It writes .cursor/rules/sfcc-lsp-mcp.mdc. Existing rules are preserved when you generate them again.

Try a cartridge-aware task

Inspect the active controller

Use the SFRA controller rule to inspect Product-Show in this workspace.
Confirm the project, identify every indexed implementation, and show
which cartridge owns the effective route. Explain its override chain
and middleware order with source locations. Do not edit files.

When you later ask for a change, have the agent check the effective owner and diagnostics after editing. Use Activity to inspect the actual MCP calls.

Troubleshooting

Symptom	Next step
Hosted HTTP is unavailable	Use the panel's stdio bridge setup for the current authentication mode.
Cursor cannot find the server	Confirm the hosting workspace is open, check the chosen project or user configuration, and refresh MCP servers.
Tools are stale after an access change	Review Tools & Access, then refresh Cursor's MCP servers or restart the session.
A rule is not used for a file	Check its generated `globs` and that the rule is under this project's `.cursor/rules/`.
Generated guidance did not update	Open the installed rule and merge the desired changes from its preview.

Skills & Guidance

Review rule formats, destinations, and topic generation.

B2C MCP panel

Inspect transport compatibility, access, and activity.