
Crmcloud
io.github.CloudCorpRecords由 GitHub 帳號 CloudCorpRecords 發布v0.1.0更新於 Nov 3, 2026
Salesforce org 存取:SOQL 查詢、SOSL 搜尋、SObject CRUD、限制以及使用者資訊。
AI 翻譯由 AI 模型根據下方的原文描述翻譯,可能有誤。
原文描述
Salesforce org access: SOQL queries, SOSL search, SObject CRUD, limits, and user info.
概覽
Crmcloud 的本機 MCP 服務;無需登入;STDIO。
暫無 AI 概覽:以下資訊來自註冊中心條目和服務本身。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Crmcloud,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
crmcloud
crmcloud is a thin, honest window into one Salesforce org. Everything in an org hangs off the same few shapes — SObjects with fields, records addressed by type and ID, SOQL for asking questions, SOSL for searching across objects — and crmcloud maps those shapes directly: run a query, run a search, list and describe the objects, then create, read, update, and delete records, with org limits and the current user's identity alongside. One binary serves a command-line interface and a stdio MCP server.
Two environment variables configure every call:
SALESFORCE_INSTANCE_URL— your org's instance URL, for examplehttps://your-org.my.salesforce.com(a trailing slash is fine).SALESFORCE_ACCESS_TOKEN— an access token for that org, sent as anAuthorization: Bearerheader and never printed.
When either variable is missing, every call fails before any request
is made, with an error that names the missing variable. Data calls go
to <instance>/services/data/v59.0; the user-info call goes to
<instance>/services/oauth2/userinfo, where Salesforce puts it.
This is a core subset on purpose: org and scratch-org management,
Apex and Lightning tooling, metadata deploy/retrieve, and bulk data
import/export — the parts of the wider Salesforce tooling world that
drive the sf CLI — are not included. crmcloud covers the REST data
surface only.
Install
Or run the container image:
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
CLI
Each command prints the upstream JSON payload. Salesforce answers
updates and deletes with an empty 204, so those two commands print
a small {"success": true, "id": ..., "sobject": ...} confirmation
instead. Exit codes: 0 on success, 1 when a call fails (including
a missing environment variable or an API error), 2 for usage
errors.
MCP server
One bin serves both faces. The mcp subcommand starts a stdio MCP
server:
MCP client configuration:
Tools
API errors surface the HTTP status plus Salesforce's own error message and error code when the org returns them.
Development
License
MIT — see LICENSE.
來源:README.md,提交 11643f4
工具
0版本歷史
1- v0.1.0最新Nov 3, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分