@W-20598954 MCP Vuepress docs by patricksullivansf · Pull Request #172 · SalesforceCommerceCloud/b2c-developer-tooling

patricksullivansf · 2026-02-19T23:10:57Z

Summary

Add MCP to Documentation site.

Also refactored internal workingDirectory variable names as projectDirectory everywhere (follow up to feat: rename --working-directory to --project-directory #199).

Testing

Pull PR and test doc site locally with pnpm run docs:dev

Dependencies

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

Tests pass (pnpm test)
Code is formatted (pnpm run format)

clavery · 2026-02-19T23:32:01Z

MCP Server should come before API reference in the header (we can also remove the latter from the homepage, it doesn't need to take up that space).

When I talked to Yuming I was wondering if we should try to "merge" the MCP in with the guides docs because there is so much overlap and then have sidebar sections specific to the CLI and MCP. Although maybe the sidebar would grow too large at that point.

We should make sure we're referencing back to the Authentication guide for detailed setup guides in AM.

patricksullivansf · 2026-02-20T03:22:57Z

MCP Server should come before API reference in the header (we can also remove the latter from the homepage, it doesn't need to take up that space).

Done, but I left API ref in the header. Seems useful and isn't crowded on my browser. YMMV.

When I talked to Yuming I was wondering if we should try to "merge" the MCP in with the guides docs because there is so much overlap and then have sidebar sections specific to the CLI and MCP. Although maybe the sidebar would grow too large at that point.

~~I can see the draw, but I believe the use cases and setup steps are different enough that it might cause confusion. Happy to be wrong though...~~

Done. (sort of). the MCP is partially integrated into the Guide: it shares the same nav menu and quick start includes the MCP.

We should make sure we're referencing back to the Authentication guide for detailed setup guides in AM.

Done. Linked the various auth references back to the configuration, and from there to the Auth guide. Also removed as much redundancy as I thought reasonable to balance comprehension vs maintainability. I'm sure more could be done here.

yhsieh1 · 2026-02-23T16:30:35Z

+| Parameter | Type | Required | Default | Description |
+|-----------|------|----------|---------|-------------|
+| `directory` | string | No | Current working directory | Path to directory to search for cartridges. The tool recursively searches for `.project` files to identify cartridges. |
+| `cartridges` | string[] | No | All found cartridges | Array of cartridge names to include in the deployment. Use this to selectively deploy specific cartridges when you have multiple cartridges but only want to update some. |


nit: Should we add "If not specified, all cartridges found in the directory are deployed." to be more clear?

yhsieh1 · 2026-02-23T16:37:29Z

+
+Returns a deployment result object containing:
+
+- `cartridges` - Array of cartridge names that were deployed


cartridges - Array of cartridge mappings that were deployed (each with name, src, dest)

yhsieh1 · 2026-02-23T16:38:08Z

+
+- `cartridges` - Array of cartridge names that were deployed
+- `codeVersion` - Code version name used for deployment
+- `hostname` - Instance hostname where cartridges were deployed


Seems hostname should be removed. Its not included in DeployResult

nice catch. fixed

yhsieh1 · 2026-02-23T16:40:36Z

+Returns a push result object containing:
+
+- `bundleId` - Unique identifier for the pushed bundle
+- `project` - MRT project slug


Should we update it to match PushResult?

projectSlug - MRT project slug

target - Target environment (if deployed)

fixed.

But brings up an interesting aside. Across the b2c tooling repo I think I see inconsistent usage of target, targetSlug, environment, and environmentSlug, not to mention the use of "environment" for process environment variables. Maybe we should standardize on one name for this concept?

The user facing terms of environment and project should always be used. The slug qualifier should be probably be dropped for ID. I'm ambivalent on whether we say ID or omit it. Consult what managed runtime itself uses in it's UI. Our "ui" (flags, etc) should use the same convention.

Internally, in the SDK, we still make use of the API conventions. Because those are still called project/target in the managed runtime API and will probably always. Logging is also safe to use these terms.

@clavery not exactly sure what the desired action here is. Currently the SDK returns targetSlug. If the user facing term is environment then maybe the SDK needs a consistent mapping utility to change the SDK names to user names? I could see the exact same code needed for CLI as MCP for PushResult, for example.

yhsieh1 · 2026-02-23T16:59:04Z

+
+| Parameter | Type | Required | Default | Description |
+|-----------|------|----------|---------|-------------|
+| `directory` | string | No | Current working directory | Path to directory to search for cartridges. The tool recursively searches for `.project` files to identify cartridges. |


Can we update the 'Current working directory' to something like:
Working directory from --working-directory flag or SFCC_WORKING_DIRECTORY env var (falls back to process.cwd())

yhsieh1 · 2026-02-23T18:54:21Z

+Projects with multiple markers (e.g., cartridges + PWA Kit) get combined toolsets. For example:
+- Cartridges + PWA Kit → CARTRIDGES, PWAV3, MRT, SCAPI
+
+## Testing the MCP Server Locally


Wonder should we remove this testing locally section? I feel this doc is for the end user but not for contributors who should reference contributor.md or mcp readme.md for local setup.

Moved all the development setup and guideles to a new MCP focused md file in the source package.

clavery · 2026-02-23T19:46:33Z

Lets get a changeset for the docs and the MCP and use this is as the starting point for MCP release changes

patricksullivansf · 2026-02-23T21:22:50Z

Lets get a changeset for the docs and the MCP and use this is as the starting point for MCP release changes

Done as a minor bump to dx-docs only. Please review.

yhsieh1 · 2026-02-23T21:52:51Z

@@ -1,12 +1,15 @@
 ---
-description: Introduction to the B2C CLI and SDK for Salesforce Commerce Cloud B2C code deployment, site management, and sandbox operations.
+description: Introduction to the B2C CLI, MCP Server, and SDK for Salesforce Commerce Cloud B2C code deployment, site management, and sandbox operations.


Just noticed, should 'Salesforce Commerce Cloud B2C' be changed to 'Salesforce B2C Commerce'? Same for https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/pull/172/changes#diff-a9f09e5fd39208124b216a0cac772b60ab660bf177b9ecd1ab87f18006cecdbcR7

Thank you. I did search for Commerce B2C and fixed a few more places including package.json names. Please review and let me know if I need to revert any these.
cc: @knhage @clavery

patricksullivansf · 2026-02-24T16:32:14Z

+  "description": "Salesforce B2C Commerce Command Line Tools",
  "version": "0.0.1-preview",


Was trying to apply some consistency of attribute ordering across package.json and arbitrarily chose description then version, but happy to use ither order or revert the order change.

patricksullivansf · 2026-02-24T20:33:04Z

    default: 'true'
-  working-directory:
-    description: 'Working directory for the command'
+  project-directory:


think i need to revert this? @clavery

patricksullivansf requested review from clavery, wei-liu-sf and yhsieh1 as code owners February 19, 2026 23:10

patricksullivansf requested review from allison-grady and sf-cboscenco February 19, 2026 23:11

patricksullivansf force-pushed the psullivan.W-20598954.mcpVueDocs branch from d201b54 to a0b4d31 Compare February 20, 2026 21:09

yhsieh1 reviewed Feb 23, 2026

View reviewed changes

patricksullivansf added 6 commits February 23, 2026 13:06

@W-20598954 MCP Vuepress docs

ddb108e

@W-20598954 MCP docs adjust menu order. integrate auth links

c7fd069

@W-20598954 MCP docs merge into existing guide

06a382f

@W-20598954 MCP docs edits from knhage

7e1f93b

@W-20598954 MCP docs emdash and whitespace fixes

2094398

@W-20598954 MCP docs edits from PR reviewers

1d62eb6

patricksullivansf force-pushed the psullivan.W-20598954.mcpVueDocs branch from c10c86e to 1d62eb6 Compare February 23, 2026 21:12

@W-20598954 MCP docs changeset

cfa9310

patricksullivansf requested a review from yhsieh1 February 23, 2026 21:23

yhsieh1 previously approved these changes Feb 23, 2026

View reviewed changes

yhsieh1 self-requested a review February 23, 2026 21:48

yhsieh1 reviewed Feb 23, 2026

View reviewed changes

@W-20598954 MCP docs B2C Commerce

4e8ba7c

patricksullivansf dismissed yhsieh1’s stale review via 4e8ba7c February 23, 2026 22:48

patricksullivansf requested review from clavery, knhage and yhsieh1 February 24, 2026 16:29

patricksullivansf commented Feb 24, 2026

View reviewed changes

patricksullivansf added 5 commits February 24, 2026 09:16

Merge branch 'main' into psullivan.W-20598954.mcpVueDocs

3b34c32

@W-20598954 working directory to project directory rename

259b5b3

Merge branch 'main' into psullivan.W-20598954.mcpVueDocs

4f62043

@W-20598954 SDK allow deprcated workingDirectory

e19a36e

Merge branch 'main' into psullivan.W-20598954.mcpVueDocs

0082087

clavery previously approved these changes Feb 24, 2026

View reviewed changes

Merge branch 'main' into psullivan.W-20598954.mcpVueDocs

b8722eb

patricksullivansf dismissed clavery’s stale review via b8722eb February 24, 2026 19:23

patricksullivansf requested a review from clavery February 24, 2026 19:30

clavery previously approved these changes Feb 24, 2026

View reviewed changes

yhsieh1 previously approved these changes Feb 24, 2026

View reviewed changes

patricksullivansf commented Feb 24, 2026

View reviewed changes

@W-20598954 revert CI CD working directory change

bfd07a1

patricksullivansf dismissed stale reviews from yhsieh1 and clavery via bfd07a1 February 24, 2026 20:41

patricksullivansf requested review from clavery and yhsieh1 February 24, 2026 20:41

yhsieh1 approved these changes Feb 24, 2026

View reviewed changes

clavery approved these changes Feb 24, 2026

View reviewed changes

patricksullivansf enabled auto-merge (squash) February 24, 2026 21:14

clavery disabled auto-merge February 24, 2026 21:23

clavery merged commit f82eaaf into main Feb 24, 2026
5 checks passed

clavery deleted the psullivan.W-20598954.mcpVueDocs branch February 24, 2026 21:24

github-actions Bot mentioned this pull request Feb 24, 2026

Next Release: changelog and version packages #205

Merged

patricksullivansf mentioned this pull request Feb 24, 2026

@W-21197996 Unregister placeholder tools and update readme #202

Merged

4 tasks

yhsieh1 mentioned this pull request Feb 24, 2026

@W-21105798: Scaffold Custom API MCP Tool #204

Merged

4 tasks


		Returns a deployment result object containing:

		- `cartridges` - Array of cartridge names that were deployed

		"description": "Salesforce B2C Commerce Command Line Tools",
		"version": "0.0.1-preview",

Conversation

patricksullivansf commented Feb 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Testing

Dependencies

Uh oh!

clavery commented Feb 19, 2026

Uh oh!

patricksullivansf commented Feb 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

yhsieh1 Feb 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

clavery commented Feb 23, 2026

Uh oh!

patricksullivansf commented Feb 23, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

patricksullivansf commented Feb 19, 2026 •

edited

Loading

patricksullivansf commented Feb 20, 2026 •

edited

Loading

yhsieh1 Feb 23, 2026 •

edited

Loading