
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 分