Undominated.ai
← Explore all 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 ↗

“MCP Server for Interacting with Salesforce Orgs”

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.

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 ↗
  1. Authorize the intended org using the Salesforce CLI or its documented VS Code sign-in flow.
  2. Configure npx with @salesforce/mcp and the required --orgs value. Prefer a specific org identity, then select the needed --tools or --toolsets.
  3. 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

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Publisher README at reviewed revision ↗Checked

    https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/README.md

    Supports: summary, upstreamDescription, whySelected, bestFor, install, compatibility, limitations, access

  2. Source licence ↗Checked

    https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/LICENSE.txt

    Supports: license, access.cost

  3. Reviewed implementation: packages/mcp/src/index.ts ↗Checked

    https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/packages/mcp/src/index.ts

    Supports: review, limitations, access, transports

  4. Reviewed implementation: packages/mcp/src/sf-mcp-server.ts ↗Checked

    https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/packages/mcp/src/sf-mcp-server.ts

    Supports: review, limitations, access, transports

  5. Reviewed implementation: packages/mcp-provider-dx-core/src/tools/run_soql_query.ts ↗Checked

    https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/packages/mcp-provider-dx-core/src/tools/run_soql_query.ts

    Supports: review, limitations, access, transports

  6. Reviewed implementation: packages/mcp-provider-dx-core/src/tools/deploy_metadata.ts ↗Checked

    https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/packages/mcp-provider-dx-core/src/tools/deploy_metadata.ts

    Supports: review, limitations, access, transports

  7. Reviewed implementation: packages/mcp-provider-dx-core/src/tools/delete_org.ts ↗Checked

    https://github.com/salesforcecli/mcp/blob/426109382a73093e77a44c4dbeb95575b7317eb9/packages/mcp-provider-dx-core/src/tools/delete_org.ts

    Supports: review, limitations, access, transports