Salesforce DX MCP Server

Official

Official Salesforce DX toolset that lets LLMs read and operate on your authorized Salesforce orgs.

How to install ↓ Compare GitHub source repository ↗

Category: Dev Tools #108 of 438
Stars: ★ 484 Very popular
Transport: stdio (local process)
Runtime: Node.js
Credentials: API key / credential required
License: Apache-2.0
Last commit: 6 days ago
Tools: 89

61FMRS · C

An official, broad-coverage Salesforce developer MCP server with a large tool catalog, but it requires local CLI authorization and careful scoping of org access.

Strongest · Documentation 16/20 Weakest · Reliability 9/20

Reliability

9/20

Security and permissions

9/20

Maintenance

14/20

Documentation

16/20

Setup experience

13/20

Why each score

Reliability 9/20: Only the README was provided—no manifest, source code, test suite, or CI configuration—so declared tool behavior cannot be verified against real code. The README itself contains a minor internal inconsistency: a config example enables a tool via `--tools run_apex_test`, the surrounding prose calls it `run_apex_tests`, while the tool list registers it as `run_apex_test`, which could cause configuration confusion. With no executable evidence (tests, CI) present, the static calibration cap prevents a score above 12.
Security and permissions 9/20: The server exposes many tools with real-world side effects, including `deploy_metadata`, `delete_org`, `create_scratch_org`, `assign_permission_set`, and DevOps Center actions like `promote_devops_center_work_item`/`commit_devops_center_work_item`, any of which could have irreversible impact on a live org. Positively, the README requires explicit prior org authorization (`org login web`) and flags `ALLOW_ALL_ORGS` with a caution note. However, this material shows no explicit confirmation/second-step-approval mechanism or granular permission scoping for the dangerous tools—those details are deferred to an external doc not included here. Telemetry is on by default but clearly disclosed and can be disabled. The lack of visible confirmation flow for destructive operations is the main deduction, though the authorization prerequisite keeps this short of a red-line violation.
Maintenance 14/20: This is an officially maintained Salesforce project (salesforcecli/mcp, published to npm as @salesforce/mcp) with 457 stars, 33 open issues, an Apache-2.0 license, not archived, a dedicated release notes directory, and GitHub Issues/Discussions channels for feedback—signs of clear ownership and governance. However, the reviewed material lacks concrete evidence of recent commit activity, release cadence, or dependency update practices, so it falls short of a top score.
Documentation 16/20: The README is fairly comprehensive, with configuration examples for several mainstream clients (VS Code, Claude Code, Cline, Cursor, etc.), a full flags reference table, a toolsets overview table, and per-toolset tool listings with GA/NON-GA status and short descriptions. It lacks a troubleshooting section, cost/rate-limit disclosure, and defers key security details to an external doc not included in this review, creating a hidden assumption. There is also the minor `run_apex_test`/`run_apex_tests` naming inconsistency noted above.
Setup experience 13/20: Setup steps are clearly laid out: one-command install via `npx -y @salesforce/mcp`, with concrete JSON configuration snippets for multiple mainstream MCP clients and a clear prerequisite for org authorization. Per the static calibration rule, without verifiable execution evidence (CI plus committed tests covering key paths), the setup score cannot exceed 15; additionally, the flow depends on manual CLI-level org authentication outside the MCP config itself, adding some fragility.

Static review · not runListed 2026-08-26

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesUses the networkChanges third-party account data

Best for

Developers already using the Salesforce CLI and a DX project
Teams that want an AI coding assistant to operate directly on Salesforce metadata, Apex, and LWC
Projects migrating Aura to LWC or adopting DevOps Center workflows

Not for

Users without a local Salesforce CLI setup or any authorized org
Cases needing only trivial read-only lookups without wanting the context overhead of the broader toolset (can be trimmed via --toolsets, but the default footprint is still sizable)

Required permissions

Requires orgs to be pre-authorized locally via `sf org login web` or equivalent
Access is scoped per `--orgs`: specific orgs, the default org/Dev Hub, or (use with caution) all authorized orgs
Several tools have write access — deploying/retrieving metadata, creating or deleting scratch orgs, assigning permission sets, committing DevOps Center work items

Risks and side effects

