A simple MCP server with packaged tools, for each Salesforce API (REST, Tooling, GraphQL, etc.)
MCP Force MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Force directly instead of describing what you should do. A simple MCP server with packaged tools, for each Salesforce API (REST, Tooling, GraphQL, etc.).
This program provides an MCP (Model Context Protocol) server that exposes Salesforce APIs as tools for use in AI agents. It enables AI assistants like Claude Desktop and VS Code to interact with your Salesforce organization through natural language.
@rapidocloud/mcp-force on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 3 environment variables: SALESFORCE_ENDPOINT, SALESFORCE_ACCESS_TOKEN, PORT. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by RupertBarrow; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
{
"mcpServers": {
"force": {
"command": "npx",
"args": ["-y", "@rapidocloud/mcp-force"],
"env": {
"SALESFORCE_ENDPOINT": "your-value",
"SALESFORCE_ACCESS_TOKEN": "your-value",
"PORT": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SALESFORCE_ENDPOINT | Configuration value read at startup. | Optional |
| SALESFORCE_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| PORT | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.