Salesforce MCP Server

A Salesforce connector MCP Server. The salesforce mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

An MCP (Model Context Protocol) server implementation that integrates Claude with Salesforce, enabling natural language interactions with your Salesforce data and metadata. This server allows Claude to query, modify, and manage your Salesforce objects and records using everyday language.

• Object and Field Management — Create and modify custom objects and fields using natural language
• Smart Object Search — Find Salesforce objects using partial name matches
• Detailed Schema Information — Get comprehensive field and relationship details for any object
• Flexible Data Queries — Query records with relationship support and complex filters
• Data Manipulation — Insert, update, delete, and upsert records with ease
• Cross-Object Search — Search across multiple objects using SOSL

Its toolset

Everything the assistant can do here goes through one of these:

• salesforce_search_objects — Search for standard and custom objects: * Search by partial name matches * Finds both standard and custom objects * Example: "Find objects related to
• salesforce_describe_object — Get detailed object schema information: * Field definitions and properties * Relationship details * Picklist values * Example: "Show me all fields in
• salesforce_query_records — Query records with relationship support: * Parent-to-child relationships * Child-to-parent relationships * Complex WHERE conditions * Example: "Get
• salesforce_aggregate_query — Execute aggregate queries with GROUP BY: * GROUP BY single or multiple fields * Aggregate functions: COUNT, COUNT_DISTINCT, SUM, AVG, MIN, MAX *
• salesforce_dml_records — Perform data operations: * Insert new records * Update existing records * Delete records * Upsert using external IDs * Example: "Update status of
• salesforce_manage_object — Create and modify custom objects: * Create new custom objects * Update object properties * Configure sharing settings * Example: "Create a Customer
• salesforce_manage_field — Manage object fields: * Add new custom fields * Modify field properties * Create relationships * Automatically grants Field Level Security to System
• salesforce_manage_field_permissions — Manage Field Level Security (Field Permissions): * Grant or revoke read/edit access to fields for specific profiles * View current field permissions
• salesforce_search_all — Search across multiple objects: * SOSL-based search * Multiple object support * Field snippets * Example: "Search for 'cloud' across Accounts and
• salesforce_read_apex — Read Apex classes: * Get full source code of specific classes * List classes matching name patterns * View class metadata (API version, status, etc.)
• salesforce_write_apex — Create and update Apex classes: * Create new Apex classes * Update existing class implementations * Specify API versions * Example: "Create a new
• salesforce_read_apex_trigger — Read Apex triggers: * Get full source code of specific triggers * List triggers matching name patterns * View trigger metadata (API version, object

Adding it to your client

@tsmztech/mcp-server-salesforce on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need 7 environment variables: SALESFORCE_CONNECTION_TYPE, SALESFORCE_USERNAME, SALESFORCE_PASSWORD, SALESFORCE_TOKEN, SALESFORCE_INSTANCE_URL, SALESFORCE_CLIENT_ID, SALESFORCE_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Salesforce's toolset — salesforce_search_objects, salesforce_describe_object, salesforce_query_records and 11 more — is a fair guide to whether it matches your workflow. It is maintained by JereSalguero30; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Salesforce.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the salesforce mcp server does with a few real requests.