Skip to main content
Glama
taurgis

SFCC Development MCP Server

by taurgis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to SFCC Development MCP Server

No user-submitted related servers found.

    Related Servers

    • sfcc-logs-mcp

      nabhat
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to fetch, tail, and clean Salesforce Commerce Cloud log files in real-time, with dynamic workspace resolution for seamless switching between multiple SFCC instances.
      13
      6 npm
      MIT

    • Salesforce DX MCP Server

      kodey-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure interaction with Salesforce orgs through LLMs, providing tools for managing orgs, querying data, deploying metadata, running tests, and performing code analysis with granular access control and encrypted authentication.
      Apache 2.0

    • MCP Salesforce Server

      AiondaDotCom
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with Salesforce through a secure interface for performing CRUD operations, executing SOQL queries, and managing schema discovery. It features a smart learning system that analyzes custom objects and fields to provide intelligent assistance tailored to specific Salesforce configurations.
      14
      50 npm
      17
      BSD 2-Clause "Simplified"
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 15 tools

    Disambiguation3/5

    The tools have some overlap that could cause confusion, particularly between get_* and search_* tools (e.g., get_sfcc_class_info vs. search_sfcc_classes) and among documentation retrieval tools (e.g., get_sfra_document vs. get_sfra_documents_by_category). However, descriptions help clarify distinctions, such as get_* for specific retrieval and search_* for broader exploration, preventing complete ambiguity.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, with clear and predictable structures like generate_cartridge_structure, get_available_best_practice_guides, and search_sfcc_classes. There are no deviations in naming conventions, making it easy for agents to parse and understand the tool purposes.

    Tool Count4/5

    With 15 tools, the count is slightly high but reasonable for a development server covering documentation, best practices, and code generation in the SFCC domain. It includes a mix of generation, listing, retrieval, and search tools, which aligns well with the server's purpose, though it might feel a bit heavy compared to more streamlined sets.

    Completeness4/5

    The tool surface is largely complete for its domain, covering documentation retrieval, best practices, and code generation for SFCC development. Minor gaps exist, such as the lack of tools for directly modifying or deploying cartridges, but agents can work around these by using the available tools for guidance and structure generation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources