- Home
- MCP servers
- Salesforce
Salesforce
- javascript
1
GitHub Stars
javascript
Language
5 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"jpmonette-salesforce-mcp": {
"command": "node",
"args": [
"/Users/jpmonette/Documents/Code/salesforce-mcp/build/stdio.js"
],
"env": {
"SALESFORCE_PASSWORD": "your_password",
"SALESFORCE_USERNAME": "your_username"
}
}
}
}This minimal MCP server lets you connect an MCP client to Salesforce through the jsforce-based API bridge. It provides a straightforward way to run a local MCP endpoint that authenticates with Salesforce and exposes data and actions to your MCP client workflows.
How to use
You run the Salesforce MCP server locally and then connect your MCP client to it as you would with any other MCP endpoint. Start the server in the mode you prefer and provide Salesforce credentials to authorize API access. Your MCP client can then request data from Salesforce or trigger actions through the same MCP protocol you already use for other data sources.
Typical usage flow: start the server, ensure it is running, and point your MCP client at the local process. The server handles authentication with Salesforce using the credentials you supply, so your client can rely on established session handling and permissions. If you need to stop or restart, simply terminate the running process and start it again.
How to install
# Prerequisites: ensure you have Node.js and npm installed
# 1) Clone the project
git clone git@github.com:jpmonette/salesforce-mcp.git && cd salesforce-mcp
# 2) Install dependencies
npm install
# 3) Build the project
npm build
Run options and environment
You can run the server in different ways depending on your deployment preference. The common approach is to use the STDIO channel for local development and testing.
node build/stdio.js
Environment variables to authenticate with Salesforce
Set the Salesforce credentials you want the MCP server to use when connecting to the Salesforce API.
export SALESFORCE_USERNAME=your_username
export SALESFORCE_PASSWORD=your_password
Example MCP configuration for running locally
{
"mcpServers": {
"salesforce": {
"command": "node",
"args": ["/Users/jpmonette/Documents/Code/salesforce-mcp/build/stdio.js"],
"env": {
"SALESFORCE_USERNAME": "your_username",
"SALESFORCE_PASSWORD": "your_password"
}
}
}
}
Security and access considerations
Treat Salesforce credentials as sensitive data. Use secure storage or secret management for your production deployments, and limit access to the MCP server to trusted environments. Rotate credentials regularly and monitor API usage to stay within Salesforce limits.
Notes
If you are integrating this with Claude Desktop or other MCP clients, pass the same environment variables to the running process so the client can authenticate on your behalf when initiating requests.