Salesforce

Name: Salesforce
Author: wyre-technology

作者：wyre-technology版本 1.0.3i★ –i在你的电脑上运行

注册名称io.github.wyre-technology/salesforce-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 营销与社交媒体
你需要填写：AUTH_MODE, SALESFORCE_CLIENT_ID, SALESFORCE_CLIENT_SECRET, SALESFORCE_INSTANCE_URL, SALESFORCE_PASSWORD, SALESFORCE_TOKEN

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： AUTH_MODE, SALESFORCE_AUTH_FLOW, SALESFORCE_CLIENT_ID, SALESFORCE_CLIENT_SECRET, SALESFORCE_INSTANCE_URL, SALESFORCE_USERNAME, SALESFORCE_PASSWORD, SALESFORCE_TOKEN, MCP_TRANSPORT, LOG_LEVEL

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

Docker已安装 Docker

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "salesforce": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "AUTH_MODE",
        "-e",
        "SALESFORCE_AUTH_FLOW",
        "-e",
        "SALESFORCE_CLIENT_ID",
        "-e",
        "SALESFORCE_CLIENT_SECRET",
        "-e",
        "SALESFORCE_INSTANCE_URL",
        "-e",
        "SALESFORCE_USERNAME",
        "-e",
        "SALESFORCE_PASSWORD",
        "-e",
        "SALESFORCE_TOKEN",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-technology/salesforce-mcp:v1.0.3"
      ],
      "env": {
        "AUTH_MODE": "your-value",
        "SALESFORCE_AUTH_FLOW": "your-value",
        "SALESFORCE_CLIENT_ID": "your-value",
        "SALESFORCE_CLIENT_SECRET": "your-value",
        "SALESFORCE_INSTANCE_URL": "your-value",
        "SALESFORCE_USERNAME": "your-value",
        "SALESFORCE_PASSWORD": "your-value",
        "SALESFORCE_TOKEN": "your-value",
        "MCP_TRANSPORT": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add salesforce --env AUTH_MODE=your-value --env SALESFORCE_AUTH_FLOW=your-value --env SALESFORCE_CLIENT_ID=your-value --env SALESFORCE_CLIENT_SECRET=your-value --env SALESFORCE_INSTANCE_URL=your-value --env SALESFORCE_USERNAME=your-value --env SALESFORCE_PASSWORD=your-value --env SALESFORCE_TOKEN=your-value --env MCP_TRANSPORT=your-value --env LOG_LEVEL=your-value -- docker run -i --rm -e AUTH_MODE -e SALESFORCE_AUTH_FLOW -e SALESFORCE_CLIENT_ID -e SALESFORCE_CLIENT_SECRET -e SALESFORCE_INSTANCE_URL -e SALESFORCE_USERNAME -e SALESFORCE_PASSWORD -e SALESFORCE_TOKEN -e MCP_TRANSPORT -e LOG_LEVEL ghcr.io/wyre-technology/salesforce-mcp:v1.0.3

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "salesforce": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "AUTH_MODE",
        "-e",
        "SALESFORCE_AUTH_FLOW",
        "-e",
        "SALESFORCE_CLIENT_ID",
        "-e",
        "SALESFORCE_CLIENT_SECRET",
        "-e",
        "SALESFORCE_INSTANCE_URL",
        "-e",
        "SALESFORCE_USERNAME",
        "-e",
        "SALESFORCE_PASSWORD",
        "-e",
        "SALESFORCE_TOKEN",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-technology/salesforce-mcp:v1.0.3"
      ],
      "env": {
        "AUTH_MODE": "your-value",
        "SALESFORCE_AUTH_FLOW": "your-value",
        "SALESFORCE_CLIENT_ID": "your-value",
        "SALESFORCE_CLIENT_SECRET": "your-value",
        "SALESFORCE_INSTANCE_URL": "your-value",
        "SALESFORCE_USERNAME": "your-value",
        "SALESFORCE_PASSWORD": "your-value",
        "SALESFORCE_TOKEN": "your-value",
        "MCP_TRANSPORT": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "salesforce": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "AUTH_MODE",
        "-e",
        "SALESFORCE_AUTH_FLOW",
        "-e",
        "SALESFORCE_CLIENT_ID",
        "-e",
        "SALESFORCE_CLIENT_SECRET",
        "-e",
        "SALESFORCE_INSTANCE_URL",
        "-e",
        "SALESFORCE_USERNAME",
        "-e",
        "SALESFORCE_PASSWORD",
        "-e",
        "SALESFORCE_TOKEN",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-technology/salesforce-mcp:v1.0.3"
      ],
      "env": {
        "AUTH_MODE": "your-value",
        "SALESFORCE_AUTH_FLOW": "your-value",
        "SALESFORCE_CLIENT_ID": "your-value",
        "SALESFORCE_CLIENT_SECRET": "your-value",
        "SALESFORCE_INSTANCE_URL": "your-value",
        "SALESFORCE_USERNAME": "your-value",
        "SALESFORCE_PASSWORD": "your-value",
        "SALESFORCE_TOKEN": "your-value",
        "MCP_TRANSPORT": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

AUTH_MODE 必填 env
Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway. Set to 'env' for stdio/local use.
SALESFORCE_AUTH_FLOW env
Salesforce auth flow: 'client_credentials' (default, requires a Connected App with Client Credentials Flow enabled) or 'username_password' (fallback).
SALESFORCE_CLIENT_ID 必填 env
Connected App consumer key. Required when SALESFORCE_AUTH_FLOW=client_credentials.
SALESFORCE_CLIENT_SECRET 机密必填 env
Connected App consumer secret. Required when SALESFORCE_AUTH_FLOW=client_credentials.
SALESFORCE_INSTANCE_URL 必填 env
Salesforce org's My Domain URL (e.g. https://yourorg.my.salesforce.com). Required when SALESFORCE_AUTH_FLOW=client_credentials.
SALESFORCE_USERNAME env
Salesforce username. Only used when SALESFORCE_AUTH_FLOW=username_password.
SALESFORCE_PASSWORD 机密 env
Salesforce password. Only used when SALESFORCE_AUTH_FLOW=username_password.
SALESFORCE_TOKEN 机密 env
Salesforce security token. Only used when SALESFORCE_AUTH_FLOW=username_password; optional if the org has IP allowlisting configured instead.
MCP_TRANSPORT env
Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
LOG_LEVEL env
Log verbosity: debug, info, warn, error

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 wyre-technology 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“营销与社交媒体”中的其他服务器比较i

星标数多于此分类中其他 3588 个服务器的 0%
发布到注册中心的时间比此分类中其他 3588 个服务器的 26% 更新
基础检查结果等于或优于此分类中其他 3588 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Salesforce 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：AUTH_MODE, SALESFORCE_CLIENT_ID, SALESFORCE_CLIENT_SECRET, SALESFORCE_INSTANCE_URL, SALESFORCE_PASSWORD, SALESFORCE_TOKEN

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.0.3）于3个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它？

同一分类中有：MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

MCP YouTube Transcript

作者：jkawamoto

An MCP server retrieving transcripts of YouTube videos

在你的电脑上运行★ 495MIT11天前更新

安装

Google Analytics MCP

作者：surendranb

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

在你的电脑上运行★ 244MIT10天前更新

安装

BibiGPT YouTube Video Summarizer

作者：JimmyLv

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

在云端运行★ 137MIT11天前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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. HTTP refuses to start unless CONDUIT_S2S_SECRET is a real secret.
`stdio`: traditional MCP client transport (Claude Desktop / Cursor). Credentials read once from env. The stdio transport does not use CONDUIT_S2S_SECRET.

Copy .env.example and set the variables below. Leave CONDUIT_S2S_SECRET empty in that file.

Variable	Required	Description
`SALESFORCE_CLIENT_ID` / `SALESFORCE_CLIENT_SECRET` / `SALESFORCE_INSTANCE_URL`	For stdio and `AUTH_MODE=env`	Client Credentials flow.
`SALESFORCE_USERNAME` / `SALESFORCE_PASSWORD` / `SALESFORCE_TOKEN`	For username-password	Used when `SALESFORCE_AUTH_FLOW=username_password`. The token is optional if the org uses IP allowlisting.
`MCP_TRANSPORT`	No	`http` (default) or `stdio`.
`AUTH_MODE`	No	`gateway` (image and Compose default) or `env`. Gateway mode requires the `X-Salesforce-` headers on each `/mcp` request and never falls back to `SALESFORCE_`. `env` uses those variables only after S2S auth succeeds.
`CONDUIT_S2S_SECRET`	Yes for HTTP	Service-to-service secret. HTTP logs an error and exits non-zero when this is empty or a known placeholder (`changeme`, `placeholder`, `your-s2s-secret`, `secret`, `password`, `test`, an unresolved `${...}` template, and the other stand-ins in `src/s2s-verify.ts`). Never commit a real value.
`MCP_ALLOW_INSECURE_DEV`	No	Set to exactly `1` only for local development to start HTTP without `CONDUIT_S2S_SECRET`. The process logs a warning, does not check `X-Gateway-S2S`, and listens on `127.0.0.1` only. A non-loopback `MCP_HTTP_HOST` is ignored and the override is logged. A known placeholder secret still refuses to start.
`MCP_HTTP_HOST`	No	Bind address when a usable `CONDUIT_S2S_SECRET` is set. When unset, a configured secret keeps `HOST` (default `0.0.0.0`). Without a usable secret the listener is `127.0.0.1`. The container image sets `0.0.0.0`.
`PORT`	No	HTTP port. Defaults to `8080`.
`HOST`	No	Fallback bind address when `MCP_HTTP_HOST` is unset and a secret is configured. Defaults to `0.0.0.0`.

/health stays unauthenticated and does not read credentials.

# HTTP mode (exits unless CONDUIT_S2S_SECRET is a real secret)

CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" PORT=8080 MCP_TRANSPORT=http AUTH_MODE=gateway npm start

Local HTTP only, without a service-to-service secret (always binds 127.0.0.1)

MCP_ALLOW_INSECURE_DEV=1 MCP_TRANSPORT=http npm start

stdio mode (env-baked, local testing; no S2S secret)

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)

