← 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.

“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.md at 9bc98ba22f0efe4a901904db7d0c76ebdf09525d: end-of-life notice, configuration, client examples, flags, orgs, toolsets and tools
  • packages/mcp/package.json, packages/mcp/src/index.ts and packages/mcp/src/sf-mcp-server.ts at 9bc98ba22f0efe4a901904db7d0c76ebdf09525d
  • run_soql_query, deploy_metadata and delete_org handlers at 9bc98ba22f0efe4a901904db7d0c76ebdf09525d
  • LICENSE.txt at 9bc98ba22f0efe4a901904db7d0c76ebdf09525d
  • Issue forcedotcom/mcp#46 (End of Life: November 2nd, 2026), read 2026-10-13

Our findings

  • The org selection rules distinguish fixed identities from dynamic default targets; the README says DEFAULT_TARGET_ORG is resolved on every tool call.
  • The reviewed query, metadata deployment and org deletion handlers show why the connector must not be labelled read-only: run_soql_query is annotated readOnlyHint, deploy_metadata destructiveHint.
  • The always-enabled core toolset is get_username and resume_tool_operation; delete_org, create_scratch_org and open_org in the orgs toolset are NON-GA and need --allow-non-ga-tools.
  • Issue #46 (opened 2026-10-05) says that after November 2, 2026 no further releases ship, salesforcecli/mcp will be archived, and pinned installs (0.30.15) keep working.
  • configExample is the README's Claude Code block at 9bc98ba2; it passes --allow-non-ga-tools, which the README says also enables non-GA tools in the chosen toolsets.
  • Re-pinned from 426109382a73093e77a44c4dbeb95575b7317eb9 to 9bc98ba22f0efe4a901904db7d0c76ebdf09525d; the README diff adds only the end-of-life notice. Package @salesforce/mcp and the Apache-2.0 LICENSE.txt are unchanged.

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. The README gives no install command: clients launch npx -y @salesforce/mcp from their MCP config. Note the November 2, 2026 end of life before adopting it.
  2. Authorize the intended org using the Salesforce CLI or its documented VS Code sign-in flow.
  3. Configure npx with @salesforce/mcp and the required --orgs value. Prefer a specific org identity, then select the needed --tools or --toolsets.
  4. 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

  • Node.js 20 or newer (packages/mcp/package.json engines) and Salesforce CLI authentication
  • A Salesforce org with appropriate user permissions
  • A client configuration that uses the publisher's actual flag names

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "Salesforce DX": {
      "command": "npx",
      "args": [
        "-y",
        "@salesforce/mcp",
        "--orgs",
        "DEFAULT_TARGET_ORG",
        "--toolsets",
        "orgs,metadata,data,users",
        "--tools",
        "run_apex_test",
        "--allow-non-ga-tools"
      ]
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

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

  1. https://github.com/salesforcecli/mcp/blob/9bc98ba22f0efe4a901904db7d0c76ebdf09525d/README.md

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

  2. Source licence ↗Checked

    https://github.com/salesforcecli/mcp/blob/9bc98ba22f0efe4a901904db7d0c76ebdf09525d/LICENSE.txt

    Supports: license, access.cost

  3. https://github.com/salesforcecli/mcp/blob/9bc98ba22f0efe4a901904db7d0c76ebdf09525d/packages/mcp/src/index.ts

    Supports: review, limitations, access, transports

  4. https://github.com/salesforcecli/mcp/blob/9bc98ba22f0efe4a901904db7d0c76ebdf09525d/packages/mcp/src/sf-mcp-server.ts

    Supports: review, limitations, access, transports

  5. https://github.com/salesforcecli/mcp/blob/9bc98ba22f0efe4a901904db7d0c76ebdf09525d/packages/mcp-provider-dx-core/src/tools/run_soql_query.ts

    Supports: review, limitations, access, transports

  6. https://github.com/salesforcecli/mcp/blob/9bc98ba22f0efe4a901904db7d0c76ebdf09525d/packages/mcp-provider-dx-core/src/tools/deploy_metadata.ts

    Supports: review, limitations, access, transports

  7. https://github.com/salesforcecli/mcp/blob/9bc98ba22f0efe4a901904db7d0c76ebdf09525d/packages/mcp-provider-dx-core/src/tools/delete_org.ts

    Supports: review, limitations, access, transports

  8. https://github.com/forcedotcom/mcp/issues/46

    Supports: limitations, review

  9. https://github.com/salesforcecli/mcp/blob/9bc98ba22f0efe4a901904db7d0c76ebdf09525d/packages/mcp/package.json

    Supports: install, language

Evidence & Ask