`ALLOW_ALL_ORGS` grants the server access to every locally authorized org, which can expose production orgs if misconfigured
Tools like `deploy_metadata` and `delete_org` make real changes or deletions to orgs — misuse carries data/config risk
Telemetry is enabled by default; use `--no-telemetry` explicitly if privacy/compliance requires disabling it
`DEFAULT_TARGET_ORG`/`DEFAULT_TARGET_DEV_HUB` resolve dynamically on every tool call, so switching your local default org changes which org the server can act on

Setup

Before you start

Runtime：Node.js

Authorize the target org locally with the Salesforce CLI beforehand (sf org login web or the 'SFDX: Authorize an Org' command in your IDE).
Add a server entry to your MCP client's config file with command npx and args -y @salesforce/mcp plus flags such as --orgs (required, e.g. DEFAULT_TARGET_ORG) and --toolsets (e.g. orgs,metadata,data,users).
Optionally add --tools for specific extra tools, or --allow-non-ga-tools to enable preview tools.
Save and reload/restart your MCP client — npx will fetch and run @salesforce/mcp automatically (no manual install needed).
If something goes wrong, add --debug for debug logs (not all clients surface MCP logs).

.mcp.json

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

Shown for Claude Code. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.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"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add 'Salesforce DX' -- npx -y @salesforce/mcp --orgs DEFAULT_TARGET_ORG --toolsets orgs,metadata,data,users --tools run_apex_test --allow-non-ga-tools

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After connecting, tools such as run_soql_query and run_apex_test should appear in the client's tool list; asking "What is the username of my default org?" and getting the correct username confirms the connection.

Troubleshooting

Confirm the org is authorized via `sf org login web` or the IDE command, and that the username/alias/token passed to --orgs is correct
Check that --toolsets and --tools names match the documented values; if a tool is missing, check whether --allow-non-ga-tools is needed
Add --debug to see run logs, keeping in mind not every MCP client exposes them
Don't modify the `-y @salesforce/mcp` portion of the args or npx may fail to auto-install/update the package

Things to try

Once connected, you can ask your AI assistant things like:

Run all Apex tests in my default org and summarize the results
List all Salesforce orgs I have authorized on this machine
Run this SOQL query against my org: SELECT Id, Name FROM Account LIMIT 10
Scan my Apex class for performance antipatterns

Tools 89

get_username read-only

Determines the appropriate username or alias for Salesforce operations, handling both default orgs and Dev Hubs.

resume_tool_operation

Resumes a long-running operation that wasn't completed by another tool.

run_soql_query read-only

Runs a SOQL query against a Salesforce org.

check_devops_center_commit_status read-only

Checks the current status of a work item committed to DevOps Center.

checkout_devops_center_work_item writes

Checks out the branch associated with a selected work item by name.

commit_devops_center_work_item writes

Commits SFDX project changes and registers the commit SHA in DevOps Center.

create_devops_center_pull_request writes

Commits local changes to a DevOps Center work item's feature branch.

detect_devops_center_merge_conflict read-only

Detects merge conflicts for a selected work item or in a given source branch.

Show 81 more tools

list_devops_center_projects read-only

Lists all DevOps Center projects in a specific org.

list_devops_center_work_items read-only

Lists all the work items for a specific DevOps Center project.

create_devops_center_work_item writes

Creates a new DevOps Center work item in the selected project.

update_devops_center_work_item_status writes

Sets a work item's status to In Progress or Ready to Promote.

promote_devops_center_work_item writes

Promotes an approved work item to the next stage in the DevOps Center pipeline.

resolve_devops_center_deployment_failure writes

Diagnoses and resolves deployment failures.

resolve_devops_center_merge_conflict writes

Applies a selected resolution method to a merge conflict.

enrich_metadata writes

Enriches metadata from your org in your DX project.

create_aura_blueprint_draft read-only

Creates a comprehensive PRD blueprint for Aura component migration.

enhance_aura_blueprint_draft

Enhances an existing draft PRD with expert analysis and unknown resolution.

orchestrate_aura_migration

Orchestrates the complete Aura-to-LWC migration workflow end to end.

transition_prd_to_lwc read-only

Provides migration bridge guidance for creating LWC components from Aura specifications.

create-custom-rule writes

Creates a custom XPath-based PMD rule from a provided Apex code sample.

