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
- List all available SObjects - Discover standard and custom objects
- 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"
}
}
}
}
Available Tools
Query and Search Tools
run_soql_query- Execute SOQL queries against Salesforcerun_sosl_search- Perform SOSL searches across objects
Metadata Tools
get_object_fields- Retrieve field metadata for specific objectslist_sobjects- List all available SObjects (standard and custom)
Single Record Operations
get_record- Retrieve a specific record by IDcreate_record- Create a new recordupdate_record- Update an existing recorddelete_record- Delete a record
Bulk Operations
bulk_create_records- Create multiple records in a single operationbulk_update_records- Update multiple records (must include Id field)bulk_delete_records- Delete multiple records using record IDs
Advanced API Tools
tooling_execute- Execute Tooling API requestsapex_execute- Execute Apex REST requestsrestful- Make direct REST API calls to Salesforce
Note on Salesforce Authentication Methods
This server supports four authentication methods:
- OAuth (Recommended): Set
SALESFORCE_ACCESS_TOKENandSALESFORCE_INSTANCE_URLas environment variables. - Client Credentials: Set
SALESFORCE_CLIENT_IDandSALESFORCE_CLIENT_SECRETfor OAuth 2.0 Client Credentials flow. This is useful for server-to-server integrations. - Salesforce CLI (Default Org): If no OAuth env vars are set, the server will try to use the active Salesforce CLI default org from the current workspace (via
sf org display --jsonorsfdx force:org:display --json). Optionally setSALESFORCE_CLI_TARGET_ORGto target a specific org. - 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.SALESFORCE_CLI_TARGET_ORG(Optional): When using the Salesforce CLI authentication method, set this to target a specific org alias or username instead of the default org.
Metadata
Release files for mcp-salesforce-connector 0.1.18
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 |
|---|---|---|---|---|
| mcp_salesforce_connector-0.1.18.tar.gz | 55.5 kB | Without provenance | Details for mcp_salesforce_connector-0.1.18.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_salesforce_connector-0.1.18-py3-none-any.whl | Python 3 | none | any | Details for mcp_salesforce_connector-0.1.18-py3-none-any.whl |
Total release size: 65.9 kB
Release files / mcp_salesforce_connector-0.1.18.tar.gz
| Download URL | mcp_salesforce_connector-0.1.18.tar.gz |
|---|---|
| Size | 55.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ba4a4e2cae168172971ade81c61e78cd49d2fa5a30b85c3049f5ea8e60dd1ad
|
|
BLAKE2b-256 checksum How to use checksums |
b84d4667761f8b9eb7bf826c0663ffcbf3587cb40ea86e3e069ea9ffd9669082
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.0 {"installer":{"name":"uv","version":"0.12.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / mcp_salesforce_connector-0.1.18-py3-none-any.whl
| Download URL | mcp_salesforce_connector-0.1.18-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
88dc75a03c873aeb18494974a0aebb54aabfda3c03ddafc4416e2e74b3924400
|
|
BLAKE2b-256 checksum How to use checksums |
abc56c5ad820a58799421bddf944d3632d6a1a94abf6cca4a8a1ecc5bf78ba93
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.0 {"installer":{"name":"uv","version":"0.12.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for mcp-salesforce-connector 0.1.18
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.