MCP Salesforce Connector
Allows LLMs to interact with Salesforce data through SOQL queries, SOSL searches, and provides tools for retrieving metadata, managing records (create, read, update, delete), executing Tooling API requests, running Apex REST requests, and making direct REST API calls to Salesforce.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Salesforce Connector show me the top 5 accounts by revenue this quarter"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Related MCP server: Salesforce MCP Server
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",
}
}
}
}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.
Available Tools
10 toolsapex_executeC
Executes an Apex REST request
Inputs: action (required), method, data.
create_recordD
Creates a new record
Inputs: object_name (required), data (required).
delete_recordC
Deletes a record
Inputs: object_name (required), record_id (required).
get_object_fieldsC
Retrieves field Names, labels and types for a specific Salesforce object
Inputs: object_name (required).
get_recordC
Retrieves a specific record by ID
Inputs: object_name (required), record_id (required).
restfulB
Makes a direct REST API call to Salesforce
Inputs: path (required), method, params, data.
run_soql_queryC
Executes a SOQL query against Salesforce
Inputs: query (required).
run_sosl_searchC
Executes a SOSL search against Salesforce
Inputs: search (required).
tooling_executeC
Executes a Tooling API request
Inputs: action (required), method, data.
update_recordB
Updates an existing record
Inputs: object_name (required), record_id (required), data (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Most tools have distinct purposes, but there is some overlap between 'restful', 'apex_execute', and 'tooling_execute' as they all involve making API calls to Salesforce, which could cause confusion. The CRUD operations and query tools are clearly differentiated.
The naming is mostly consistent with a verb_noun pattern, but there are minor deviations like 'restful' (adjective instead of verb) and 'tooling_execute' (noun_verb instead of verb_noun). Overall, the pattern is readable and predictable.
With 10 tools, the count is well-scoped for a Salesforce connector, covering core operations like CRUD, queries, and API interactions. Each tool serves a specific function without being overwhelming.
The tool set provides comprehensive coverage for Salesforce operations, including CRUD, metadata retrieval (get_object_fields), querying (SOQL/SOSL), and various API calls (REST, Apex, Tooling). There are no obvious gaps for typical agent workflows.
Maintenance
Related MCP Connectors
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Marketo MCP server for AI. 130 tools to operate Marketo from Claude, Cursor, or ChatGPT.
The HubSpot MCP Server acts as a bridge that enables AI assistants and Large Language Models to securely interact with HubSpot CRM data through natural conversation, without requiring users to understand complex API structures. It provides read-only access to standard CRM objects (contacts, companies, deals, tickets, products, invoices, and more) and their associations, secured via OAuth 2.0, allowing AI agents to perform tasks like summarizing deals, fetching company updates, and looking up record changes.
API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.
Related MCP Servers
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables LLMs to interact with Salesforce data through SOQL queries, SOSL searches, and various API operations including record management.14197 PyPI179MIT
- AlicenseNot gradedqualityDmaintenanceA TypeScript implementation of a Model Context Protocol server that enables LLMs to interact with Salesforce data through SOQL queries, SOSL searches, and CRUD operations.2MIT
- FlicenseBqualityDmaintenanceA customizable MCP server for integrating Salesforce APIs with GenAI applications, supporting SOQL queries, record CRUD, metadata access, and more.138-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects AI assistants to Salesforce orgs, enabling querying, searching, creating, updating, and managing Salesforce data through natural language via any MCP-compatible client.48 npmMIT