The MCP Salesforce Connector enables LLMs to interact with Salesforce data and APIs through the following capabilities:
Run SOQL Queries (run_soql_query): Execute Salesforce Object Query Language queries to retrieve structured data.
Run SOSL Searches (run_sosl_search): Perform searches across multiple objects and fields (e.g., FIND {John Smith} IN ALL FIELDS).
Get Object Fields (get_object_fields): Retrieve metadata for Salesforce objects, including field names, labels, and data types.
Record Management: Retrieve (get_record), create (create_record), update (update_record), and delete (delete_record) records for any Salesforce object.
Tooling API (tooling_execute): Make GET, POST, PATCH, and DELETE calls to the Salesforce Tooling API (e.g., access ApexClass metadata).
Apex REST (apex_execute): Call custom Apex REST endpoints with GET, POST, PATCH, and DELETE methods.
Direct REST API (restful): Make arbitrary REST API calls to any Salesforce endpoint with custom paths, methods, query parameters, and request bodies.
Supports OAuth, Salesforce CLI, and username/password authentication, and works with both production and sandbox environments.
Enables interaction with Salesforce data through SOQL queries, SOSL searches, and various operations including 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 last 10 opportunities created this week"
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.
A Model Context Protocol (MCP) server implementation for Salesforce integration, allowing LLMs to interact with Salesforce data through SOQL queries and SOSL searches.
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
Related MCP server: Salesforce MCP Integration
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 Salesforce
run_sosl_search - Perform SOSL searches across objects
get_object_fields - Retrieve field metadata for specific objects
list_sobjects - List all available SObjects (standard and custom)
get_record - Retrieve a specific record by ID
create_record - Create a new record
update_record - Update an existing record
delete_record - Delete a record
bulk_create_records - Create multiple records in a single operation
bulk_update_records - Update multiple records (must include Id field)
bulk_delete_records - Delete multiple records using record IDs
tooling_execute - Execute Tooling API requests
apex_execute - Execute Apex REST requests
restful - Make direct REST API calls to Salesforce
Note on Salesforce Authentication Methods
This server supports four authentication methods:
OAuth (Recommended): Set SALESFORCE_ACCESS_TOKEN and SALESFORCE_INSTANCE_URL as environment variables.
Client Credentials: Set SALESFORCE_CLIENT_ID and SALESFORCE_CLIENT_SECRET for 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 --json or sfdx force:org:display --json). Optionally set SALESFORCE_CLI_TARGET_ORG to target a specific org.
Username/Password (Legacy): If 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.
Executes an Apex REST request
Inputs: action (required), data, method.
Creates multiple records of a specified SObject type in bulk.
Inputs: data (required), object_name (required).
Deletes multiple records of a specified SObject type in bulk, given their IDs.
Inputs: record_ids (required), object_name (required).
Updates multiple records of a specified SObject type in bulk. Each record must have an 'Id' field.
Inputs: data (required), object_name (required).
Creates a new record
Inputs: data (required), object_name (required).
Deletes a record
Inputs: record_id (required), object_name (required).
Retrieves field names and types for a Salesforce object. Use this to discover available fields before writing SOQL queries.
Output is CSV format: name,label,type,updateable
Inputs: object_name (required).
Retrieves a specific record by ID. Returns all fields - prefer SOQL with specific fields for token efficiency.
Inputs: record_id (required), object_name (required), format.
Retrieves a list of all available Salesforce SObjects (standard and custom).
Inputs: no named parameters.
Makes a direct REST API call to Salesforce
Inputs: path (required), data, method, params.
Executes a SOQL query against Salesforce.
TOKEN OPTIMIZATION GUIDELINES:
Always SELECT only the fields you need (never SELECT *)
Use LIMIT to restrict results (start with LIMIT 10, increase if needed)
Use WHERE clauses to filter data server-side
Default output is CSV format (most token-efficient)
Use format='json' only when you need nested data structure
You can always run additional queries if you need more data
Example efficient query: SELECT Id, Name FROM Account WHERE IsActive = true LIMIT 20
Inputs: query (required), format.
Executes a SOSL search against Salesforce.
TOKEN OPTIMIZATION: Use RETURNING clause to limit fields and objects. Example: FIND {searchterm} RETURNING Account(Id, Name), Contact(Id, Name) LIMIT 10
Inputs: search (required), format.
Executes a Tooling API request
Inputs: action (required), data, method.
Updates an existing record
Inputs: data (required), record_id (required), object_name (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 14 tools
Each tool targets a distinct operation: CRUD, bulk CRUD, queries, metadata, and direct API calls. Overlaps like get_record vs run_soql_query are clarified by different access patterns (ID vs query). Apex and tooling executes are differentiated by API type.
Most tools follow snake_case verb_noun pattern (e.g., create_record, run_soql_query). Exceptions include 'restful' (single word) and plural in bulk tools (bulk_create_records) vs singular in standard tools (create_record), causing minor inconsistency.
14 tools cover a broad Salesforce use case without being excessive. Each tool has a clear purpose, and the count is well-scoped for a comprehensive connector.
The tool set covers CRUD, bulk operations, queries, searches, object metadata, and direct API calls. Minor gaps include absence of upsert or describe metadata operations, but core workflows are fully supported.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
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.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
