From 9de2301ed734770a0eb33398f47cdf75529fec82 Mon Sep 17 00:00:00 2001 From: Yuming Hsieh Date: Tue, 24 Feb 2026 13:59:03 -0500 Subject: [PATCH 1/3] unregister placeholder tools and update readme --- .changeset/unregister-placeholder-tools.md | 9 ++ packages/b2c-dx-mcp/README.md | 33 ++--- packages/b2c-dx-mcp/package.json | 2 +- packages/b2c-dx-mcp/src/registry.ts | 2 +- packages/b2c-dx-mcp/src/tools/index.ts | 5 +- packages/b2c-dx-mcp/src/tools/pwav3/index.ts | 133 ++---------------- .../src/tools/storefrontnext/README.md | 12 -- .../src/tools/storefrontnext/index.ts | 100 +------------ packages/b2c-dx-mcp/test/registry.test.ts | 15 +- 9 files changed, 41 insertions(+), 270 deletions(-) create mode 100644 .changeset/unregister-placeholder-tools.md diff --git a/.changeset/unregister-placeholder-tools.md b/.changeset/unregister-placeholder-tools.md new file mode 100644 index 000000000..82d27fcc7 --- /dev/null +++ b/.changeset/unregister-placeholder-tools.md @@ -0,0 +1,9 @@ +--- +'@salesforce/b2c-dx-mcp': patch +--- + +Unregister placeholder tools and update README for preview release + +- Remove placeholder tools (PWA Kit, Storefront Next) so users only see implemented tools at startup +- Update README: preview release wording, accurate tool tables, credential notes, example prompts +- Fix package license to Apache-2.0 diff --git a/packages/b2c-dx-mcp/README.md b/packages/b2c-dx-mcp/README.md index b2edb7faf..900982d92 100644 --- a/packages/b2c-dx-mcp/README.md +++ b/packages/b2c-dx-mcp/README.md @@ -2,7 +2,7 @@ MCP (Model Context Protocol) server for Salesforce B2C Commerce Cloud 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. +> ⚠️ **Preview Release**: This package is in preview. Tools are functional but require `--allow-non-ga-tools` to enable. Additional tools will be added in future releases. ## Overview @@ -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:** +**Example prompts:** - ✅ "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:** +**Example prompts:** - ✅ "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:** +**Example prompts:** - ✅ "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:** +**Example prompts:** - ✅ "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." @@ -184,6 +184,8 @@ Credentials can be provided via **config files** (recommended), **environment va | **PWAV3** | `--working-directory` only (+ MRT config for deployments) | | **STOREFRONTNEXT** | `--working-directory` only (+ MRT/CARTRIDGES config for those tools) | +> **Note:** SCAPI and CARTRIDGES use the same `hostname` (your B2C instance). All B2C credentials are typically stored together in `dw.json`. + **Option 1: Config files (recommended)** B2C credentials — [`dw.json`](https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/configuration.html#configuration-file) in your project root: @@ -254,7 +256,7 @@ See [Flag Reference](#flag-reference) for all available flags and env vars. Use `--toolsets all` to enable all toolsets, or select specific ones with `--toolsets CARTRIDGES,MRT`. -> **Note:** All tools are currently placeholder implementations. Use `--allow-non-ga-tools` flag to enable them. +> **Note:** Tools require `--allow-non-ga-tools` to enable (preview release). #### CARTRIDGES Cartridge development, deployment, and code version management. @@ -274,17 +276,10 @@ Managed Runtime operations for PWA Kit and Storefront Next deployments. #### PWAV3 PWA Kit v3 development tools for building headless storefronts. -- **Status:** 🚧 Placeholder +- **Status:** 🚧 Early Access (PWA Kit-specific tools planned) | Tool | Description | |------|-------------| -| `pwakit_create_storefront` | Create a new PWA Kit storefront project | -| `pwakit_create_page` | Create a new page component in PWA Kit project | -| `pwakit_create_component` | Create a new React component in PWA Kit project | -| `pwakit_get_dev_guidelines` | Get PWA Kit development guidelines and best practices | -| `pwakit_recommend_hooks` | Recommend appropriate React hooks for PWA Kit use cases | -| `pwakit_run_site_test` | Run site tests for PWA Kit project | -| `pwakit_install_agent_rules` | Install AI agent rules for PWA Kit development | | `scapi_schemas_list` | List or fetch SCAPI schemas (standard and custom). Use apiFamily: "custom" for custom APIs. | | `scapi_custom_apis_status` | Get registration status of custom API endpoints (active/not_registered). Remote only, requires OAuth. | | `mrt_bundle_push` | Build, push bundle (optionally deploy) | @@ -297,21 +292,15 @@ Salesforce Commerce API discovery and exploration. |------|-------------| | `scapi_schemas_list` | List or fetch SCAPI schemas (standard and custom). Use apiFamily: "custom" for custom APIs. | | `scapi_custom_apis_status` | Get registration status of custom API endpoints (active/not_registered). Remote only, requires OAuth. | -| `scapi_customapi_scaffold` | Scaffold a new custom SCAPI API (not yet implemented) | #### STOREFRONTNEXT Storefront Next development tools for building modern storefronts. -- **Status:** 🚧 Placeholder +- **Status:** 🚧 Early Access | Tool | Description | |------|-------------| | `storefront_next_development_guidelines` | Get Storefront Next development guidelines and best practices | -| `storefront_next_site_theming` | Configure and manage site theming for Storefront Next | -| `storefront_next_figma_to_component_workflow` | Convert Figma designs to Storefront Next components | -| `storefront_next_generate_component` | Generate a new Storefront Next component | -| `storefront_next_map_tokens_to_theme` | Map design tokens to Storefront Next theme configuration | | `storefront_next_page_designer_decorator` | Add Page Designer decorators to Storefront Next components | -| `storefront_next_generate_page_designer_metadata` | Generate Page Designer metadata for Storefront Next components | | `scapi_schemas_list` | List or fetch SCAPI schemas (standard and custom). Use apiFamily: "custom" for custom APIs. | | `scapi_custom_apis_status` | Get registration status of custom API endpoints (active/not_registered). Remote only, requires OAuth. | | `mrt_bundle_push` | Build, push bundle (optionally deploy) | @@ -446,7 +435,7 @@ Configure your IDE to use the local MCP server. Add this to your IDE's MCP confi Send raw MCP protocol messages: ```bash -# List all tools (--allow-non-ga-tools required for placeholder tools) +# List all tools (--allow-non-ga-tools required for preview tools) echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | node bin/dev.js --toolsets all --allow-non-ga-tools # Call a specific tool diff --git a/packages/b2c-dx-mcp/package.json b/packages/b2c-dx-mcp/package.json index 4f1545656..1d7e7d353 100644 --- a/packages/b2c-dx-mcp/package.json +++ b/packages/b2c-dx-mcp/package.json @@ -3,7 +3,7 @@ "version": "0.4.1", "description": "MCP server for B2C Commerce Cloud developer experience tools", "author": "Salesforce", - "license": "MIT", + "license": "Apache-2.0", "repository": "SalesforceCommerceCloud/b2c-developer-tooling", "keywords": [ "salesforce", diff --git a/packages/b2c-dx-mcp/src/registry.ts b/packages/b2c-dx-mcp/src/registry.ts index 7d2be4fa6..cc27394e1 100644 --- a/packages/b2c-dx-mcp/src/registry.ts +++ b/packages/b2c-dx-mcp/src/registry.ts @@ -265,7 +265,7 @@ async function registerTools(tools: McpTool[], server: B2CDxMcpServer, allowNonG } // Register the tool - // TODO: Telemetry - Tool registration includes timing/error tracking + // Register the tool (invocations are tracked by B2CDxMcpServer) server.addTool(tool.name, tool.description, tool.inputSchema, async (args) => tool.handler(args)); } } diff --git a/packages/b2c-dx-mcp/src/tools/index.ts b/packages/b2c-dx-mcp/src/tools/index.ts index 630da6dc2..cdb142303 100644 --- a/packages/b2c-dx-mcp/src/tools/index.ts +++ b/packages/b2c-dx-mcp/src/tools/index.ts @@ -9,10 +9,7 @@ * * This module exports all available tools and utilities. * Tools use the @salesforce/b2c-tooling-sdk operations layer directly. - * - * > ⚠️ **PLACEHOLDER - ACTIVE DEVELOPMENT** - * > Tools are currently placeholder implementations that return mock responses. - * > Actual implementations are coming soon. Use `--allow-non-ga-tools` flag to enable. + * Use `--allow-non-ga-tools` flag to enable tools (preview release). * * @module tools */ diff --git a/packages/b2c-dx-mcp/src/tools/pwav3/index.ts b/packages/b2c-dx-mcp/src/tools/pwav3/index.ts index 39d0e04bd..991664b42 100644 --- a/packages/b2c-dx-mcp/src/tools/pwav3/index.ts +++ b/packages/b2c-dx-mcp/src/tools/pwav3/index.ts @@ -8,138 +8,25 @@ * PWA Kit v3 toolset for B2C Commerce. * * This toolset provides MCP tools for PWA Kit v3 development. - * - * > ⚠️ **PLACEHOLDER - ACTIVE DEVELOPMENT** - * > Tools in this module are placeholder implementations that return mock responses. - * > Actual implementations are coming soon. Use `--allow-non-ga-tools` flag to enable. + * PWA Kit-specific tools are planned for future releases. + * mrt_bundle_push (from MRT toolset) is available for PWAV3 projects. * * @module tools/pwav3 */ -import {z} from 'zod'; -import type {McpTool, Toolset} from '../../utils/index.js'; +import type {McpTool} from '../../utils/index.js'; import type {Services} from '../../services.js'; -import {createToolAdapter, jsonResult} from '../adapter.js'; - -/** - * Common input type for placeholder tools. - */ -interface PlaceholderInput { - message?: string; -} - -/** - * Common output type for placeholder tools. - */ -interface PlaceholderOutput { - tool: string; - status: string; - message: string; - input: PlaceholderInput; - timestamp: string; -} - -/** - * Creates a placeholder tool for PWA Kit development. - * - * Placeholder tools log invocations and return mock responses until - * the actual implementation is available. - * - * @param name - Tool name - * @param description - Tool description - * @param toolsets - Toolsets this tool belongs to - * @param loadServices - Function that loads configuration and returns Services instance - * @returns The configured MCP tool - */ -function createPlaceholderTool( - name: string, - description: string, - toolsets: Toolset[], - loadServices: () => Services, -): McpTool { - return createToolAdapter( - { - name, - description: `[PLACEHOLDER] ${description}`, - toolsets, - isGA: false, - requiresInstance: false, - inputSchema: { - message: z.string().optional().describe('Optional message to echo'), - }, - async execute(args) { - // Placeholder implementation - const timestamp = new Date().toISOString(); - - return { - tool: name, - status: 'placeholder', - message: `This is a placeholder implementation for '${name}'. The actual implementation is coming soon.`, - input: args, - timestamp, - }; - }, - formatOutput: (output) => jsonResult(output), - }, - loadServices, - ); -} /** * Creates all tools for the PWAV3 toolset. * - * Note: mrt_bundle_push is defined in the MRT toolset with - * toolsets: ["MRT", "PWAV3", "STOREFRONTNEXT"] and will - * automatically appear in PWAV3. + * PWA Kit-specific tools are not yet implemented. mrt_bundle_push is defined + * in the MRT toolset with toolsets: ["MRT", "PWAV3", "STOREFRONTNEXT"] and + * automatically appears in PWAV3 for bundle deployment. * - * @param loadServices - Function that loads configuration and returns Services instance - * @returns Array of MCP tools + * @param _loadServices - Function that loads configuration and returns Services instance + * @returns Array of MCP tools (empty until PWA Kit tools are implemented) */ -export function createPwav3Tools(loadServices: () => Services): McpTool[] { - return [ - // PWA Kit development tools - createPlaceholderTool( - 'pwakit_create_storefront', - 'Create a new PWA Kit storefront project', - ['PWAV3'], - loadServices, - ), - createPlaceholderTool( - 'pwakit_create_page', - 'Create a new page component in PWA Kit project', - ['PWAV3'], - loadServices, - ), - createPlaceholderTool( - 'pwakit_create_component', - 'Create a new React component in PWA Kit project', - ['PWAV3'], - loadServices, - ), - createPlaceholderTool( - 'pwakit_get_dev_guidelines', - 'Get PWA Kit development guidelines and best practices', - ['PWAV3'], - loadServices, - ), - createPlaceholderTool( - 'pwakit_recommend_hooks', - 'Recommend appropriate React hooks for PWA Kit use cases', - ['PWAV3'], - loadServices, - ), - createPlaceholderTool('pwakit_run_site_test', 'Run site tests for PWA Kit project', ['PWAV3'], loadServices), - createPlaceholderTool( - 'pwakit_install_agent_rules', - 'Install AI agent rules for PWA Kit development', - ['PWAV3'], - loadServices, - ), - createPlaceholderTool( - 'pwakit_explore_scapi_shop_api', - 'Explore SCAPI Shop API endpoints and capabilities', - ['PWAV3'], - loadServices, - ), - ]; +export function createPwav3Tools(_loadServices: () => Services): McpTool[] { + return []; } diff --git a/packages/b2c-dx-mcp/src/tools/storefrontnext/README.md b/packages/b2c-dx-mcp/src/tools/storefrontnext/README.md index cf45a994a..a13ac57b7 100644 --- a/packages/b2c-dx-mcp/src/tools/storefrontnext/README.md +++ b/packages/b2c-dx-mcp/src/tools/storefrontnext/README.md @@ -201,15 +201,3 @@ The tool automatically searches for components in these locations (in order): Component discovery uses the working directory resolved from `--working-directory` flag or `SFCC_WORKING_DIRECTORY` environment variable (via Services). This ensures searches start from the correct project directory, especially when MCP clients spawn servers from the home directory. **See also**: [Detailed documentation](./page-designer-decorator/README.md) for complete usage guide, architecture details, and examples. - -## Placeholder Tools - -The following tools are placeholders awaiting implementation: - -- `storefront_next_site_theming` - Configure and manage site theming for Storefront Next -- `storefront_next_figma_to_component_workflow` - Convert Figma designs to Storefront Next components -- `storefront_next_generate_component` - Generate a new Storefront Next component -- `storefront_next_map_tokens_to_theme` - Map design tokens to Storefront Next theme configuration -- `storefront_next_generate_page_designer_metadata` - Generate Page Designer metadata for Storefront Next components - -Use `--allow-non-ga-tools` flag to enable placeholder tools. diff --git a/packages/b2c-dx-mcp/src/tools/storefrontnext/index.ts b/packages/b2c-dx-mcp/src/tools/storefrontnext/index.ts index f60bb2d98..4b72d3969 100644 --- a/packages/b2c-dx-mcp/src/tools/storefrontnext/index.ts +++ b/packages/b2c-dx-mcp/src/tools/storefrontnext/index.ts @@ -10,83 +10,19 @@ * This toolset provides MCP tools for Storefront Next development. * * **Implemented Tools:** - * - `storefront_next_development_guidelines` - Get development guidelines and best practices (GA) + * - `storefront_next_development_guidelines` - Get development guidelines and best practices + * - `storefront_next_page_designer_decorator` - Add Page Designer decorators to React components * - * **Placeholder Tools (Use `--allow-non-ga-tools` flag to enable):** - * - `storefront_next_site_theming` - Configure site theming - * - `storefront_next_figma_to_component_workflow` - Convert Figma to components - * - `storefront_next_generate_component` - Generate new components - * - `storefront_next_map_tokens_to_theme` - Map design tokens - * - `storefront_next_generate_page_designer_metadata` - Generate Page Designer metadata + * Note: mrt_bundle_push is defined in the MRT toolset and appears in STOREFRONTNEXT. * * @module tools/storefrontnext */ -import {z} from 'zod'; import type {McpTool} from '../../utils/index.js'; import type {Services} from '../../services.js'; -import {createToolAdapter, jsonResult} from '../adapter.js'; import {createDeveloperGuidelinesTool} from './developer-guidelines.js'; import {createPageDesignerDecoratorTool} from './page-designer-decorator/index.js'; -/** - * Common input type for placeholder tools. - */ -interface PlaceholderInput { - message?: string; -} - -/** - * Common output type for placeholder tools. - */ -interface PlaceholderOutput { - tool: string; - status: string; - message: string; - input: PlaceholderInput; - timestamp: string; -} - -/** - * Creates a placeholder tool for Storefront Next development. - * - * Placeholder tools log invocations and return mock responses until - * the actual implementation is available. - * - * @param name - Tool name - * @param description - Tool description - * @param loadServices - Function that loads configuration and returns Services instance - * @returns The configured MCP tool - */ -function createPlaceholderTool(name: string, description: string, loadServices: () => Services): McpTool { - return createToolAdapter( - { - name, - description: `[PLACEHOLDER] ${description}`, - toolsets: ['STOREFRONTNEXT'], - isGA: false, - requiresInstance: false, - inputSchema: { - message: z.string().optional().describe('Optional message to echo'), - }, - async execute(args) { - // Placeholder implementation - const timestamp = new Date().toISOString(); - - return { - tool: name, - status: 'placeholder', - message: `This is a placeholder implementation for '${name}'. The actual implementation is coming soon.`, - input: args, - timestamp, - }; - }, - formatOutput: (output) => jsonResult(output), - }, - loadServices, - ); -} - /** * Creates all tools for the STOREFRONTNEXT toolset. * @@ -98,33 +34,5 @@ function createPlaceholderTool(name: string, description: string, loadServices: * @returns Array of MCP tools */ export function createStorefrontNextTools(loadServices: () => Services): McpTool[] { - return [ - createDeveloperGuidelinesTool(loadServices), - createPageDesignerDecoratorTool(loadServices), - createPlaceholderTool( - 'storefront_next_site_theming', - 'Configure and manage site theming for Storefront Next', - loadServices, - ), - createPlaceholderTool( - 'storefront_next_figma_to_component_workflow', - 'Convert Figma designs to Storefront Next components', - loadServices, - ), - createPlaceholderTool( - 'storefront_next_generate_component', - 'Generate a new Storefront Next component', - loadServices, - ), - createPlaceholderTool( - 'storefront_next_map_tokens_to_theme', - 'Map design tokens to Storefront Next theme configuration', - loadServices, - ), - createPlaceholderTool( - 'storefront_next_generate_page_designer_metadata', - 'Generate Page Designer metadata for Storefront Next components', - loadServices, - ), - ]; + return [createDeveloperGuidelinesTool(loadServices), createPageDesignerDecoratorTool(loadServices)]; } diff --git a/packages/b2c-dx-mcp/test/registry.test.ts b/packages/b2c-dx-mcp/test/registry.test.ts index a8c41fb18..1a0c33feb 100644 --- a/packages/b2c-dx-mcp/test/registry.test.ts +++ b/packages/b2c-dx-mcp/test/registry.test.ts @@ -71,13 +71,8 @@ describe('registry', () => { const registry = createToolRegistry(loadServices); expect(registry.PWAV3).to.be.an('array'); - expect(registry.PWAV3.length).to.be.greaterThan(0); - + // mrt_bundle_push appears in PWAV3 (multi-toolset); PWA Kit-specific tools not yet implemented const toolNames = registry.PWAV3.map((t) => t.name); - expect(toolNames).to.include('pwakit_create_storefront'); - expect(toolNames).to.include('pwakit_create_page'); - expect(toolNames).to.include('pwakit_create_component'); - // mrt_bundle_push should also appear in PWAV3 (multi-toolset) expect(toolNames).to.include('mrt_bundle_push'); }); @@ -102,8 +97,7 @@ describe('registry', () => { const toolNames = registry.STOREFRONTNEXT.map((t) => t.name); expect(toolNames).to.include('storefront_next_development_guidelines'); - expect(toolNames).to.include('storefront_next_site_theming'); - expect(toolNames).to.include('storefront_next_generate_component'); + expect(toolNames).to.include('storefront_next_page_designer_decorator'); // mrt_bundle_push should also appear in STOREFRONTNEXT (multi-toolset) expect(toolNames).to.include('mrt_bundle_push'); }); @@ -192,7 +186,7 @@ describe('registry', () => { expect(server.registeredTools).to.include('cartridge_deploy'); // Should include MRT tools expect(server.registeredTools).to.include('mrt_bundle_push'); - // Should not include PWAV3-only tools + // Should not include PWAV3-only tools (placeholder tools removed) expect(server.registeredTools).to.not.include('pwakit_create_storefront'); }); @@ -206,10 +200,9 @@ describe('registry', () => { const loadServices = createMockLoadServicesWrapper(); await registerToolsets(flags, server, loadServices); - // Should include tools from all toolsets + // Should include tools from all toolsets (placeholder tools removed) expect(server.registeredTools).to.include('cartridge_deploy'); expect(server.registeredTools).to.include('mrt_bundle_push'); - expect(server.registeredTools).to.include('pwakit_create_storefront'); expect(server.registeredTools).to.include('scapi_schemas_list'); expect(server.registeredTools).to.include('storefront_next_development_guidelines'); }); From ef3e89e00902ffd002f7a976c82d0386d2156af6 Mon Sep 17 00:00:00 2001 From: Yuming Hsieh Date: Tue, 24 Feb 2026 16:39:48 -0500 Subject: [PATCH 2/3] update mcp docs --- docs/mcp/index.md | 2 +- docs/mcp/toolsets.md | 19 +++---------------- 2 files changed, 4 insertions(+), 17 deletions(-) diff --git a/docs/mcp/index.md b/docs/mcp/index.md index 3cadd05d3..2ab025f70 100644 --- a/docs/mcp/index.md +++ b/docs/mcp/index.md @@ -6,7 +6,7 @@ description: MCP Server for Salesforce B2C Commerce - AI-assisted development to The B2C DX MCP Server enables AI assistants (like Cursor, Claude Desktop, and others) to help with B2C Commerce development tasks. It provides toolsets for **SCAPI**, **CARTRIDGES**, **MRT**, **PWAV3**, and **STOREFRONTNEXT** development. -> ⚠️ **Active Development**: This package is under active development. Some tools are currently **placeholder implementations** that return mock responses. Tool implementations will be added incrementally. +> ⚠️ **Preview Release**: This package is in preview. Tools are functional but require `--allow-non-ga-tools` to enable. Additional tools will be added in future releases. ## Overview diff --git a/docs/mcp/toolsets.md b/docs/mcp/toolsets.md index b7b20a7ed..9a12fe3f5 100644 --- a/docs/mcp/toolsets.md +++ b/docs/mcp/toolsets.md @@ -6,7 +6,7 @@ description: Available toolsets and tools in the B2C DX MCP Server for SCAPI, CA The B2C DX MCP Server provides five toolsets with specialized tools for different B2C Commerce development workflows. -> **Note:** Some tools are currently placeholder or early release implementations. Use `--allow-non-ga-tools` flag to enable them. +> **Note:** Tools require `--allow-non-ga-tools` to enable (preview release). ## Overview @@ -53,7 +53,7 @@ Managed Runtime operations for PWA Kit and Storefront Next deployments. PWA Kit v3 development tools for building headless storefronts. -**Status:** 🚧 Placeholder +**Status:** 🚧 Early Access (PWA Kit-specific tools planned) **Auto-enabled for:** PWA Kit v3 projects (detected by `@salesforce/pwa-kit-*` dependencies) @@ -61,13 +61,6 @@ PWA Kit v3 development tools for building headless storefronts. | Tool | Description | Documentation | |------|-------------|---------------| -| `pwakit_create_storefront` | Create a new PWA Kit storefront project | — | -| `pwakit_create_page` | Create a new page component in the PWA Kit project | — | -| `pwakit_create_component` | Create a React component in the PWA Kit project | — | -| `pwakit_get_dev_guidelines` | Get PWA Kit development guidelines and best practices | — | -| `pwakit_recommend_hooks` | Recommend appropriate React hooks for PWA Kit use cases | — | -| `pwakit_run_site_test` | Run site tests for PWA Kit project | — | -| `pwakit_install_agent_rules` | Install AI agent rules for PWA Kit development | — | | [`scapi_schemas_list`](./tools/scapi-schemas-list) | List or fetch SCAPI schemas (standard and custom). Use apiFamily: "custom" for custom APIs. | [View details](./tools/scapi-schemas-list) | | [`scapi_custom_apis_status`](./tools/scapi-custom-apis-status) | Get registration status of custom API endpoints (active/not_registered). Remote only, requires OAuth. | [View details](./tools/scapi-custom-apis-status) | | [`mrt_bundle_push`](./tools/mrt-bundle-push) | Build, push bundle (optionally deploy) | [View details](./tools/mrt-bundle-push) | @@ -86,13 +79,12 @@ Salesforce Commerce API discovery and exploration. |------|-------------|---------------| | [`scapi_schemas_list`](./tools/scapi-schemas-list) | List or fetch SCAPI schemas (standard and custom). Use apiFamily: "custom" for custom APIs. | [View details](./tools/scapi-schemas-list) | | [`scapi_custom_apis_status`](./tools/scapi-custom-apis-status) | Get registration status of custom API endpoints (active/not_registered). Remote only, requires OAuth. | [View details](./tools/scapi-custom-apis-status) | -| `scapi_customapi_scaffold` | Scaffold a new custom SCAPI API (not yet implemented) | — | ## STOREFRONTNEXT Storefront Next development tools for building modern storefronts. -**Status:** 🚧 Placeholder +**Status:** 🚧 Early Access **Auto-enabled for:** Storefront Next projects (detected by `@salesforce/storefront-next*` dependencies) @@ -101,12 +93,7 @@ Storefront Next development tools for building modern storefronts. | Tool | Description | Documentation | |------|-------------|---------------| | `storefront_next_development_guidelines` | Get Storefront Next development guidelines and best practices | — | -| `storefront_next_site_theming` | Configure and manage site theming for Storefront Next | — | -| `storefront_next_figma_to_component_workflow` | Convert Figma designs to Storefront Next components | — | -| `storefront_next_generate_component` | Generate a new Storefront Next component | — | -| `storefront_next_map_tokens_to_theme` | Map design tokens to Storefront Next theme configuration | — | | [`storefront_next_page_designer_decorator`](./tools/storefront-next-page-designer-decorator) | Add Page Designer decorators to Storefront Next components | [View details](./tools/storefront-next-page-designer-decorator) | -| `storefront_next_generate_page_designer_metadata` | Generate Page Designer metadata for Storefront Next components | — | | [`scapi_schemas_list`](./tools/scapi-schemas-list) | List or fetch SCAPI schemas (standard and custom). Use apiFamily: "custom" for custom APIs. | [View details](./tools/scapi-schemas-list) | | [`scapi_custom_apis_status`](./tools/scapi-custom-apis-status) | Get registration status of custom API endpoints (active/not_registered). Remote only, requires OAuth. | [View details](./tools/scapi-custom-apis-status) | | [`mrt_bundle_push`](./tools/mrt-bundle-push) | Build, push bundle (optionally deploy) | [View details](./tools/mrt-bundle-push) | From e2eba7a307c9cc1e97fb4b3782b50be057cbead2 Mon Sep 17 00:00:00 2001 From: Yuming Hsieh Date: Wed, 25 Feb 2026 06:22:25 -0500 Subject: [PATCH 3/3] add docs/mcp changeset --- .changeset/docs-mcp-preview-update.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 .changeset/docs-mcp-preview-update.md diff --git a/.changeset/docs-mcp-preview-update.md b/.changeset/docs-mcp-preview-update.md new file mode 100644 index 000000000..bfc6f0fc3 --- /dev/null +++ b/.changeset/docs-mcp-preview-update.md @@ -0,0 +1,5 @@ +--- +'@salesforce/b2c-dx-docs': patch +--- + +MCP docs: preview release wording, sidebar nav, remove placeholder tool references