Salesforce B2C Commerce 개발 운영 및 Agent Skills 관리를 위한 CLI, SDK, MCP server를 제공합니다.
다른 이름 SalesforceCommerceCloud/b2c-developer-tooling, @salesforce/b2c-dx-mcp
- 스타
- 58
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 11월 14일
- 라이선스
- Apache-2.0
Salesforce B2C Commerce Tooling MCP란?
Salesforce B2C Commerce 개발 운영 및 Agent Skills 관리를 위한 CLI, SDK, MCP server를 제공합니다.
프로젝트 README에서 생성된 요약
Salesforce B2C Commerce Tooling MCP server 정보
이 툴킷은 개발자가 command line interface, 전용 SDK, MCP server를 통해 Salesforce B2C Commerce 운영을 관리할 수 있는 도구 모음을 제공합니다. AI 기반 에디터 및 통합 개발 환경에서 작업하는 엔지니어를 위해 설계되었습니다. 이 패키지에는 명령줄 작업을 위한 b2c-cli, 독립 라이브러리용 b2c-tooling-sdk, 그리고 Claude Code 사용자를 위한 b2c-dx-mcp server가 포함되어 있습니다.
사용자는 Claude Code, GitHub Copilot을 통한 VS Code, Cursor, Gemini CLI 등 다양한 워크플로우에 이러한 기능을 통합할 수 있습니다. 설정 시 특정 플러그인을 설치하거나 npx 명령어를 사용하여 agent skills를 활성화합니다. 시스템은 B2C 인스턴스와 상호 작용하기 위해 OAuth, API Key, Basic과 같은 다양한 인증 전략을 지원합니다. 또한 검증 및 문서 검색을 지원하기 위해 Script API 참조 및 XML schema와 같은 플랫폼 데이터가 함께 제공됩니다.
활용 사례
- 1채팅 내 CLI 작업 자동화개발자는 b2c-cli 플러그인을 사용하여 AI 채팅 인터페이스 내에서 직접 명령줄 작업을 실행할 수 있습니다.
- 2Schema 기반 XML 검증개발자는 MCP server를 사용하여 XML 파일이 특정 B2C Commerce XSD schema를 준수하는지 확인할 수 있습니다.
- 3플랫폼 문서 검색AI agent는 내장된 검색 도구를 사용하여 Script API 또는 job step 문서에서 특정 정보를 검색할 수 있습니다.
- 4커스텀 앱에 B2C 로직 통합소프트웨어 엔지니어는 독립형 SDK를 사용하여 B2C Commerce 인스턴스 관리를 위한 커스텀 도구를 구축할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Salesforce B2C Commerce Tooling MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Salesforce B2C Commerce Tooling MCP 설치
$ claude mcp add b2c-developer-tooling -- npx -y @salesforce/b2c-dx-mcpCursor에 Salesforce B2C Commerce Tooling MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"b2c-developer-tooling": {
"command": "npx",
"args": [
"-y",
"@salesforce/b2c-dx-mcp"
]
}
}
}VS Code에 Salesforce B2C Commerce Tooling MCP 설치
.vscode/mcp.json
{
"servers": {
"b2c-developer-tooling": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@salesforce/b2c-dx-mcp"
]
}
}
}VS Code CLI에 Salesforce B2C Commerce Tooling MCP 설치
$ code --add-mcp '{"name":"b2c-developer-tooling","type":"stdio","command":"npx","args":["-y","@salesforce/b2c-dx-mcp"]}'Claude Desktop에 Salesforce B2C Commerce Tooling MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"b2c-developer-tooling": {
"command": "npx",
"args": [
"-y",
"@salesforce/b2c-dx-mcp"
]
}
}
}Codex에 Salesforce B2C Commerce Tooling MCP 설치
$ codex mcp add b2c-developer-tooling -- npx -y @salesforce/b2c-dx-mcpCodex config.toml에 Salesforce B2C Commerce Tooling MCP 설치
~/.codex/config.toml
[mcp_servers.b2c-developer-tooling] command = "npx" args = ["-y", "@salesforce/b2c-dx-mcp"]
Gemini CLI에 Salesforce B2C Commerce Tooling MCP 설치
$ gemini mcp add -s user b2c-developer-tooling npx -- -y @salesforce/b2c-dx-mcpGemini settings.json에 Salesforce B2C Commerce Tooling MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"b2c-developer-tooling": {
"command": "npx",
"args": [
"-y",
"@salesforce/b2c-dx-mcp"
]
}
}
}구성
B2C_INSTANCE
| 이름 | 설명 | 유형 |
|---|---|---|
| B2C_INSTANCE | — |
자동 검사
2026년 11월 12일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음통과
- 원격 엔드포인트가 HTTPS 사용검사되지 않음
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
README
GitHub에서 보기B2C 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.
Salesforce B2C Commerce Tooling MCP 질문
Salesforce B2C Commerce Tooling MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add b2c-developer-tooling -- npx -y @salesforce/b2c-dx-mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Salesforce B2C Commerce Tooling MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Claude Code에서 B2C Commerce agent skills를 어떻게 설치하나요?
채팅창에서 다음 명령어를 실행하여 설치할 수 있습니다: /plugin install b2c-cli@b2c-developer-tooling, /plugin install b2c@b2c-developer-tooling, /plugin install b2c-dx-mcp@b2c-developer-tooling.
이 monorepo에는 어떤 패키지들이 포함되어 있나요?
이 프로젝트에는 b2c-cli (command line interface), b2c-tooling-sdk (B2C Commerce 운영용 SDK), b2c-dx-mcp (개발자 경험 도구용 MCP server)가 포함되어 있습니다.
SDK는 어떤 인증 전략을 지원하나요?
SDK는 OAuth, API Key, Basic 인증 전략을 지원합니다.