A comprehensive Salesforce connector that wraps the full REST API surface, giving you SOQL queries, SOSL searches, and CRUD operations on any SObject. Beyond basic data access, it exposes Tooling API for metadata operations and Apex REST endpoints for custom logic. Supports multiple auth flows including OAuth, CLI integration, and client credentials, making it work whether you're prototyping with sf CLI or building production integrations. Reach for this when you need Claude to pull customer data, update records, or analyze Salesforce metadata without switching contexts.
A Model Context Protocol (MCP) server implementation for Salesforce integration, allowing LLMs to interact with Salesforce data through SOQL queries and SOSL searches.
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"
}
}
}
}
run_soql_query - Execute SOQL queries against Salesforcerun_sosl_search - Perform SOSL searches across objectsget_object_fields - Retrieve field metadata for specific objectslist_sobjects - List all available SObjects (standard and custom)get_record - Retrieve a specific record by IDcreate_record - Create a new recordupdate_record - Update an existing recorddelete_record - Delete a recordbulk_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 IDstooling_execute - Execute Tooling API requestsapex_execute - Execute Apex REST requestsrestful - Make direct REST API calls to SalesforceNote on Salesforce Authentication Methods
This server supports four authentication methods:
SALESFORCE_ACCESS_TOKEN and SALESFORCE_INSTANCE_URL as environment variables.SALESFORCE_CLIENT_ID and SALESFORCE_CLIENT_SECRET for OAuth 2.0 Client Credentials flow. This is useful for server-to-server integrations.sf org display --json or sfdx force:org:display --json). Optionally set SALESFORCE_CLI_TARGET_ORG to target a specific org.SALESFORCE_ACCESS_TOKEN and SALESFORCE_INSTANCE_URL are not set, the server will fall back to using SALESFORCE_USERNAME, SALESFORCE_PASSWORD, and SALESFORCE_SECURITY_TOKEN.Environment Configuration
SALESFORCE_DOMAIN (Optional): Set to test to 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.explorium-ai/vibeprospecting-mcp
io.github.compuute/lead-enrichment
dev.workers.selbyventurecap.cf-worker/apollo-salesforce-mapper
io.github.br0ski777/company-enrichment
com.mcparmory/apollo
mambalabsdev/mcp-gtm-tech-stack-signal-scraper