salesforce_search_objectsLABSCO SUMMARY
Salesforce work and the notification wiring in one place.
Getting a WhatsApp message when a lead lands normally means an admin, a trigger and a middleware service. Here it is one setup call, and the same session that shaped the object can wire what happens after it.
What it is
A Salesforce client with an integration builder attached. Beyond object, schema and record work it can create integrations that fire an external call when a record is created, updated or deleted.
What you get
- Custom objects and fields created and modified in natural language, with partial-name search to find them
- Full field and relationship detail for any object
- Record queries with relationship support and complex filters, plus insert, update, delete and upsert
- Cross-object search using SOSL
- Apex classes and triggers read, created and updated
- Integrations to external APIs created, listed, updated, activated, deactivated and deleted
- Templates for the common cases: WhatsApp on new leads, Slack on opportunities, email on cases, and a generic webhook for anything else
Requirements
Build it from a clone of this repository and connect a Salesforce org you can write to. Each integration carries its own credentials — a WhatsApp Business API token and number, a Slack webhook URL, or the endpoint you are calling.
Setup effort
Build from source — git clone https://github.com/chetyz/Mcp_Salesforce.git
USE CASES
01
Getting told the moment a lead arrives
Pick the template, give it the number and the message, and new leads start firing a WhatsApp notification.
02
Auditing what is already wired up
List every configured integration, then deactivate or delete the ones nobody remembers creating.
03
Pointing an object at your own service
A generic webhook on any object and event combination, so the destination does not have to be one of the templates.
04
Changing an integration without rebuilding it
Update its settings, switch it off for a release, switch it back on afterwards.
05
Getting records out without writing SOQL
Queries with relationship support and complex filters, described rather than composed, with SOSL for the searches that cross objects.
17 tools
Listed in project docs. Your client may show a different list.
salesforce_describe_objectsalesforce_query_recordssalesforce_aggregate_querysalesforce_dml_recordssalesforce_manage_objectsalesforce_manage_fieldsalesforce_manage_field_permissionssalesforce_search_allsalesforce_read_apexsalesforce_write_apexsalesforce_read_apex_triggersalesforce_write_apex_triggersalesforce_execute_anonymoussalesforce_manage_debug_logssalesforce_manage_integrationssalesforce_quick_setup_integrationBEFORE YOU INSTALL
What to know first
Tools you get
17 tools named in the project's documentation.
Requires
- Node.js and npm, to install and build the clone
- A Salesforce org: a username, password and security token, or a Connected App client ID and secret (Client Credentials Flow), plus the instance URL
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/chetyz/Mcp_Salesforce.git
cd Mcp_Salesforce
npm install
npm run buildMCP Clients
Claude Desktop — username, password
CLAUDE DESKTOP — USERNAME, PASSWORD · JSON
{
"mcpServers": {
"salesforce": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_SALESFORCE>/dist/index.js"
],
"env": {
"SALESFORCE_CONNECTION_TYPE": "User_Password",
"SALESFORCE_USERNAME": "<YOUR_SALESFORCE_USERNAME>",
"SALESFORCE_PASSWORD": "<YOUR_SALESFORCE_PASSWORD>",
"SALESFORCE_TOKEN": "<YOUR_SALESFORCE_TOKEN>",
"SALESFORCE_INSTANCE_URL": "org_url"
}
}
}
}<YOUR_PATH_TO_MCP_SALESFORCE> is the folder you cloned and built (the build writes dist/index.js). <YOUR_SALESFORCE_TOKEN> is your security token (reset it from Salesforce Settings).
Claude Desktop — OAuth
CLAUDE DESKTOP — OAUTH · JSON
{
"mcpServers": {
"salesforce": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_SALESFORCE>/dist/index.js"
],
"env": {
"SALESFORCE_CONNECTION_TYPE": "OAuth_2.0_Client_Credentials",
"SALESFORCE_CLIENT_ID": "<YOUR_SALESFORCE_CLIENT_ID>",
"SALESFORCE_CLIENT_SECRET": "<YOUR_SALESFORCE_CLIENT_SECRET>",
"SALESFORCE_INSTANCE_URL": "https://<YOUR_DOMAIN>.my.salesforce.com"
}
}
}
}<YOUR_PATH_TO_MCP_SALESFORCE> is the folder you cloned and built. <YOUR_SALESFORCE_CLIENT_ID> and <YOUR_SALESFORCE_CLIENT_SECRET> come from a Connected App that has Client Credentials Flow enabled (the api scope is usually enough).
