Salesforce CLI MCP Server

The Salesforce DX MCP Server is the official Model Context Protocol implementation from the Salesforce CLI team, exposing the Salesforce developer toolchain to LLM clients like VS Code Copilot, Claude Code, Cursor, and Cline. It builds on the local Salesforce CLI auth state, so agents act on orgs you have already authorized rather than handling credentials themselves.

The server ships with 60+ tools grouped into toolsets: core, orgs, metadata, data, users, testing, code-analysis, lwc-experts, aura-experts, mobile, mobile-core, devops, enrichment, scale-products, and experts-validation. This covers running SOQL queries, deploying and retrieving metadata, running Apex and agent tests, scanning code with Code Analyzer, scaffolding and reviewing Lightning Web Components, migrating Aura to LWC, generating mobile LWC integrations, and driving DevOps Center work items and pull requests.

Because enabling all tools at once can overwhelm an LLM context window, the server requires you to scope access via the --orgs, --toolsets, and --tools flags, with an experimental --dynamic-tools mode that loads tools on demand. It is currently distributed as a pilot/beta service under Salesforce Beta Services Terms.

Tools

Prerequisites

• Node.js with npx available
• Salesforce CLI installed locally
• At least one authorized org. Run one of:
  • sf org login web from the Salesforce CLI
  • SFDX: Authorize an Org from the VS Code command palette

Install

The server is distributed as the npm package @salesforce/mcp and is typically run via npx:

npx -y @salesforce/mcp --orgs DEFAULT_TARGET_ORG --toolsets orgs,metadata,data,users

MCP client configuration

VS Code (.vscode/mcp.json):

{
  "servers": {
    "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"
      ]
    }
  }
}

Claude Code / Cursor / Cline use the same command and args under their respective mcpServers (Claude Code) or servers (Cursor, Cline) keys in .mcp.json, mcp.json, or cline_mcp_settings.json.

Flags

• --orgs (required): one or more of DEFAULT_TARGET_ORG, DEFAULT_TARGET_DEV_HUB, ALLOW_ALL_ORGS, or an org username/alias
• --toolsets: comma-separated list of toolset names to enable (core is always on)
• --tools: enable specific individual tool names
• --allow-non-ga-tools: opt in to experimental, non-GA tools
• --dynamic-tools: load tools on demand (experimental, VS Code and Cline only)
• --no-telemetry: disable telemetry
• --debug: enable debug logging

• Query production and sandbox orgs with natural language that compiles to SOQL, returning records via run_soql_query.
• Deploy and retrieve metadata between local source and orgs during feature work, using deploy_metadata and retrieve_metadata.
• Run Apex tests and Code Analyzer scans on a branch before opening a pull request, using run_apex_test and run_code_analyzer.
• Scaffold and review Lightning Web Components, including Jest tests and LDS GraphQL queries, from PRDs or Figma designs.
• Drive DevOps Center work items end to end: create the item, commit, open a PR, promote stages, and resolve deployment failures.

• "Run a SOQL query against my default org to list the 20 most recently modified Accounts with their Owner."
• "Deploy the force-app/main/default/classes folder to my staging org and run all local Apex tests."
• "Retrieve the Account and Contact custom fields from production into this project."
• "Generate an LWC called caseTriagePanel from this PRD and create Jest tests for it."
• "Create a DevOps Center work item titled Fix Opportunity rollup, commit my changes, and open a pull request."

• Official server maintained by the Salesforce CLI team under salesforcecli/mcp.
• Very broad surface area: 60+ tools across metadata, data, testing, code analysis, LWC, Aura migration, mobile, and DevOps Center.
• Reuses existing Salesforce CLI org auth, so the LLM never sees credentials.
• Granular scoping via --orgs, --toolsets, and --tools to keep context manageable.

• Pilot/beta status with Beta Services Terms; some tools are explicitly non-GA and require --allow-non-ga-tools.
• Enabling all toolsets can overwhelm an LLM's context window, so users must hand-pick toolsets.
• Requires a local Salesforce CLI install plus pre-authorized orgs; not a zero-setup remote server.
• Experimental --dynamic-tools mode currently only works in VS Code and Cline.

• smn2gnt/MCP-Salesforce and other community Salesforce MCP servers focused on SOQL and basic CRUD.
• Direct use of the Salesforce CLI (sf) from an agent shell, without MCP.
• HubSpot or Zoho MCP servers if the underlying need is general CRM access rather than Salesforce-specific dev tooling.