Salesforce

Access and manage Salesforce CRM records, tasks, opportunities, and custom objects.

Stars

★ 12

Source

Official Registry

Updated

2026-09-29

// securityCaution

Requires keys· SALESFORCE_CLIENT_ID, SALESFORCE_CLIENT_SECRET, SALESFORCE_SANDBOX, SALESFORCE_ACCESS_TOKEN, SALESFORCE_INSTANCE_URL, SALESFORCE_CONFIG_DIR, SALESFORCE_OAUTH_PORT, SALESFORCE_OAUTH_SCOPES
Runs locally
Official / curated
Open source
Community-trusted

Summary

This Salesforce MCP tool requires multiple sensitive OAuth/access-token settings and runs a local server process to access Salesforce CRM data; these are typical capabilities for this class of tool, with no evidence here of exfiltration to unknown endpoints or clear overreach. It comes from an official registry, is open source, and has recent maintenance, so the overall posture is mostly caution rather than high risk.

CredentialsCaution

It requires SALESFORCE_CLIENT_ID, SALESFORCE_CLIENT_SECRET, SALESFORCE_ACCESS_TOKEN, SALESFORCE_INSTANCE_URL, and related settings, which are sensitive credentials that can directly access a Salesforce tenant; exposure through logs, environment variables, or config storage could enable misuse of CRM data.

Network egressCaution

No fixed remote host is listed, but the stated functionality plus INSTANCE_URL/OAuth settings indicate network communication with the relevant Salesforce instance, potentially transmitting accounts, contacts, opportunities, leads, tasks, and custom object data; there is no evidence here of sending data to unrelated or unknown endpoints.

Code executionCaution

The system checks show that it executes code / starts a local MCP server process, which is standard for this type of tool. The provided material does not indicate additional high-risk system capabilities or permission requests beyond what a Salesforce integration normally needs.

Data accessCaution

Per the description, it can access Salesforce CRM accounts, contacts, opportunities, leads, tasks, and custom objects, which is a broad business-data surface, and SALESFORCE_CONFIG_DIR suggests local config storage; this implies both CRM data access and possible local storage of auth/config state, but no clear access beyond the stated functionality is shown.

Supply chainCaution

It comes from an official registry, has a public source repository, and was updated within the last year, all of which are positive signals; however, the missing README, unspecified license, and 0 GitHub stars reduce confidence in auditability and maturity, so the supply-chain posture is best treated as caution rather than high risk.

Recommendations

Use least-privilege Salesforce OAuth scopes and avoid long-lived reuse of highly privileged access tokens.
Protect CLIENT_SECRET, ACCESS_TOKEN, and the config directory with proper secret management, and keep them out of logs, shell history, and repositories.
Prefer sandbox use for testing and verify that INSTANCE_URL points only to the intended Salesforce tenant.
Before installation, review the source implementation, dependency list, and license, and confirm that sensitive credentials are not stored in plaintext in the local config directory.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "Salesforce" MCP server from askskill:
Run: claude mcp add 'io-github-mindstone-mcp-server-salesforce' -- npx -y @mindstone/mcp-server-salesforce