describe_code_analyzer_rule read-only

Gets the description of a Code Analyzer rule.

generate_xpath_prompt read-only

Builds the prompt that guides XPath authoring from AST context for custom rule creation.

list_code_analyzer_rules read-only

Selects Code Analyzer rules based on a number of criteria.

query_code_analyzer_results read-only

Queries a Code Analyzer results JSON file and returns filtered violations.

run_code_analyzer read-only

Performs static analysis against code for best practices, security, and performance issues.

create_lwc_component_from_prd

Creates complete LWC components from PRD specifications with proper structure and best practices.

create_lwc_jest_tests read-only

Generates Jest test suites for LWC components with coverage and mocking.

review_lwc_jest_tests read-only

Reviews and validates Jest test implementations for LWC components.

create_lightning_type read-only

Provides guidance for creating Custom Lightning Types (CLT) for apps, agent actions, LWC, and platform integrations.

explore_slds_blueprints read-only

Retrieves SLDS blueprint specifications by name, category, component, CSS class, or styling hook.

guide_design_general read-only

Provides SLDS guidelines and best practices for LWC covering accessibility and responsive design.

guide_component_accessibility read-only

Provides accessibility guidelines and testing instructions for LWC components.

guide_lwc_best_practices read-only

Offers LWC development best practices and coding standards guidance.

guide_lwc_development read-only

Provides LWC development workflow and implementation guidelines.

guide_lwc_rtl_support read-only

Provides Right-to-Left (RTL) internationalization support and development guidance.

guide_lws_security read-only

Provides security analysis per product security and Lightning Web Security guidelines.

guide_slds_blueprints read-only

Provides comprehensive SLDS blueprint guidelines, reference docs, and a category index.

guide_utam_generation

Provides UI Test Automation Model (UTAM) Page Object generation guidelines and best practices.

lwc-doc-error

Retrieves information about LWC error messages, including static guidance for resolving them.

reference_lwc_compilation_error

References LWC compilation errors against a knowledge base of documented patterns, causes, and fixes.

guide_slds_styling read-only

Retrieves SLDS styling hooks guidance and reference documentation.

explore_slds_styling read-only

Searches SLDS styling hooks with exact, fuzzy, prefix, and wildcard matching.

guide_lbc_usage read-only

Provides an index of Lightning Base Components with short descriptions to help pick the right one.

explore_lbc_components read-only

Returns full API documentation for given Lightning Base Component names.

create_lds_graphql_mutation_query read-only

Provides guidance for creating GraphQL mutation queries.

create_lds_graphql_read_query read-only

Creates GraphQL read queries for LDS.

explore_lds_uiapi read-only

Explores and documents Lightning Design System UI API capabilities.

fetch_lds_graphql_schema read-only

Fetches the GraphQL schema structure for LDS.

guide_lds_data_consistency read-only

Provides data consistency patterns and best practices for LDS components.

guide_lds_development read-only

Provides LDS development guidelines and component integration guidance.

guide_lds_graphql read-only

Provides LDS GraphQL usage patterns and guidelines.

guide_lds_referential_integrity read-only

Provides referential integrity patterns for LDS data management.

orchestrate_lds_data_requirements read-only

Provides step-by-step guidance for analyzing LDS data requirements into PRD-ready specs.

test_lds_graphql_query read-only

Tests a GraphQL query against a connected Salesforce org and returns the result.

guide_figma_to_lwc_conversion read-only

Converts Figma designs to LWC component specifications.

guide_lo_migration read-only

Provides guidance to convert a Lightning Out (beta) app into a Lightning Out 2.0 app.

run_lwc_accessibility_jest_tests read-only

Provides accessibility testing utilities and Jest integration for LWC components.

verify_aura_migration_completeness read-only

Provides an Aura-to-LWC migration completeness checklist and validation.

orchestrate_lwc_component_creation read-only

Provides guidance for the entire Aura-to-LWC migration process.

orchestrate_lwc_component_optimization read-only

Provides performance optimization and best practices for LWC components.

orchestrate_lwc_component_testing read-only

Provides comprehensive testing workflow and test generation guidance.

orchestrate_lwc_slds2_uplift read-only

Provides migration guidance for upgrading to SLDS 2.

validate_and_optimize read-only

