This MCP server implements a simple Salesforce MCP (Model Context Protocol) server as described in the accompanying guide. It’s built with Node.js and exposes a minimal MCP interface that allows clients to subscribe to Salesforce-like streams and receive structured events in MCP format. The repository provides the core server logic and configuration necessary to start listening for MCP connections, process incoming requests, and emit events to connected MCP clients. To use it, start the server and connect an MCP client to the designated port, then subscribe to the available entity streams or event channels defined by the server. The client can request, push, or update context data as defined by the MCP protocol and the server’s implemented capabilities.

Typical usage steps include starting the server, verifying it’s listening on the configured port, and then using an MCP-compatible client to subscribe to the Salesforce-like streams (for example, account or contact events) and consume the emitted MCP-formatted payloads. If you’re integrating with Salesforce or a mock Salesforce data source, configure the server to pull or simulate that data and forward it through the MCP interface. The tools provided focus on establishing the MCP connection, managing subscriptions, and delivering event payloads in a consistent, extensible format for downstream consumers.

Prerequisites:

• Node.js (v14+ recommended) and npm installed
• Basic familiarity with Node.js project structure

Installation steps:

1. Clone the repository: git clone https://github.com/akutishevsky-sf-mcp-server.git cd akutishevsky-sf-mcp-server

2. Install dependencies: npm install

3. Configure environment (optional):

   • Create a .env file to override defaults (port, log level, data sources, etc.).
   • Example: MCP_PORT=3000 LOG_LEVEL=info

4. Start the server: node server.js

   or if a script is provided

   npm start

5. Verify the server is running by checking the console output or attempting to connect an MCP client to the configured port.

Notes:

• If your setup uses a different entry file, adjust the command accordingly (e.g., node dist/server.js).
• Ensure any required Salesforce or mock data sources are reachable by the server process.

Tips and common issues:

• Ensure the port used by the MCP server is not blocked by a firewall and is accessible by MCP clients.
• If you see missing event streams, verify the server’s configuration or code paths that define available MCP channels.
• Use environment variables to toggle verbose logging during development (e.g., LOG_LEVEL=debug).
• If the server relies on external data sources (Salesforce, mocks), ensure credentials or connection strings are configured correctly in environment variables or a config file.
• When upgrading Node.js versions, validate that the MCP protocol handling code remains compatible with the Node runtime and dependencies.
• If you modify the server, document any new MCP endpoints or event channels added to aid downstream integrations.