Is Salesforce DX MCP official?
Yes. Salesforce documents the Salesforce DX MCP Server as the @salesforce/mcp npm package, with a GitHub repository for the implementation.
CRMFreeactiveReviewed by MCPIndex
Salesforce DX MCP Server
Connects AI assistants to Salesforce orgs for metadata, development, deployment, and administrative DX workflows.
Looking for more MCP servers? Browse the full MCP tools directory or explore more tools in CRM.
Quick overview
Salesforce DX MCP changes the unit of control from a copied CLI command to an org-aware agent workflow where authentication, project context, metadata, org aliases, source tracking, and deployment state intersect. Its architectural value is that an assistant can reason over Salesforce DX project structure, org permissions, metadata types, and deployment operations without asking a developer to assemble the context manually. The hidden risk is that an apparently harmless “deploy this” or “fix this metadata” request can target the wrong org, sandbox, package directory, or source-tracked state. Use the official Salesforce DX MCP server through the @salesforce/mcp package, configure only approved toolsets, and require org alias, org ID, project root, package directory, and deployment plan before state-changing operations. A silent failure occurs when the CLI is authenticated successfully but selects a different default org or project root than the operator expects; the operation can succeed while modifying a sandbox or production org unintentionally. Require every response to expose org alias, org ID, username, project directory, package.xml or source path, test level, and validation mode before deploy or metadata mutation. Salesforce DX MCP should be treated as an org administration and development control surface, not a generic CRM query connector.
What this MCP server is best for
- Salesforce DX MCP Server is useful when you want to extend an AI assistant with real tools and live system access.
- It helps move from chat-only answers to real actions such as reading data, managing systems, or retrieving current information.
- It is best for developer and technical workflows where AI needs controlled access to external tools or services.
When to choose it
Choose Salesforce DX MCP Server when you want an MCP server focused on CRM and need tighter integration with your existing tools.
Good fit
salesforcesalesforce-dxmetadatacrmdevelopment
Salesforce DX MCP Server Configuration
Use the following configuration as a starting point for Claude Desktop or any compatible MCP client, then replace placeholder credentials with your own values.
claude_desktop_config.json
{
"mcpServers": {
"salesforce-dx": {
"command": "npx",
"args": ["-y", "@salesforce/mcp"],
"env": {
"SFDX_PROJECT_PATH": "/path/to/sfdx-project"
}
}
}
}How to set up Salesforce DX MCP Server
These setup steps cover the typical installation flow for this MCP server.
- 1
Install Salesforce CLI and authenticate only the org aliases required for the development workflow.
- 2
Install the official Salesforce DX MCP server with npx -y @salesforce/mcp.
- 3
Configure the MCP client in a specific Salesforce DX project and restrict enabled toolsets to the required org and metadata operations.
- 4
Verify org alias, org ID, username, project root, source-tracked state, and package directories before running a tool.
- 5
Begin with read-only org and metadata inspection, then use validation or dry-run deployment modes before destructive or production changes.
- 6
Pro-Tip: Never let the agent rely on the CLI's default org alone; require org alias, org ID, project root, package directory, test level, and a reviewed deployment plan before metadata changes.
Frequently asked questions
Common questions for Salesforce DX MCP Server.
Can it deploy metadata?
Yes, subject to the enabled tools, authenticated org permissions, project configuration, and deployment workflow. Production deployments should require explicit approval and validation.
What is a silent failure in Salesforce DX MCP?
The server can use a valid default org or project root that differs from the intended target. Fix it by requiring org alias, org ID, username, project path, package directory, and source-tracking state.
How should destructive metadata changes be governed?
Use sandbox-first validation, deployment plans, test levels, change sets or source reviews, and human approval before destructive or production operations.
Salesforce DX MCP Server vs Competitors
| Feature | Salesforce DX MCP Server | Competitor |
|---|---|---|
| Org-Aware Development | ✅ Connects Salesforce DX project, org, metadata, and deployment context | ❌ Generic CRM API connector |
| Metadata Operations | ✅ Supports source-tracked metadata and Salesforce DX workflows | ❌ Manual org browser exports |
| Deployment Governance | ✅ Can expose org, project, package, test, and validation context | ❌ Unreviewed one-off CLI automation |
| Toolset Control | ✅ Can enable selected MCP toolsets rather than a broad org identity | ❌ Shared administrator Salesforce sessions |