Every /mcp request must include a valid X-Gateway-S2S header when CONDUIT_S2S_SECRET is set. Gateway mode also requires the credential headers for the chosen flow. A request missing them returns 401 and does not fall back to SALESFORCE_* in the process environment.

Header	Required?	Notes
`X-Gateway-S2S`	Yes when the S2S secret is set	`t= ,v1=` . See X-Gateway-S2S signing.
`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.

X-Gateway-S2S signing

v1 is HMAC-SHA256, hex-encoded, of the ASCII string t= (the same t= prefix that starts the header), keyed with CONDUIT_S2S_SECRET. The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns HTTP 401. The secret is never written to logs or the response body.

t=$(date +%s)

v1=$(printf 't=%s' "$t" | openssl dgst -sha256 -hmac "$CONDUIT_S2S_SECRET" | awk '{print $NF}') curl -sS http://127.0.0.1:8080/mcp \ -H "content-type: application/json" \ -H "accept: application/json, text/event-stream" \ -H "X-Gateway-S2S: t=${t},v1=${v1}" \ -H "X-Salesforce-Client-Id: ..." \ -H "X-Salesforce-Client-Secret: ..." \ -H "X-Salesforce-Instance-Url: https://yourorg.my.salesforce.com" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

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

npm install

npm run build

Container

The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode, Salesforce credentials arrive on each request as headers; they are not read from the environment.

docker build -t salesforce-mcp:dev .

docker run --rm \ -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \ -p 127.0.0.1:8080:8080 \ salesforce-mcp:dev curl -s http://127.0.0.1:8080/health

Compose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, publishes 127.0.0.1:8080:8080, and does not inject SALESFORCE_*:

CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up

Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses SALESFORCE_*:

docker run --rm \

-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \ -e AUTH_MODE=env \ -e SALESFORCE_AUTH_FLOW=client_credentials \ -e SALESFORCE_CLIENT_ID=your-value \ -e SALESFORCE_CLIENT_SECRET=your-value \ -e SALESFORCE_INSTANCE_URL=https://yourorg.my.salesforce.com \ -p 127.0.0.1:8080:8080 \ salesforce-mcp:dev

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

License

Apache-2.0.