Proporciona una interfaz de línea de comandos, un SDK y un MCP server para gestionar las operaciones de desarrollo de Salesforce B2C Commerce y Agent Skills.
También conocido como SalesforceCommerceCloud/b2c-developer-tooling, @salesforce/b2c-dx-mcp
- Stars
- 58
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- —
- Último commit
- 14 nov 2026
- Licencia
- Apache-2.0
¿Qué es Salesforce B2C Commerce Tooling MCP?
Proporciona una interfaz de línea de comandos, un SDK y un MCP server para gestionar las operaciones de desarrollo de Salesforce B2C Commerce y Agent Skills.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Salesforce B2C Commerce Tooling
Este toolkit ofrece a los desarrolladores un conjunto de herramientas para gestionar las operaciones de Salesforce B2C Commerce mediante una interfaz de línea de comandos, un SDK dedicado y un MCP server. Está diseñado para ingenieros que trabajan con editores potenciados por IA y entornos de desarrollo integrados. El paquete incluye b2c-cli para operaciones por línea de comandos, b2c-tooling-sdk para uso como librería independiente y el servidor b2c-dx-mcp específicamente para usuarios de Claude Code.
Los usuarios pueden integrar estas capacidades en diversos flujos de trabajo, incluyendo Claude Code, VS Code a través de GitHub Copilot, Cursor y Gemini CLI. La configuración implica la instalación de plugins específicos o el uso de comandos npx para habilitar las agent skills. El sistema admite múltiples estrategias de autenticación como OAuth, API Key y Basic para interactuar con instancias de B2C. También incluye datos de plataforma integrados, como referencias de la Script API y esquemas XML, para ayudar con la validación y la búsqueda de documentación.
Qué puedes hacer con él
- 1Automatizar operaciones de CLI en el chatUn desarrollador puede usar el plugin b2c-cli para ejecutar operaciones de línea de comandos directamente dentro de una interfaz de chat de IA.
- 2Validar XML contra esquemasLos desarrolladores pueden usar el MCP server para verificar que los archivos XML cumplan con los esquemas XSD específicos de B2C Commerce.
- 3Buscar documentación de la plataformaUn agente de IA puede recuperar información específica de la Script API o de la documentación de los pasos de trabajo (job steps) utilizando las herramientas de búsqueda integradas.
- 4Integrar lógica de B2C en aplicaciones personalizadasLos ingenieros de software pueden usar el SDK independiente para construir herramientas personalizadas para la gestión de instancias de B2C Commerce.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Salesforce B2C Commerce Tooling MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Salesforce B2C Commerce Tooling MCP en Claude Code
$ claude mcp add b2c-developer-tooling -- npx -y @salesforce/b2c-dx-mcpInstalar Salesforce B2C Commerce Tooling MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"b2c-developer-tooling": {
"command": "npx",
"args": [
"-y",
"@salesforce/b2c-dx-mcp"
]
}
}
}Instalar Salesforce B2C Commerce Tooling MCP en VS Code
.vscode/mcp.json
{
"servers": {
"b2c-developer-tooling": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@salesforce/b2c-dx-mcp"
]
}
}
}Instalar Salesforce B2C Commerce Tooling MCP en VS Code CLI
$ code --add-mcp '{"name":"b2c-developer-tooling","type":"stdio","command":"npx","args":["-y","@salesforce/b2c-dx-mcp"]}'Instalar Salesforce B2C Commerce Tooling MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"b2c-developer-tooling": {
"command": "npx",
"args": [
"-y",
"@salesforce/b2c-dx-mcp"
]
}
}
}Instalar Salesforce B2C Commerce Tooling MCP en Codex
$ codex mcp add b2c-developer-tooling -- npx -y @salesforce/b2c-dx-mcpInstalar Salesforce B2C Commerce Tooling MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.b2c-developer-tooling] command = "npx" args = ["-y", "@salesforce/b2c-dx-mcp"]
Instalar Salesforce B2C Commerce Tooling MCP en Gemini CLI
$ gemini mcp add -s user b2c-developer-tooling npx -- -y @salesforce/b2c-dx-mcpInstalar Salesforce B2C Commerce Tooling MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"b2c-developer-tooling": {
"command": "npx",
"args": [
"-y",
"@salesforce/b2c-dx-mcp"
]
}
}
}Configuración
B2C_INSTANCE
| Nombre | Descripción | Tipo |
|---|---|---|
| B2C_INSTANCE | — |
Verificaciones automáticas
Ejecutado 12 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesibleAprobado
- Licencia de código abierto (OSI)Aprobado
- Commit o lanzamiento en el último añoAprobado
- El nombre del paquete no es similar a un paquete popularAprobado
- El endpoint remoto usa HTTPSNo verificado
- Las herramientas destructivas están etiquetadasNo verificado
- Sin instrucciones ocultas para el modeloAprobado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
README
Ver en GitHubB2C CLI, MCP and Tooling SDK
[!NOTE] This project is Generally Available (GA). Please provide feedback via GitHub issues.
Salesforce B2C Commerce Command Line Tools.
[!TIP] Just looking for the B2C CLI or MCP install instructions? Visit the documentation site at https://salesforcecommercecloud.github.io/b2c-developer-tooling/ for the latest install guide and CLI reference.
Agent Skills & Plugins
Install B2C Commerce agent skills and plugins in your AI-powered editor. Three plugins are available: b2c-cli (CLI operations), b2c (development patterns), and b2c-dx-mcp (MCP server — Claude Code only).
-
Claude Code: run these commands in chat:
/plugin marketplace add SalesforceCommerceCloud/b2c-developer-tooling /plugin install b2c-cli@b2c-developer-tooling /plugin install b2c@b2c-developer-tooling /plugin install b2c-dx-mcp@b2c-developer-toolingClaude Code does not auto-update third-party marketplaces by default. To get new releases automatically, run
/pluginagain, open Marketplaces, selectb2c-developer-tooling, and choose Enable auto-update. -
VS Code (GitHub Copilot): Command Palette (
Cmd+Shift+P/Ctrl+Shift+P) → Chat: Install Plugin From Source → enter the repoSalesforceCommerceCloud/b2c-developer-tooling. -
GitHub Copilot CLI:
copilot plugin marketplace add SalesforceCommerceCloud/b2c-developer-tooling copilot plugin install b2c-cli@b2c-developer-tooling copilot plugin install b2c@b2c-developer-tooling -
Cursor: add the marketplace from this repo URL in Cursor Settings → Plugins, then install
b2c-cli/b2c. -
Codex CLI: run
/pluginsand add from this repo (GitHub URL). -
Gemini CLI:
gemini extensions install https://github.com/SalesforceCommerceCloud/b2c-developer-tooling -
Any supported IDE (file-copy install via CLI):
npx @salesforce/b2c-cli setup skills
For Windsurf, OpenCode, Agentforce Vibes, manual installs, and the full install matrix, see docs/guide/agent-skills.
Packages
This is a pnpm monorepo with the following packages:
| Package | Description |
|---|---|
b2c-cli |
Command line interface built with oclif |
b2c-tooling-sdk |
SDK/library for B2C Commerce operations; supports the CLI and can be used standalone |
b2c-dx-mcp |
MCP server for B2C Commerce developer experience tools |
Development
Prerequisites
- Node.js >= 22.16.0
- pnpm 10.17.1+
Setup
pnpm install
Running the CLI in Development Mode
pnpm start
# or directly:
pnpm --filter @salesforce/b2c-cli run dev
# or using convenience script:
./cli
The dev mode uses Node.js --conditions=development to resolve TypeScript source files directly from @salesforce/b2c-tooling-sdk without needing to build first.
Building
# Build all packages
pnpm -r run build
# Build individual packages
pnpm --filter @salesforce/b2c-cli run build
pnpm --filter @salesforce/b2c-tooling-sdk run build
Testing
Tests use Mocha + Chai with c8 for coverage. HTTP mocking uses MSW.
# Run all tests with coverage (also runs linter after tests)
pnpm test
# Run tests for a specific package
pnpm --filter @salesforce/b2c-tooling-sdk run test
# Run tests without coverage (faster)
pnpm --filter @salesforce/b2c-tooling-sdk run test:unit
# Watch mode for TDD
pnpm --filter @salesforce/b2c-tooling-sdk run test:watch
# Run a specific test file
cd packages/b2c-tooling-sdk
pnpm mocha "test/clients/webdav.test.ts"
# Run tests matching a pattern
pnpm mocha --grep "uploads a file" "test/**/*.test.ts"
Coverage
Coverage reports are generated in each package's coverage/ directory:
coverage/index.html- HTML reportcoverage/lcov.info- LCOV format for CI integration
The SDK package has a 5% coverage threshold that will fail the build if not met.
Linting
# Run linter only
pnpm --filter @salesforce/b2c-cli run lint
pnpm --filter @salesforce/b2c-tooling-sdk run lint
Code Formatting
This project uses Prettier for code formatting.
# Format all packages
pnpm -r run format
# Check formatting without modifying files
pnpm -r run format:check
Documentation
Documentation is built using TypeDoc for API reference generation and VitePress for the documentation site.
Structure
docs/- VitePress documentation sourceguide/- User guide and getting startedcli/- CLI command referenceapi/- Generated API documentation (do not edit manually)
typedoc.json- TypeDoc configuration with entry points for SDK modules
Development Server
pnpm run docs:dev
This runs typedoc to generate API docs, then starts VitePress in development mode with hot reload.
Building Documentation
pnpm run docs:build
Previewing Built Documentation
pnpm run docs:preview
Deployed Documentation
The documentation site serves two versions:
- Stable (root URL) — built from the most recent release tag, updated on every stable release
- Dev (
/dev/) — built from themainbranch, updated on every push tomain
Doc-only releases (without bumping CLI/SDK/MCP versions) are possible by creating a changeset targeting @salesforce/b2c-dx-docs. See PUBLISHING.md for details.
API Documentation
API documentation is auto-generated from JSDoc comments in the @salesforce/b2c-tooling-sdk package. The entry points are defined in typedoc.json:
See the documentation site for the generated API reference.
auth- Authentication strategies (OAuth, API Key, Basic)instance- B2C instance configurationplatform- MRT and ODS clientsoperations/code- Cartridge code operationsoperations/jobs- Job executionoperations/sites- Site managementi18n- Internationalization utilitieslogging- Structured logging
When adding new public APIs, ensure they have comprehensive JSDoc comments as these will appear in the generated documentation.
Bundled Platform Data (Script API docs, schemas, job steps)
The SDK ships several corpora derived from the B2C Commerce platform under packages/b2c-tooling-sdk/data/:
| Directory | Contents | Consumed by |
|---|---|---|
script-api/ |
Script API reference markdown + search index | b2c docs search / docs read, MCP docs_* |
content-schemas/ |
Page Designer / content metadefinition JSON schemas | b2c content validate |
xsd/ |
Import/export XSD schemas + search index | b2c docs schema *, b2c validate, MCP validate_xml_schema |
xml-validator/ |
libxml2 compiled to WebAssembly; built by wasm/xml-validator/build.sh and verified in CI |
b2c validate, MCP validate_xml_schema |
job-steps/ |
Standard job-step markdown + dataset + search index | b2c docs search / docs read |
All of these originate from the same documentation archive that b2c docs download fetches from an instance (the inner DWAPP-<version>-API-doc.zip). To refresh all of them to a new platform release at once, run the maintainer script against a current instance (it uses your default instance/auth via the CLI):
# Refresh every data set and regenerate the derived indexes
pnpm --filter @salesforce/b2c-tooling-sdk run refresh:docs-data
# Target a non-default instance, or keep the temp workdir for inspection
B2C_INSTANCE=my-sandbox KEEP_WORKDIR=1 pnpm --filter @salesforce/b2c-tooling-sdk run refresh:docs-data
The script prints the detected platform version (e.g. DWAPP 26.7). Afterward, review the diff under packages/b2c-tooling-sdk/data/ (index files always change their generatedAt timestamp; look for substantive schema/doc changes), run pnpm --filter @salesforce/b2c-tooling-sdk run test:agent, and add a changeset if the refresh changes user-facing behavior. See the sdk-module-development skill for details.
Releases and Publishing
This project uses Changesets for version management and publishes to npm using OIDC trusted publishers.
| Release Type | npm Tag | Trigger |
|---|---|---|
| Stable | @latest |
Merge version PR on main |
| Release Branch | @latest or @release-X.Y |
Push to release/** branch |
| Nightly | @nightly |
Manual |
For detailed information about the release process, including release branches, see PUBLISHING.md.
Quick Reference
# Create a changeset for your changes
pnpm changeset
# Check pending changesets
pnpm changeset status
Preview Releases
Preview releases are available as tgz files on GitHub Releases for testing before npm publication.
Package Exports
The @salesforce/b2c-tooling-sdk package uses the exports field in package.json to define its public API surface. Each module is available as a subpath export:
import {OAuthStrategy} from '@salesforce/b2c-tooling-sdk/auth';
import {B2CInstance} from '@salesforce/b2c-tooling-sdk/instance';
import {getLogger} from '@salesforce/b2c-tooling-sdk/logging';
The development condition in exports enables direct TypeScript source resolution when using --conditions=development, which is how bin/dev.js works for local development.
Contributing
We welcome contributions! Please see our Contributing Guide for details on how to get started, submit pull requests, and our code of conduct.
Third-Party Dependency Review
To prevent net-new third-party libraries from being added without discussion, PRs are checked by the 3PL Guard workflow (Net-new 3PL check).
- The check compares changed
package.jsonfiles in the PR and detects net-new external dependencies. - If net-new dependencies are found, the PR is labeled
needs-3pl-reviewand the check fails. - After discussion and approval, a maintainer adds the
3pl-approvedlabel to allow the check to pass. - If the net-new dependency is removed,
needs-3pl-reviewis removed automatically.
To enforce this as a merge gate, keep Net-new 3PL check as a required status check in branch protection.
Security
For security concerns, please review our Security Policy. Report any security issues to security@salesforce.com.
License
This project is licensed under the Apache License 2.0. See LICENSE.txt for full details.
Disclaimer
This project is provided "as-is" without warranty of any kind. While the CLI, SDK, and MCP server are Generally Available, the VS Code extension is currently in Developer Preview — see its documentation for details. Breaking changes to any component will follow a documented deprecation cycle.
Preguntas sobre Salesforce B2C Commerce Tooling MCP
¿Cómo agrego Salesforce B2C Commerce Tooling MCP a Claude Code?
Ejecuta claude mcp add b2c-developer-tooling -- npx -y @salesforce/b2c-dx-mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Salesforce B2C Commerce Tooling MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Cómo instalo las B2C Commerce agent skills en Claude Code?
Puedes instalarlas ejecutando los siguientes comandos en el chat: /plugin install b2c-cli@b2c-developer-tooling, /plugin install b2c@b2c-developer-tooling, y /plugin install b2c-dx-mcp@b2c-developer-tooling.
¿Qué paquetes están incluidos en este monorepo?
El proyecto incluye b2c-cli (una interfaz de línea de comandos), b2c-tooling-sdk (un SDK para operaciones de B2C Commerce) y b2c-dx-mcp (un MCP server para herramientas de experiencia de desarrollador).
¿Qué estrategias de autenticación soporta el SDK?
El SDK soporta estrategias de autenticación OAuth, API Key y Basic.