Salesforce

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

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "salesforce": {
      "command": "npx",
      "args": [
        "-y",
        "salesforce"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

salesforce-mcp

MCP (Model Context Protocol) server for Salesforce CRM, scoped to the WYRE Gateway BYOC use case.

A focused HTTP MCP server that exposes a Salesforce org's CRM data surface to Claude (and other MCP clients) through the WYRE MCP Gateway. Built for the multi-tenant gateway pattern: credentials are injected per-request via HTTP headers, no startup secrets are baked into the container.

Scope discipline

This package intentionally ships a narrow tool surface — six CRM data tools — and deliberately omits the Apex code-management / custom-object-creation / EXECUTE_ANONYMOUS surfaces that broader Salesforce MCP servers include. The use case is read/write access to standard CRM objects (Accounts, Contacts, Opportunities, Leads, Cases). Customers who need DX or admin tooling should use the official @salesforce/mcp package instead.

Tools

Tool	Purpose
`salesforce_search_objects`	Find standard + custom objects by partial name.
`salesforce_describe_object`	Full schema (fields, picklists, relationships) for an object.
`salesforce_query_records`	Execute SOQL with relationship traversal.
`salesforce_aggregate_query`	SOQL GROUP BY / COUNT / SUM / AVG / MIN / MAX.
`salesforce_dml_records`	Insert / update / delete / upsert records.
`salesforce_search_all`	Cross-object SOSL search.

Run modes

http (default): listens on :8080, exposes /mcp (JSON-RPC) + /health. Per-request credentials from X-Salesforce-* headers. This is the gateway deployment shape.
stdio: traditional MCP client transport (Claude Desktop / Cursor). Credentials read once from env. Useful for local testing.

bash

# HTTP mode (gateway default)
PORT=8080 MCP_TRANSPORT=http AUTH_MODE=gateway npm start

# stdio mode (env-baked, local testing)
MCP_TRANSPORT=stdio \
SALESFORCE_AUTH_FLOW=client_credentials \
SALESFORCE_CLIENT_ID=... SALESFORCE_CLIENT_SECRET=... \
SALESFORCE_INSTANCE_URL=https://yourorg.my.salesforce.com \
node dist/entry.js

Header contract (gateway mode)

Header	Required?	Notes
`X-Salesforce-Auth-Mode`	optional	`client_credentials` (default) or `username_password`.
`X-Salesforce-Client-Id`	for client_credentials	Connected App consumer key.
`X-Salesforce-Client-Secret`	for client_credentials	Connected App consumer secret.
`X-Salesforce-Instance-Url`	for client_credentials	Customer's My Domain URL (e.g. `https://acmecorp.my.salesforce.com`).
`X-Salesforce-Username`	for username_password	Salesforce user.
`X-Salesforce-Password`	for username_password	Salesforce password.
`X-Salesforce-Token`	for username_password	Security token (required unless IP allowlisted).

Per-request authentication means the same container instance can service many customers without restart — each MCP tools/call builds a fresh jsforce.Connection from the headers on that request.

Salesforce Connected App setup

For Client Credentials flow (the recommended path):

Salesforce Setup → App Manager → New Connected App.
Under API (Enable OAuth Settings): turn on Enable OAuth Settings and Enable Client Credentials Flow.
Save, wait ~5 minutes for propagation.
Manage → Edit Policies → Client Credentials Flow → set a Run As user (the API calls run with that user's permissions).
Copy the Consumer Key and Consumer Secret from the Connected App into the gateway BYOC fields as clientId and clientSecret.
Set instanceUrl to the customer's My Domain URL (Setup → My Domain).

Build

Terminal

npm install
npm run build

Container

Terminal

docker build -t salesforce-mcp:dev .
docker run --rm -p 8080:8080 -e MCP_TRANSPORT=http salesforce-mcp:dev
curl -s http://localhost:8080/health

The published image lives at ghcr.io/wyre-ai/salesforce-mcp with :latest, :sha-<short_sha>, and :v<version> tags.

License

Apache-2.0.

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Salesforce

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "salesforce": { "command": "npx", "args": ["-y", "Salesforce"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/salesforce?style=directory)](https://allmcps.com/mcp/salesforce)

HTML Embed

<a href="https://allmcps.com/mcp/salesforce"><img src="https://allmcps.com/api/badge/salesforce?style=directory" alt="Salesforce on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Salesforce →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

salesforce-mcp

MCP (Model Context Protocol) server for Salesforce CRM, scoped to the WYRE Gateway BYOC use case.

Scope discipline

Tools

Tool	Purpose
`salesforce_search_objects`	Find standard + custom objects by partial name.
`salesforce_describe_object`	Full schema (fields, picklists, relationships) for an object.
`salesforce_query_records`	Execute SOQL with relationship traversal.
`salesforce_aggregate_query`	SOQL GROUP BY / COUNT / SUM / AVG / MIN / MAX.
`salesforce_dml_records`	Insert / update / delete / upsert records.
`salesforce_search_all`	Cross-object SOSL search.

Run modes

http (default): listens on :8080, exposes /mcp (JSON-RPC) + /health. Per-request credentials from X-Salesforce-* headers. This is the gateway deployment shape.
stdio: traditional MCP client transport (Claude Desktop / Cursor). Credentials read once from env. Useful for local testing.

bash

# HTTP mode (gateway default)
PORT=8080 MCP_TRANSPORT=http AUTH_MODE=gateway npm start

# stdio mode (env-baked, local testing)
MCP_TRANSPORT=stdio \
SALESFORCE_AUTH_FLOW=client_credentials \
SALESFORCE_CLIENT_ID=... SALESFORCE_CLIENT_SECRET=... \
SALESFORCE_INSTANCE_URL=https://yourorg.my.salesforce.com \
node dist/entry.js

Header contract (gateway mode)

Header	Required?	Notes
`X-Salesforce-Auth-Mode`	optional	`client_credentials` (default) or `username_password`.
`X-Salesforce-Client-Id`	for client_credentials	Connected App consumer key.
`X-Salesforce-Client-Secret`	for client_credentials	Connected App consumer secret.
`X-Salesforce-Instance-Url`	for client_credentials	Customer's My Domain URL (e.g. `https://acmecorp.my.salesforce.com`).
`X-Salesforce-Username`	for username_password	Salesforce user.
`X-Salesforce-Password`	for username_password	Salesforce password.
`X-Salesforce-Token`	for username_password	Security token (required unless IP allowlisted).

Per-request authentication means the same container instance can service many customers without restart — each MCP tools/call builds a fresh jsforce.Connection from the headers on that request.

Salesforce Connected App setup

For Client Credentials flow (the recommended path):

Salesforce Setup → App Manager → New Connected App.
Under API (Enable OAuth Settings): turn on Enable OAuth Settings and Enable Client Credentials Flow.
Save, wait ~5 minutes for propagation.
Manage → Edit Policies → Client Credentials Flow → set a Run As user (the API calls run with that user's permissions).
Copy the Consumer Key and Consumer Secret from the Connected App into the gateway BYOC fields as clientId and clientSecret.
Set instanceUrl to the customer's My Domain URL (Setup → My Domain).

Build

Terminal

npm install
npm run build

Container

Terminal

docker build -t salesforce-mcp:dev .
docker run --rm -p 8080:8080 -e MCP_TRANSPORT=http salesforce-mcp:dev
curl -s http://localhost:8080/health

The published image lives at ghcr.io/wyre-ai/salesforce-mcp with :latest, :sha-<short_sha>, and :v<version> tags.

License

Apache-2.0.