Overview
What is SFCC MCP Server?
An MCP (Model Context Protocol) server that interacts with Salesforce Commerce Cloud (SFCC) APIs, enabling dynamic endpoint registration, OCAPI authentication, and support for both stdio and remote modes. It is intended for developers working with SFCC instances.
How to use SFCC MCP Server?
Install dependencies with npm install, build with npm run build, configure .env with SFCC API base, client ID, and client secret, then start with node build/index.js. In VSCode, add it as an MCP server via Command Palette using the stdio command node <full-path-to>/build/index.js.
Key features of SFCC MCP Server
- Dynamic endpoint registration via
endpoints.json - Automatic handling of path and query parameters
- OCAPI authentication using client credentials flow
- Support for GET, POST, PUT, DELETE requests
- Remote mode with OAuth authentication
- Per-session configuration and multi-tenant support
- Automated deployment to Google App Engine
Use cases of SFCC MCP Server
- Querying SFCC product search via Data API endpoints
- Automating SFCC administration tasks through custom endpoints
- Integrating SFCC data into AI-assisted coding workflows in GitHub Copilot
FAQ from SFCC MCP Server
What authentication does SFCC MCP Server use?
It uses OCAPI client credentials flow, configured via SFCC_ADMIN_CLIENT_ID and SFCC_ADMIN_CLIENT_SECRET in the .env file.
Can multiple SFCC instances be used simultaneously?
Yes, per-session configuration allows different credentials and endpoints per session, supporting multi‑tenant use.
Where are API endpoints defined?
Endpoints are defined in src/endpoints.json, each with path, description, optional method, and parameter definitions.
Does the server support custom request processing?
Yes, custom handlers can be created for endpoints by naming a function handler_[toolName] in index.ts.
What deployment options are available?
Automated deployment to Google App Engine is supported via npm commands like npm run version:create and npm run version:deploy.
