
Crmcloud
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Salesforce org access: SOQL queries, SOSL search, SObject CRUD, limits, and user info.
Overview
Crmcloud's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Crmcloud in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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.
Source: README.md at commit 11643f4
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts