# Salesforce [Health: Active]

**Category:** 👤 Customer Data Platforms  
**Repository:** https://github.com/WYRE-AI/salesforce-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 70  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/salesforce

## Description
MCP server for Salesforce CRM — Accounts, Contacts, Opportunities, Leads, Cases.

## Tools
Capabilities this server exposes over MCP:

- **Describe Salesforce Object** — Describe a Salesforce object and return its field information in CSV format
- **List Salesforce Objects** — List all available Salesforce objects
- **Find Similar Objects** — Find Salesforce objects with similar names
- **Create Data Dictionary** — Create a data dictionary from one or more Salesforce objects and export as Excel (one tab per object)

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "salesforce": {
    "command": "npx",
    "args": ["-y","salesforce-mcp"],
    "env": {
      "CONDUIT_S2S_SECRET": "",
      "SALESFORCE_CLIENT_ID": "",
      "SALESFORCE_CLIENT_SECRET": "",
      "SALESFORCE_INSTANCE_URL": "",
      "SALESFORCE_USERNAME": "",
      "SALESFORCE_PASSWORD": "",
      "SALESFORCE_TOKEN": "",
      "MCP_TRANSPORT": ""
    }
  }
}
```

**Requires environment variables:** `CONDUIT_S2S_SECRET`, `SALESFORCE_CLIENT_ID`, `SALESFORCE_CLIENT_SECRET`, `SALESFORCE_INSTANCE_URL`, `SALESFORCE_USERNAME`, `SALESFORCE_PASSWORD`, `SALESFORCE_TOKEN`, `MCP_TRANSPORT` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the Salesforce MCP server does

The Salesforce MCP server gives MCP clients access to a focused set of Salesforce CRM operations. Its scope covers standard CRM records such as Accounts, Contacts, Opportunities, Leads, and Cases, while also allowing discovery and use of custom objects through the available query tools.

The tool surface is intentionally limited to CRM data access. It does not provide Apex code management, custom-object creation, or anonymous Apex execution. Teams needing Salesforce DX or broader administration capabilities should evaluate a different Salesforce MCP implementation.

## How it works

The Salesforce MCP server can run over HTTP or stdio. HTTP is the default mode and exposes `/mcp` for JSON-RPC requests plus an unauthenticated `/health` endpoint. In gateway mode, Salesforce credentials arrive in request headers, allowing one running instance to serve multiple customers without restarting. Each tool call creates a Salesforce connection using the credentials supplied for that request.

HTTP requests also require a valid `X-Gateway-S2S` header when a usable service-to-service secret is configured. The header contains a timestamp and HMAC-SHA256 signature, and the timestamp must be within 300 seconds of the server clock. Stdio is intended for traditional local MCP client connections and reads credentials once from the environment.

## Setup and configuration

Build the project with `npm install` followed by `npm run build`. Set `MCP_TRANSPORT=stdio` for local client use, or leave the transport at its HTTP default. Client-credentials authentication uses a Salesforce Connected App with client credentials enabled, a configured Run As user, the Consumer Key and Secret, and the organization’s My Domain URL.

For HTTP deployments, set `CONDUIT_S2S_SECRET` to a real secret. The process exits when this value is missing or remains a known placeholder. `MCP_ALLOW_INSECURE_DEV=1` permits local HTTP development without that secret, but binds only to `127.0.0.1` and disables gateway-header checks. `PORT` defaults to `8080`; bind behavior can be adjusted with `MCP_HTTP_HOST` and `HOST`.

Gateway mode expects Salesforce authentication headers on every MCP request and does not fall back to process environment variables. `AUTH_MODE=env` uses the `SALESFORCE_*` variables after service-to-service authentication succeeds.

## Tools and capabilities

The Salesforce MCP server provides six tools:

- `salesforce_search_objects` finds standard and custom objects using a partial name.
- `salesforce_describe_object` returns fields, picklists, and relationships for an object.
- `salesforce_query_records` runs SOQL queries, including relationship traversal.
- `salesforce_aggregate_query` supports SOQL grouping and COUNT, SUM, AVG, MIN, and MAX operations.
- `salesforce_dml_records` inserts, updates, deletes, or upserts records.
- `salesforce_search_all` performs cross-object searches with SOSL.

## Limitations and notes

The Salesforce MCP server is designed for a narrow CRM data surface, not general Salesforce administration. The `/health` endpoint does not authenticate or read Salesforce credentials. In container deployments, the image listens on `0.0.0.0`; Compose publishes the service on loopback by default. The project is licensed under Apache-2.0.

_Full upstream README: https://allmcps.com/mcp/salesforce/readme_