sfcc

This MCP server provides a remote interface to Salesforce Commerce Cloud (SFCC) APIs via the MCP (Model Context Protocol). It dynamically registers endpoints based on the configuration in src/endpoints.json, handles path and query parameters automatically, and supports both GET and POST requests. It authenticates with SFCC using the client credentials flow against the Admin API, and can access SFCC Data APIs, including product search. The server supports multi-tenant deployments, allowing different SFCC instances and credentials per session, and is designed for automated deployment workflows (e.g., GitHub Actions to Google App Engine). You can start the server with Node.js and then call the generated tools/endpoints through the MCP runtime in your editor or tooling.

Once running, endpoints are exposed according to the endpoints.json configuration. Tools are automatically generated from endpoint paths (path separators become underscores, path parameters become by_param, and names are truncated if needed). If you need custom behavior, you can implement a handler_[toolName] function to override the default behavior for a given endpoint. This enables you to preprocess requests, modify bodies, or route to alternative SFCC APIs before returning the response to the client.

Prerequisites:

• Node.js and npm installed
• A Salesforce Commerce Cloud (SFCC) environment with API client credentials

Installation steps:

1. Install dependencies

   npm install
   

2. Build the server

   npm run build
   

3. Create and configure environment variables (see Configuration section) or provide them via the MCP config when running the server.
4. Start the server (from project root):

   node build/index.js
   

Optional for VSCode MCP integration:

• Use the MCP VSCode extension to add the server definition in your settings, using the provided command and path example from the README.

Tips and common issues:

• Ensure SFCC_API_BASE is correctly set to your SFCC instance base URL.
• The Admin API credentials (SFCC_ADMIN_CLIENT_ID and SFCC_ADMIN_CLIENT_SECRET) must have appropriate permissions for the endpoints you intend to use.
• For POST endpoints, you can supply a requestBody in your call; defaultBody definitions will be used if you omit it.
• If you customize tool names or add custom handlers, ensure your handler_[toolName] function exists and is exported/accessible as described in the Custom Handlers section.
• When running multi-tenant, consider per-session configuration for credentials and endpoints to isolate clients.
• If you encounter authentication issues, verify token endpoint configurations in SFCC and ensure the OAuth client has the correct scopes and grant type (client_secret_post).
• Remember to rebuild after changes to TypeScript sources (npm run build).