@salesforce/b2c-dx-mcp 0.4.9 → 0.4.11

package/README.md

@@ -5,45 +5,64 @@ MCP (Model Context Protocol) server for Salesforce B2C Commerce developer experi
 > [!NOTE]
 > This project is currently in **Developer Preview**. Tools are functional but require `--allow-non-ga-tools` to enable. Additional tools will be added in future releases.
 
-This MCP server enables AI assistants (Cursor, Claude Desktop, and others) to help with B2C Commerce development tasks. It provides toolsets for **SCAPI**, **CARTRIDGES**, **MRT**, **PWAV3**, and **STOREFRONTNEXT** development.
+This MCP server enables AI assistants (Cursor, Claude Code, and others) to help with B2C Commerce development tasks. It provides toolsets for **SCAPI**, **CARTRIDGES**, **MRT**, **PWAV3**, and **STOREFRONTNEXT** development.
 
 Full documentation: [https://salesforcecommercecloud.github.io/b2c-developer-tooling/mcp/](https://salesforcecommercecloud.github.io/b2c-developer-tooling/mcp/)
 
 ## Installation
 
-**Prerequisites:** Node.js 22.0.0 or higher, MCP client (Cursor, Claude Desktop, or compatible)
+**Prerequisites:** Node.js 22.0.0 or higher, MCP client (Cursor, Claude Code, GitHub Copilot, or compatible)
 
-**Cursor** (supports `${workspaceFolder}`):
+**Cursor** (project-level configuration - recommended):
 
 ```json
 {
   "mcpServers": {
-    "b2c-dx": {
+    "b2c-dx-mcp": {
       "command": "npx",
-      "args": ["-y", "@salesforce/b2c-dx-mcp", "--project-directory", "${workspaceFolder}", "--allow-non-ga-tools"]
+      "args": ["-y", "@salesforce/b2c-dx-mcp@latest", "--allow-non-ga-tools"]
     }
   }
 }
 ```
 
-**Claude Desktop** (use explicit path):
+> **Note:** Project-level configuration (`.cursor/mcp.json`) automatically detects your project location. For user-level configuration, add `--project-directory "${workspaceFolder}"` to the args array.
+
+**GitHub Copilot / VS Code**:
 
 ```json
 {
-  "mcpServers": {
-    "b2c-dx": {
+  "servers": {
+    "b2c-dx-mcp": {
+      "type": "stdio",
       "command": "npx",
-      "args": ["-y", "@salesforce/b2c-dx-mcp", "--project-directory", "/path/to/your/project", "--allow-non-ga-tools"]
+      "args": ["-y", "@salesforce/b2c-dx-mcp@latest", "--allow-non-ga-tools"]
     }
-  }
+  },
+  "inputs": []
 }
 ```
 
+> **Note:** GitHub Copilot/VS Code uses `"servers"` (not `"mcpServers"`) and requires `"type": "stdio"` for stdio-based servers.
+
+**Claude Code**:
+
+Claude Code supports MCP servers via CLI installation:
+
+```bash
+# Project scope (recommended)
+cd /path/to/your/project
+claude mcp add --transport stdio --scope project b2c-dx-mcp -- npx -y @salesforce/b2c-dx-mcp@latest --allow-non-ga-tools
+
+# User scope
+claude mcp add --transport stdio --scope user b2c-dx-mcp -- npx -y @salesforce/b2c-dx-mcp@latest --allow-non-ga-tools
+```
+
 See the [Installation Guide](https://salesforcecommercecloud.github.io/b2c-developer-tooling/mcp/installation) for detailed setup.
 
 ## Configuration
 
-Always set `--project-directory` (or `SFCC_PROJECT_DIRECTORY`). MCP clients spawn from the home directory (`~`), not your project.
+**Project-level configuration** (recommended for Cursor and GitHub Copilot) automatically detects your project location. For **user-level configuration** or when using explicit paths, set `--project-directory` (or `SFCC_PROJECT_DIRECTORY`). MCP clients spawn from the home directory (`~`), not your project.
 
 | Environment Variable | Description |
 |---------------------|-------------|

package/dist/commands/mcp.d.ts

@@ -113,9 +113,9 @@ export default class McpServerCommand extends BaseCommand<typeof McpServerComman
      * - `this.telemetry` - Telemetry instance (auto-initialized from package.json config)
      *
      * oclif provides standard config paths via `this.config`:
-     * - `this.config.configDir` - User config (~/.config/b2c-dx-mcp)
-     * - `this.config.dataDir` - User data (~/.local/share/b2c-dx-mcp)
-     * - `this.config.cacheDir` - Cache (~/.cache/b2c-dx-mcp)
+     * - `this.config.configDir` - User config (~/.config/b2c)
+     * - `this.config.dataDir` - User data (~/.local/share/b2c) - shared with b2c-cli for plugin discovery
+     * - `this.config.cacheDir` - Cache (~/.cache/b2c)
      * These can be exposed to Services if needed for features like telemetry or caching.
      */
     run(): Promise<void>;

package/dist/commands/mcp.js

@@ -55,7 +55,7 @@
  * | `--json` | - | Output logs as JSON lines |
  * | `--lang` | - | Language for messages |
  *
- * **Note on `--project-directory`**: Many MCP clients (Cursor, Claude Desktop) spawn servers from the
+ * **Note on `--project-directory`**: Many MCP clients (Cursor, Claude Code) spawn servers from the
  * user's home directory (`~`) rather than the project directory. This flag is used for:
  * - Auto-discovery (detecting project type when no `--toolsets` or `--tools` are provided)
  * - Scaffolding tools (creating files in the correct project location)
@@ -283,9 +283,9 @@ export default class McpServerCommand extends BaseCommand {
      * - `this.telemetry` - Telemetry instance (auto-initialized from package.json config)
      *
      * oclif provides standard config paths via `this.config`:
-     * - `this.config.configDir` - User config (~/.config/b2c-dx-mcp)
-     * - `this.config.dataDir` - User data (~/.local/share/b2c-dx-mcp)
-     * - `this.config.cacheDir` - Cache (~/.cache/b2c-dx-mcp)
+     * - `this.config.configDir` - User config (~/.config/b2c)
+     * - `this.config.dataDir` - User data (~/.local/share/b2c) - shared with b2c-cli for plugin discovery
+     * - `this.config.cacheDir` - Cache (~/.cache/b2c)
      * These can be exposed to Services if needed for features like telemetry or caching.
      */
     async run() {

package/dist/registry.js

@@ -100,7 +100,7 @@ async function performAutoDiscovery(flags, reason) {
     // 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. ' +
+            'MCP clients like Cursor and Claude Code often spawn servers from ~ instead of the project directory. ' +
             'Set --project-directory or SFCC_PROJECT_DIRECTORY for reliable auto-discovery.');
     }
     const detectionResult = await detectWorkspaceType(projectDirectory);

package/oclif.manifest.json

@@ -390,5 +390,5 @@
       "enableJsonFlag": false
     }
   },
-  "version": "0.4.9"
+  "version": "0.4.11"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/b2c-dx-mcp",
   "description": "MCP server for B2C Commerce developer experience tools",
-  "version": "0.4.9",
+  "version": "0.4.11",
   "author": "Salesforce",
   "license": "Apache-2.0",
   "repository": "SalesforceCommerceCloud/b2c-developer-tooling",
@@ -29,7 +29,7 @@
   },
   "oclif": {
     "bin": "b2c-dx-mcp",
-    "dirname": "b2c-dx-mcp",
+    "dirname": "b2c",
     "commands": {
       "strategy": "single",
       "target": "./dist/commands/mcp.js"
@@ -80,7 +80,7 @@
     "yaml": "2.8.1",
     "postcss": "8.5.6",
     "zod": "3.25.76",
-    "@salesforce/b2c-tooling-sdk": "0.8.0"
+    "@salesforce/b2c-tooling-sdk": "0.8.1"
   },
   "devDependencies": {
     "@eslint/compat": "^1",