@salesforce/b2c-dx-mcp 0.4.2 → 0.4.4

package/README.md

@@ -1,8 +1,8 @@
-# Salesforce Commerce Cloud B2C MCP Server
+# Salesforce B2C Commerce MCP Server
 
-MCP (Model Context Protocol) server for Salesforce B2C Commerce Cloud developer experience tools.
+MCP (Model Context Protocol) server for Salesforce B2C Commerce developer experience tools.
 
-> ⚠️ **Active Development**: This package is under active development. All tools are currently **placeholder implementations** that return mock responses. Tool implementations will be added incrementally.
+> ⚠️ **Active Development**: This package is under active development. Some tools are currently **placeholder implementations** that return mock responses. Tool implementations will be added incrementally.
 
 ## Overview
 
@@ -12,15 +12,15 @@ The server automatically detects your project type and enables relevant tools. S
 
 ## Usage
 
-### Working Directory and Auto-Discovery
+### Project Directory and Auto-Discovery
 
-The most important flag is **`--working-directory`** (or env var `SFCC_WORKING_DIRECTORY`). It tells the server where your project is located, enabling:
+The most important flag is **`--project-directory`** (or env var `SFCC_PROJECT_DIRECTORY`). It tells the server where your project is located, enabling:
 
 1. **Auto-discovery** - Detects your project type and enables appropriate toolsets
 2. **Configuration loading** - Reads [`dw.json`](https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/configuration.html#configuration-file) from your project for credentials
 3. **Scaffolding** - Creates new files in the correct location
 
-> **Important:** MCP clients like Cursor and Claude Desktop spawn servers from the home directory (`~`), not your project. Always set `--working-directory`.
+> **Important:** MCP clients like Cursor and Claude Desktop spawn servers from the home directory (`~`), not your project. Always set `--project-directory`.
 
 **Cursor** (supports `${workspaceFolder}`):
 
@@ -29,7 +29,7 @@ The most important flag is **`--working-directory`** (or env var `SFCC_WORKING_D
   "mcpServers": {
     "b2c-dx": {
       "command": "npx",
-      "args": ["-y", "@salesforce/b2c-dx-mcp", "--working-directory", "${workspaceFolder}", "--allow-non-ga-tools"]
+      "args": ["-y", "@salesforce/b2c-dx-mcp", "--project-directory", "${workspaceFolder}", "--allow-non-ga-tools"]
     }
   }
 }
@@ -42,7 +42,7 @@ The most important flag is **`--working-directory`** (or env var `SFCC_WORKING_D
   "mcpServers": {
     "b2c-dx": {
       "command": "npx",
-      "args": ["-y", "@salesforce/b2c-dx-mcp", "--working-directory", "/path/to/your/project", "--allow-non-ga-tools"]
+      "args": ["-y", "@salesforce/b2c-dx-mcp", "--project-directory", "/path/to/your/project", "--allow-non-ga-tools"]
     }
   }
 }
@@ -50,7 +50,7 @@ The most important flag is **`--working-directory`** (or env var `SFCC_WORKING_D
 
 ### Project Type Detection
 
-The server analyzes your working directory and enables toolsets based on what it finds:
+The server analyzes your project directory and enables toolsets based on what it finds:
 
 | Project Type | Detection | Toolsets Enabled |
 |--------------|-----------|------------------|
@@ -66,14 +66,14 @@ The **SCAPI** toolset is always enabled. Hybrid projects (e.g., cartridges + PWA
 Override auto-discovery by specifying toolsets explicitly:
 
 ```json
-"args": ["--working-directory", "${workspaceFolder}", "--toolsets", "CARTRIDGES,MRT", "--allow-non-ga-tools"]
+"args": ["--project-directory", "${workspaceFolder}", "--toolsets", "CARTRIDGES,MRT", "--allow-non-ga-tools"]
 ```
 
 ### Prompting Tips and Examples
 
 AI assistants (like Cursor, Claude Desktop) automatically decide which MCP tools to use based on your prompts. To get the best results, use clear, specific prompts that describe what you want to accomplish.
 
-> ⚠️ **IMPORTANT**: **Explicitly mention "Use the MCP tool"** in your prompts for reliable tool usage. While AI assistants (like Cursor's Composer) can automatically select MCP tools based on context, explicit instructions ensure the assistant prioritizes MCP tools over general knowledge, especially when multiple approaches are possible. This is particularly important for getting project-specific, up-to-date information rather than generic responses.
+> ⚠️ **IMPORTANT**: **Explicitly mention "Use the MCP tool"** in your prompts for reliable tool usage. While AI assistants (like Cursor's Composer) can automatically select MCP tools based on context, explicit instructions ensure that the assistant prioritizes MCP tools over general knowledge, especially when multiple approaches are possible. This is particularly important for getting project-specific, up-to-date information rather than generic responses.
 
 #### Best Practices
 
@@ -90,7 +90,7 @@ AI assistants (like Cursor, Claude Desktop) automatically decide which MCP tools
 
 The `storefront_next_development_guidelines` tool provides critical architecture rules and best practices. **Use this tool first** when starting new Storefront Next development or when you need architecture guidance.
 
-**Good prompts:**
+**Prompt examples:**
 - ✅ "I'm new to Storefront Next. Use the MCP tool to show me the critical rules I need to know."
 - ✅ "I need to build a product detail page. Use the MCP tool to show me best practices for data fetching and component patterns."
 - ✅ "I need to build a checkout form with authentication and validation. Use the MCP tool to show me how to handle form submissions, authentication, and internationalized error messages."
@@ -114,7 +114,7 @@ The `storefront_next_development_guidelines` tool provides critical architecture
 
 ##### PWA Kit Development
 
-**Good prompts:**
+**Prompt examples:**
 - ✅ "I'm starting a new PWA Kit project. Use the MCP tool to get the development guidelines."
 - ✅ "Use the MCP tool to create a new product listing page component in my PWA Kit project."
 - ✅ "Use the MCP tool to recommend React hooks for fetching product data in PWA Kit."
@@ -153,14 +153,14 @@ Get registration status of custom API endpoints deployed on the instance (remote
 
 ##### Cartridge Deployment
 
-**Good prompts:**
+**Prompt examples:**
 - ✅ "Use the MCP tool to deploy my cartridges to the sandbox instance."
 - ✅ "Use the MCP tool to deploy only the app_storefront_base cartridge to production."
 - ✅ "Use the MCP tool to deploy cartridges from the ./cartridges directory and reload the code version."
 
 ##### MRT Bundle Operations
 
-**Good prompts:**
+**Prompt examples:**
 - ✅ "Use the MCP tool to build and push my Storefront Next bundle to staging."
 - ✅ "Use the MCP tool to push the bundle from ./build directory to Managed Runtime."
 - ✅ "Use the MCP tool to deploy my PWA Kit or Storefront Next bundle to production with a deployment message."
@@ -181,8 +181,8 @@ Credentials can be provided via **config files** (recommended), **environment va
 | **SCAPI** | `hostname` + `client-id` + `client-secret` (for `scapi_custom_apis_status`: requires `sfcc.custom-apis` scope) |
 | **CARTRIDGES** | `hostname` + `username` + `password` (or OAuth) |
 | **MRT** | `api-key` + `project` (optionally `environment`) |
-| **PWAV3** | `--working-directory` only (+ MRT config for deployments) |
-| **STOREFRONTNEXT** | `--working-directory` only (+ MRT/CARTRIDGES config for those tools) |
+| **PWAV3** | `--project-directory` only (+ MRT config for deployments) |
+| **STOREFRONTNEXT** | `--project-directory` only (+ MRT/CARTRIDGES config for those tools) |
 
 **Option 1: Config files (recommended)**
 
@@ -220,7 +220,7 @@ See [Flag Reference](#flag-reference) for all available flags and env vars.
 
 | Flag | Env Variable | Description |
 |------|--------------|-------------|
-| `--working-directory` | `SFCC_WORKING_DIRECTORY` | Project directory (enables auto-discovery and config loading) |
+| `--project-directory` | `SFCC_PROJECT_DIRECTORY` | Project directory (enables auto-discovery and config loading) |
 | `--toolsets` | — | Comma-separated toolsets to enable |
 | `--tools` | — | Comma-separated individual tools to enable |
 | `--allow-non-ga-tools` | — | Enable experimental (non-GA) tools |
@@ -378,7 +378,7 @@ pnpm run lint
 pnpm run clean
 ```
 
-### Working Directory
+### Project Directory
 
 Commands should be run from the `packages/b2c-dx-mcp` directory:
 
@@ -435,7 +435,7 @@ Configure your IDE to use the local MCP server. Add this to your IDE's MCP confi
 }
 ```
 
-> **Note:** Make sure the script is executable: `chmod +x /full/path/to/packages/b2c-dx-mcp/bin/dev.js`
+> **Note:** Make sure that the script is executable: `chmod +x /full/path/to/packages/b2c-dx-mcp/bin/dev.js`
 >
 > The script's shebang (`#!/usr/bin/env -S node --conditions development`) handles Node.js setup automatically.
 

package/dist/commands/mcp.js

@@ -7,7 +7,7 @@
  * MCP Server Command - Salesforce B2C Commerce Developer Experience
  *
  * This is the main entry point for the B2C DX MCP server, built with oclif.
- * It exposes B2C Commerce Cloud developer tools to AI assistants via the
+ * It exposes B2C Commerce developer tools to AI assistants via the
  * Model Context Protocol (MCP).
  *
  * ## Flags
@@ -151,7 +151,7 @@ import { TOOLSETS } from '../utils/index.js';
  * - `this.config` - package.json metadata and standard config paths
  */
 export default class McpServerCommand extends BaseCommand {
-    static description = 'Salesforce B2C Commerce Cloud Developer Experience MCP Server - Expose B2C Commerce Developer Experience tools to AI assistants';
+    static description = 'Salesforce B2C Commerce Developer Experience MCP Server - Expose B2C Commerce Developer Experience tools to AI assistants';
     static examples = [
         {
             description: 'All toolsets',
@@ -297,8 +297,8 @@ export default class McpServerCommand extends BaseCommand {
             tools: this.flags.tools ? this.flags.tools.split(',').map((s) => s.trim()) : undefined,
             allowNonGaTools: this.flags['allow-non-ga-tools'],
             configPath: this.flags.config,
-            // Working directory for auto-discovery. oclif handles flag with env fallback.
-            workingDirectory: this.flags['project-directory'],
+            // Project directory for auto-discovery. oclif handles flag with env fallback.
+            projectDirectory: this.flags['project-directory'],
         };
         // Add toolsets to telemetry attributes
         if (this.telemetry && startupFlags.toolsets) {

package/dist/registry.js

@@ -89,21 +89,21 @@ export function createToolRegistry(loadServices) {
  * Performs workspace auto-discovery and returns appropriate toolsets.
  * Always includes BASE_TOOLSET even if no project types are detected.
  *
- * @param flags - Startup flags containing workingDirectory
+ * @param flags - Startup flags containing projectDirectory
  * @param reason - Reason for triggering auto-discovery (for logging)
  * @returns Array of toolsets to enable
  */
 async function performAutoDiscovery(flags, reason) {
     const logger = getLogger();
-    // Working directory from --project-directory flag or SFCC_PROJECT_DIRECTORY env var
-    const workingDirectory = flags.workingDirectory ?? process.cwd();
-    // Warn if working directory wasn't explicitly configured
-    if (!flags.workingDirectory) {
-        logger.warn({ cwd: workingDirectory }, 'No --project-directory flag or SFCC_PROJECT_DIRECTORY env var provided. ' +
+    // Project directory from --project-directory flag or SFCC_PROJECT_DIRECTORY env var
+    const projectDirectory = flags.projectDirectory ?? process.cwd();
+    // Warn if project directory wasn't explicitly configured
+    if (!flags.projectDirectory) {
+        logger.warn({ cwd: projectDirectory }, 'No --project-directory flag or SFCC_PROJECT_DIRECTORY env var provided. ' +
             'MCP clients like Cursor and Claude Desktop often spawn servers from ~ instead of the project directory. ' +
             'Set --project-directory or SFCC_PROJECT_DIRECTORY for reliable auto-discovery.');
     }
-    const detectionResult = await detectWorkspaceType(workingDirectory);
+    const detectionResult = await detectWorkspaceType(projectDirectory);
     // Map all detected project types to MCP toolsets (union)
     // Note: getToolsetsForProjectTypes always includes BASE_TOOLSET
     const mappedToolsets = getToolsetsForProjectTypes(detectionResult.projectTypes);

package/dist/services.d.ts

@@ -185,13 +185,13 @@ export declare class Services {
      */
     getWebDavClient(): WebDavClient;
     /**
-     * Get the project working directory.
+     * Get the project project directory.
      * Falls back to process.cwd() if not explicitly set.
      *
      * This is the directory where the project is located, which may differ from process.cwd()
      * when MCP clients spawn servers from a different location (e.g., home directory).
      *
-     * @returns Project working directory path
+     * @returns Project project directory path
      */
     getWorkingDirectory(): string;
     /**

package/dist/services.js

@@ -234,16 +234,16 @@ export class Services {
         return this.b2cInstance.webdav;
     }
     /**
-     * Get the project working directory.
+     * Get the project project directory.
      * Falls back to process.cwd() if not explicitly set.
      *
      * This is the directory where the project is located, which may differ from process.cwd()
      * when MCP clients spawn servers from a different location (e.g., home directory).
      *
-     * @returns Project working directory path
+     * @returns Project project directory path
      */
     getWorkingDirectory() {
-        return this.resolvedConfig.values.workingDirectory ?? process.cwd();
+        return this.resolvedConfig.values.projectDirectory ?? process.cwd();
     }
     /**
      * Join path segments.

package/dist/tools/cartridges/index.js

@@ -45,7 +45,7 @@ function createCartridgeDeployTool(loadServices, injections) {
             directory: z
                 .string()
                 .optional()
-                .describe('Path to directory to search for cartridges. Defaults to current working directory if not specified. ' +
+                .describe('Path to directory to search for cartridges. Defaults to current project directory if not specified. ' +
                 'The tool will recursively search this directory for .project files to identify cartridges.'),
             cartridges: z
                 .array(z.string())
@@ -83,7 +83,7 @@ function createCartridgeDeployTool(loadServices, injections) {
                     codeVersion = active.id;
                     instance.config.codeVersion = codeVersion;
                 }
-                // Resolve directory path: relative paths are resolved relative to working directory, absolute paths are used as-is
+                // Resolve directory path: relative paths are resolved relative to project directory, absolute paths are used as-is
                 const directory = args.directory
                     ? path.isAbsolute(args.directory)
                         ? args.directory

package/dist/tools/storefrontnext/page-designer-decorator/index.js

@@ -530,7 +530,7 @@ export function createPageDesignerDecoratorTool(loadServices) {
         name: 'storefront_next_page_designer_decorator',
         description: 'Adds Page Designer decorators (@Component, @AttributeDefinition, @RegionDefinition) to React components. ' +
             'Two modes: autoMode=true for quick setup with defaults, or interactive mode via conversationContext.step. ' +
-            'Component discovery uses workingDirectory from flags/env. ' +
+            'Component discovery uses projectDirectory from flags/env. ' +
             'Auto mode: selects suitable props, infers types, generates code immediately. ' +
             'Interactive mode: multi-step workflow (analyze → select_props → configure_attrs → configure_regions → confirm_generation).',
         inputSchema: pageDesignerDecoratorSchema.shape,
@@ -540,7 +540,7 @@ export function createPageDesignerDecoratorTool(loadServices) {
             try {
                 // Validate and parse input
                 const validatedArgs = pageDesignerDecoratorSchema.parse(args);
-                // Use workingDirectory from services to ensure we search in the correct project directory
+                // Use projectDirectory from services to ensure we search in the correct project directory
                 // This prevents searches in the home folder when MCP clients spawn servers from ~
                 const services = loadServices();
                 const workspaceRoot = services.getWorkingDirectory();

package/dist/utils/types.d.ts

@@ -40,6 +40,6 @@ export interface StartupFlags {
     allowNonGaTools?: boolean;
     /** Path to config file (dw.json format) */
     configPath?: string;
-    /** Project working directory for tools (auto-discovery, scaffolding, etc.) */
-    workingDirectory?: string;
+    /** Project project directory for tools (auto-discovery, scaffolding, etc.) */
+    projectDirectory?: string;
 }

package/oclif.manifest.json

@@ -3,7 +3,7 @@
     "Symbol(SINGLE_COMMAND_CLI)": {
       "aliases": [],
       "args": {},
-      "description": "Salesforce B2C Commerce Cloud Developer Experience MCP Server - Expose B2C Commerce Developer Experience tools to AI assistants",
+      "description": "Salesforce B2C Commerce Developer Experience MCP Server - Expose B2C Commerce Developer Experience tools to AI assistants",
       "examples": [
         {
           "description": "All toolsets",
@@ -387,5 +387,5 @@
       "enableJsonFlag": false
     }
   },
-  "version": "0.4.2"
+  "version": "0.4.4"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/b2c-dx-mcp",
-  "version": "0.4.2",
-  "description": "MCP server for B2C Commerce Cloud developer experience tools",
+  "description": "MCP server for B2C Commerce developer experience tools",
+  "version": "0.4.4",
   "author": "Salesforce",
   "license": "MIT",
   "repository": "SalesforceCommerceCloud/b2c-developer-tooling",
@@ -79,7 +79,7 @@
     "ts-morph": "^27.0.0",
     "yaml": "2.8.1",
     "zod": "3.25.76",
-    "@salesforce/b2c-tooling-sdk": "0.5.2"
+    "@salesforce/b2c-tooling-sdk": "0.5.4"
   },
   "devDependencies": {
     "@eslint/compat": "^1",