--- title: "Salesforce DX MCP: review, setup & limitations · Undominated.ai" canonical: https://undominated.ai/mcp-servers/salesforce/ description: "A local Salesforce development connector scoped to explicitly authorized orgs, toolsets and individual tools." --- # Salesforce DX MCP: review, setup & limitations · Undominated.ai > A local Salesforce development connector scoped to explicitly authorized orgs, toolsets and individual tools. [← Explore all mcp servers](/mcp-servers/) BUSINESS SYSTEMS AND DEVELOPMENT / Salesforce # Salesforce DX MCP A local Salesforce development connector scoped to explicitly authorized orgs, toolsets and individual tools. See setup guidance ↓Original source ↗ SOURCE REVIEW Reviewed 2026-09-22 Evidence 7 linked sources Publisher Salesforce Licence Apache-2.0 ↗ Revision 426109382a73 Read what was—and wasn’t—checked ↓ “MCP Server for Interacting with Salesforce Orgs” Salesforce · upstream description ↗ Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Makes the allowed Salesforce orgs explicit in server configuration. - Supports selecting toolsets and individual tools, with non-GA tools disabled unless deliberately enabled. ### A good fit for - Inspecting a Salesforce development org and running bounded SOQL queries - Reviewing and performing authorized metadata or Apex development tasks ### Weigh up before choosing - Core tools are always available; selecting an additional tool is not a guarantee that it is the only exposed operation. - Default-target aliases can resolve differently as workspace settings change. Use an explicit authorized org identity when a fixed destination matters. - Deployment and some org-management tools mutate remote state. Telemetry is enabled unless --no-telemetry is set; non-GA operations need an additional opt-in. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - README configuration and permission sections - Package and server startup declarations - run_soql_query, deploy_metadata and delete_org handlers - LICENSE.txt notice ### Our findings - The org selection rules distinguish fixed identities from dynamic default targets. - The reviewed query, metadata deployment and org deletion handlers show why the connector must not be labelled read-only. ### Not established by this review - No MCP server or upstream package was installed or run. - No authenticated account, API request, client handshake or write operation was tested. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Connect a server deliberately. Upstream setup instructions ↗ - Authorize the intended org using the Salesforce CLI or its documented VS Code sign-in flow. - Configure npx with @salesforce/mcp and the required --orgs value. Prefer a specific org identity, then select the needed --tools or --toolsets. - Use --no-telemetry if that matches the team’s policy. Leave --allow-non-ga-tools off unless the additional operations were reviewed. ### Before you start - Supported Node.js/npm and Salesforce CLI authentication - A Salesforce org with appropriate user permissions - A client configuration that uses the publisher’s actual flag names ### Compatibility Claude Code · Cline · Cursor · VS Code ### Implementation TypeScript ### Transports stdio ### Local MCP process with service access - Read data through authorized org APIs - Selected tools can deploy metadata, run tests or administer org resources - Core tools remain registered; account permissions and client approvals still matter ### Cost model Apache-2.0-licensed connector; Salesforce accounts, features, API limits and model usage remain separate. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - Publisher README at reviewed revision ↗ Checked 2026-09-22 https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/README.md Supports: summary, upstreamDescription, whySelected, bestFor, install, compatibility, limitations, access - Source licence ↗ Checked 2026-09-22 https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/LICENSE.txt Supports: license, access.cost - Reviewed implementation: packages/mcp/src/index.ts ↗ Checked 2026-09-22 https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/packages/mcp/src/index.ts Supports: review, limitations, access, transports - Reviewed implementation: packages/mcp/src/sf-mcp-server.ts ↗ Checked 2026-09-22 https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/packages/mcp/src/sf-mcp-server.ts Supports: review, limitations, access, transports - Reviewed implementation: packages/mcp-provider-dx-core/src/tools/run_soql_query.ts ↗ Checked 2026-09-22 https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/packages/mcp-provider-dx-core/src/tools/run_soql_query.ts Supports: review, limitations, access, transports - Reviewed implementation: packages/mcp-provider-dx-core/src/tools/deploy_metadata.ts ↗ Checked 2026-09-22 https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/packages/mcp-provider-dx-core/src/tools/deploy_metadata.ts Supports: review, limitations, access, transports - Reviewed implementation: packages/mcp-provider-dx-core/src/tools/delete_org.ts ↗ Checked 2026-09-22 https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/packages/mcp-provider-dx-core/src/tools/delete_org.ts Supports: review, limitations, access, transports [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)