Skip to content

W-21260424 Update documentation for mcp config discrepancy#164

Merged
allison-grady merged 4 commits into
mainfrom
t/commerce/W-21260424/mcp-config
Feb 20, 2026
Merged

W-21260424 Update documentation for mcp config discrepancy#164
allison-grady merged 4 commits into
mainfrom
t/commerce/W-21260424/mcp-config

Conversation

@allison-grady
Copy link
Copy Markdown
Contributor

@allison-grady allison-grady commented Feb 18, 2026

Summary

Update paved path documentation to use npx in mcp.json config.

Testing

How was this tested?

Manual Testing:

  • Pull latest changes from main and build
  • From storefront-next project, restart the b2c MCP from Cursor Settings and verify that the Output logs detect cartridges and storefront-next project types

Dependencies

  • [ X] No net-new third-party dependencies were added
  • [X ] If net-new third-party dependencies were added, rationale/discussion is included and 3pl-approved is set by a maintainer

  • [ X] Tests pass (pnpm test)
  • [X ] Code is formatted (pnpm run format)

@allison-grady allison-grady marked this pull request as ready for review February 18, 2026 20:22
@allison-grady allison-grady changed the title W-21260424 Update documentation W-21260424 Update documentation for mcp config discrepancy Feb 18, 2026
Comment thread packages/b2c-dx-mcp/README.md Outdated

> **Important:** MCP clients like Cursor and Claude Desktop spawn servers from the home directory (`~`), not your project. Always set `--working-directory`.

When using `"command": "node"`, the shebang in `bin/dev.js` is not run, so the server loads from built `dist/`. **Build the project to latest** (`pnpm run build` from the repo root) so auto-discovery works. Without a fresh build, auto-discovery can fail—notably **Storefront Next** in monorepos like [storefront-next](https://github.com/SalesforceCommerceCloud/storefront-next), because that detector is the only one that walks workspace packages. Optional: add `"env": { "NODE_OPTIONS": "--conditions development" }` to run from source instead (no build needed).
Copy link
Copy Markdown
Contributor

@patricksullivansf patricksullivansf Feb 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's discuss this further, but my first takes on this:

  • the description is too technical for a how to get started README.
  • as this is the paved path section maybe we encourage npm with npx similar to PWA Kit MCP Setup

@allison-grady allison-grady merged commit b9440fe into main Feb 20, 2026
4 checks passed
@allison-grady allison-grady deleted the t/commerce/W-21260424/mcp-config branch February 20, 2026 18:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants