MCP Salesforce Connector
A Model Context Protocol (MCP) server implementation for Salesforce integration, allowing LLMs to interact with Salesforce data through SOQL queries and SOSL searches.
Features
- Execute SOQL (Salesforce Object Query Language) queries
- Perform SOSL (Salesforce Object Search Language) searches
- Retrieve metadata for Salesforce objects, including field names, labels, and types
- Retrieve, create, update, and delete records
- Execute Tooling API requests
- Execute Apex REST requests
- Make direct REST API calls to Salesforce
Configuration
Model Context Protocol
To use this server with the Model Context Protocol, you need to configure it in your claude_desktop_config.json file. Add the following entry to the mcpServers section:
{
"mcpServers": {
"salesforce": {
"command": "uvx",
"args": [
"--from",
"mcp-salesforce-connector",
"salesforce"
],
"env": {
"SALESFORCE_ACCESS_TOKEN": "SALESFORCE_ACCESS_TOKEN",
"SALESFORCE_INSTANCE_URL": "SALESFORCE_INSTANCE_URL",
"SALESFORCE_DOMAIN": "SALESFORCE_DOMAIN"
}
}
}
}
Note on Salesforce Authentication Methods
This server supports two authentication methods:
- OAuth (Recommended): Set
SALESFORCE_ACCESS_TOKENandSALESFORCE_INSTANCE_URLas environment variables. - Username/Password (Legacy): If
SALESFORCE_ACCESS_TOKENandSALESFORCE_INSTANCE_URLare not set, the server will fall back to usingSALESFORCE_USERNAME,SALESFORCE_PASSWORD, andSALESFORCE_SECURITY_TOKEN.
Environment Configuration
SALESFORCE_DOMAIN(Optional): Set totestto connect to a Salesforce sandbox environment. If not set or left empty, the server will connect to the production environment.
Metadata
Release files for iflow-mcp_mcp-salesforce-connector 0.1.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_mcp_salesforce_connector-0.1.9.tar.gz | 39.7 kB | Without provenance | Details for iflow_mcp_mcp_salesforce_connector-0.1.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_mcp_salesforce_connector-0.1.9-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_mcp_salesforce_connector-0.1.9-py3-none-any.whl |
Total release size: 46.1 kB
Release files / iflow_mcp_mcp_salesforce_connector-0.1.9.tar.gz
| Download URL | iflow_mcp_mcp_salesforce_connector-0.1.9.tar.gz |
|---|---|
| Size | 39.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0eb38b44c7c8b2583fedfd4347cdbad59fbfedc9d7f7829bbddf46419f1ce559
|
|
BLAKE2b-256 checksum How to use checksums |
654d7b54bb2a92dfc6e1dfd7cce82c9188ae5a7169d1808f426f873be88adb8a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.10 {"installer":{"name":"uv","version":"0.9.10"},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_mcp_salesforce_connector-0.1.9-py3-none-any.whl
| Download URL | iflow_mcp_mcp_salesforce_connector-0.1.9-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
99ebb615cf20758d53f8d01998a61a7b020b3e84236da5c92ab14ca9dbbd6289
|
|
BLAKE2b-256 checksum How to use checksums |
c3fc58dae23a54c4ee2834f5e2a4b89279f608f3569a8f7052174909f7700e55
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.10 {"installer":{"name":"uv","version":"0.9.10"},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_mcp-salesforce-connector 0.1.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.