Returns a validation runbook to run accessibility/security/best-practice validators, produce SARIF issues, and score results.

score_issues read-only

Computes a 0-100 readiness score and quality grade (draft, prototype, review-for-production) from SARIF issues.

deploy_metadata writes

Deploys metadata from your DX project to an org.

retrieve_metadata read-only

Retrieves metadata from your org to your DX project.

create_mobile_lwc_app_review read-only

Provides TypeScript API docs for the LWC App Review Service.

create_mobile_lwc_ar_space_capture read-only

Provides TypeScript API docs for LWC AR Space Capture.

create_mobile_lwc_barcode_scanner read-only

Provides TypeScript API docs for the LWC Barcode Scanner.

create_mobile_lwc_biometrics read-only

Provides TypeScript API docs for the LWC Biometrics Service.

create_mobile_lwc_calendar read-only

Provides TypeScript API docs for the LWC Calendar Service.

create_mobile_lwc_contacts read-only

Provides TypeScript API docs for the LWC Contacts Service.

create_mobile_lwc_document_scanner read-only

Provides TypeScript API docs for the LWC Document Scanner.

create_mobile_lwc_geofencing read-only

Provides TypeScript API docs for the LWC Geofencing Service.

create_mobile_lwc_location read-only

Provides TypeScript API docs for the LWC Location Service.

create_mobile_lwc_nfc read-only

Provides TypeScript API docs for the LWC NFC Service.

create_mobile_lwc_payments read-only

Provides TypeScript API docs for the LWC Payments Service.

get_mobile_lwc_offline_analysis read-only

Analyzes LWC components for mobile-specific issues and offline compatibility/performance recommendations.

get_mobile_lwc_offline_guidance read-only

Provides structured review instructions to detect and remediate mobile offline code violations in LWC components.

create_org_snapshot writes

Creates a scratch org snapshot.

create_scratch_org writes

Creates a scratch org.

delete_org destructive

Deletes a locally-authorized Salesforce scratch org or sandbox.

list_all_orgs read-only

Lists all configured Salesforce orgs, with optional connection status checking.

open_org read-only

Opens an org in a browser.

scan_apex_class_for_antipatterns read-only

Analyzes Apex class files for performance antipatterns and gives fix recommendations.

run_agent_test writes

Executes agent tests in your org.

run_apex_test writes

Executes Apex tests in your org.

assign_permission_set writes

Assigns a permission set to the user or on behalf of another user.

Use cases

Query, deploy, and retrieve Salesforce org metadata directly from an IDE or AI agent

Run SOQL queries, Apex tests, and agent tests and get results inline

Migrate Aura components to Lightning Web Components with expert guidance tools

Run static analysis (Code Analyzer) on Apex code and author custom rules

Manage DevOps Center work items and detect/resolve merge conflicts

Manage scratch org lifecycle and permission set assignments

Supported clients

Claude Code

GitHub Copilot

Cline

Cursor

TraePartial support

WindsurfPartial support

ZedPartial support

Listed from the project's documentation, not tested by this site.

Overview

The Salesforce DX MCP Server is maintained by the official salesforcecli GitHub organization and implements the Model Context Protocol so LLMs can securely interact with Salesforce orgs already authorized on your machine. Launched via npx @salesforce/mcp, it's configured with --orgs to scope which orgs are accessible and --toolsets/--tools to enable specific tool groups, spanning metadata deploy/retrieve, SOQL queries, Apex/agent testing, user and permission set management, scratch org lifecycle, DevOps Center work items, static code analysis (Code Analyzer), Aura-to-LWC migration experts, and mobile LWC capability documentation across more than sixty tools. Only generally-available (GA) tools are enabled by default; the --allow-non-ga-tools flag is required to use tools still in preview.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →

NPM Sentinel MCP Server 79 · B

AI-powered NPM package analysis MCP server

★ 18 · Tools 19 Compare with this →

MartinLoop MCP Server 79 · B

An independent control layer that gives AI coding agents budgets, brakes, and receipts

★ 410 Compare with this →

GitHub MCP Server 76 · B

GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language

★ 33.5k · Tools 15 Compare with this →

Compare with other MCP servers

Source revision 9bc98ba22f0e Data synced 2026-10-12 Read the FMRS scoring method