Salesforce MCP Server

An MCP (Model Context Protocol) server implementation that integrates Claude with Salesforce, enabling natural language interactions with your

Local serverstdio

What is the Salesforce MCP server?

Most developer tooling work still happens through a UI a human drives. Salesforce MCP server moves it into the conversation instead. 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.

The short version

  • 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

What it needs from you

Configuration is passed through the environment: SALESFORCE_USERNAME, SALESFORCE_PASSWORD, SALESFORCE_TOKEN, SALESFORCE_INSTANCE_URL, SALESFORCE_CONSUMER_KEY, SALESFORCE_CONSUMER_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

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

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by SurajAdsul; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • 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.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How to install the Salesforce MCP server

##### For OAuth2 Authentication
```json
{
  "mcpServers": {
    "salesforce": {
      "command": "npx",
      "args": ["-y", "@surajadsul02/mcp-server-salesforce"],
      "env": {
        "SALESFORCE_USERNAME": "your_username",
        "SALESFORCE_PASSWORD": "your_password",
        "SALESFORCE_CONSUMER_KEY": "your_consumer_key",
        "SALESFORCE_CONSUMER_SECRET": "your_consumer_secret",
        "SALESFORCE_INSTANCE_URL": "https://login.salesforce.com"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
SALESFORCE_USERNAMEConfiguration value read at startup.Optional
SALESFORCE_PASSWORDConfiguration value read at startup.Optional
SALESFORCE_TOKENCredential the server authenticates with.Yes
SALESFORCE_INSTANCE_URLEndpoint or connection string the server talks to.Yes
SALESFORCE_CONSUMER_KEYCredential the server authenticates with.Yes
SALESFORCE_CONSUMER_SECRETCredential the server authenticates with.Yes

Frequently asked questions

The server supports username/password with a security token and OAuth2 with a consumer key