sfcc-dev-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 5 of 5 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y sfcc-dev-mcp@1.1.0
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
5 tools that take no input and look read-only were called once with nothing. 5 returned a result.
list_sfcc_classes | Returned a result 0.1 s · 13,726 characters |
get_available_sfra_documents | Returned a result under 0.1 s · 9,128 characters |
get_sfra_categories | Returned a result under 0.1 s · 967 characters |
list_isml_elements | Returned a result under 0.1 s · 14,126 characters |
get_isml_categories | Returned a result under 0.1 s · 1,531 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
1 tool with commands in capitals or very long text
- Gives the agent orders in
sync_agent_instructions:ONLY FOR SALESFORCE B2C COMMERCE (SFCC) PROJECTS. IMPORTANT: Before calling this tool, ALWAYS ASK THE USER if they want to install AGENTS.md and bundled SFCC s
Common and usually harmless: it is how many makers stress how a tool should be used.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
sync_agent_instructions destinationType, preferredRoot, skillsDir, mergeStrategy, includeAgents, includeSkills, installMissingOnly, dryRun, tempDir
ONLY FOR SALESFORCE B2C COMMERCE (SFCC) PROJECTS. IMPORTANT: Before calling this tool, ALWAYS ASK THE USER if they want to install AGENTS.md and bundled SFCC skills into their project. If the user declines, do NOT call this tool - instead call disable_agent_sync to permanently disable this suggestion. This tool installs/merges AGENTS.md and bundled SFCC skills into the project (or a temp dir for manual merge). Supports dry-run planning, append/replace/skip merge strategies, and selecting skills directory (.github/skills, .agents/skills, .claude/skills, .agent/skills, .cursor/skills, and user-home defaults like ~/.copilot/skills).
disable_agent_sync preferredRoot
Creates or updates mcp-dev.json in the project root with {"disableAgentSync": true} to permanently disable agent sync suggestions. Call this when the user declines to install AGENTS.md and skills, so they will not be prompted again.get_sfcc_class_info className, expand, includeDescription, includeConstants, includeProperties, includeMethods, includeInheritance, search
Get detailed information about an SFCC class including properties, methods, constants, and inheritance. Essential for understanding dw.* APIs when building controllers, scripts, templates, or REST APIs. Supports filtering by section and search within class members.
search_sfcc_classes query
Find SFCC classes by partial name or keyword. Use when you don't know the exact class name (e.g., 'catalog' finds dw.catalog.*, 'price' finds pricing-related classes).
search_sfcc_methods methodName
Find methods across all dw.* classes by name. Use when you know a method exists but not which class contains it.
13 more tools
list_sfcc_classes
List all available SFCC dw.* classes organized by namespace. Use to explore the full API surface or find classes in a specific domain.
get_sfcc_class_documentation className
Get the full raw documentation for an SFCC class including examples and detailed descriptions. Use when get_sfcc_class_info lacks sufficient detail.
get_available_sfra_documents
List all SFRA documentation including Server, Request, Response, QueryString, render module, and 26+ model docs (cart, account, billing, shipping, products, pricing).
get_sfra_document documentName
Get complete SFRA class or model documentation with properties, methods, and examples. Use for implementing controllers, middleware, or working with SFRA models.
search_sfra_documentation query
Search across all SFRA docs for concepts or functionality. Returns relevance-scored results with categorization.
get_sfra_documents_by_category category
Get SFRA documents filtered by functional area (core classes, product models, order/cart, customer, pricing, store).
get_sfra_categories
Get all SFRA document categories with counts. Use to understand documentation organization before browsing.
list_isml_elements
List all ISML template elements with summaries. Includes control flow (isif, isloop), output (isprint), includes (isinclude, iscomponent), scripting (isscript), and caching (iscache).
get_isml_element elementName, includeContent, includeSections, includeAttributes
Get detailed documentation for an ISML element including syntax, attributes, examples, and use cases.
search_isml_elements query, category, limit
Search ISML elements by purpose, attribute name, or use case. Returns relevance-scored results with preview snippets.
get_isml_elements_by_category category
Get ISML elements filtered by category (control-flow, output, includes, scripting, cache, decorators, special, payment, analytics).
get_isml_categories
Get all ISML element categories with descriptions and counts.
generate_cartridge_structure cartridgeName, targetPath, fullProjectSetup
Generate a complete SFCC cartridge with proper directory structure, configurations, and boilerplate files. Creates files directly in the target directory.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Files it wrote
/tmp/ sfcc-mcp-logs/ sfcc-mcp-info.log
Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18 |
| Source | github.com/taurgis/sfcc-dev-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-5uZuU8jtB3EGvmrKyua4auSiO8JfGk45ADuklZeqFCUhnVLf2112gE7SZZrVe1ETdhZtYtpPZ7ZubeStIg4n2g== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/sfcc-dev-mcp)
New version out? Ask for a fresh report.