Salesforce DX MCP Server
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
- 487 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Changes metadata and data in Salesforce orgs
- Uses local Salesforce CLI authorizations
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/salesforce-dx-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Changes metadata and data in Salesforce orgs
- Uses local Salesforce CLI authorizations
This is third-party code. Review the repository files before installing.
What it does
The server gives the agent Salesforce DX tools for orgs already authorized locally through Salesforce CLI. Tools come in toolsets: orgs, metadata, data, users, testing, code analysis, DevOps, mobile, Aura component analysis and more. The --toolsets and --tools flags pick what is enabled, and --orgs limits which orgs the agent can reach. An experimental mode loads tools on demand to keep context small.
Who it is for. For Salesforce developers and admins who work with Salesforce CLI.
Good fit when
- You want the agent to deploy or retrieve metadata
- You need a SOQL query or data fix in a sandbox
- You need to run Apex tests and analyze results
Not a fit when
- You do not use Salesforce
- You would grant access to every org: the vendor advises caution with ALLOW_ALL_ORGS
Example request
Deploy the project metadata changes to my sandbox and run the Apex testsMCP
- Transport
- stdio
- Authentication
- OAuth
Limitations
Requires a Salesforce account and orgs authorized via Salesforce CLI. Telemetry is on by default; disable it with --no-telemetry. There are over sixty tools, and the vendor advises against enabling all at once. Some tools are not GA and need --allow-non-ga-tools.
How to disable. Remove the Salesforce DX entry from your MCP client config.
FAQ
How do I restrict access to one org?
Pass the org username or alias to --orgs instead of DEFAULT_TARGET_ORG so changing the default org does not widen access.
How do I reduce context load?
Enable only the toolsets you need via --toolsets, or try the experimental --dynamic-tools flag.
Discussion
No questions or reviews yet.
Related
MCP serversMCP server for the amoCRM (Kommo) API v4: leads, contacts, companies, tasks, pipelines, unsorted inbox and analytics
A minimal MCP server for amoCRM API v4: read and create leads, contacts and notes, with OAuth2 and long-term tokens
amoCRM sales manager MCP server
amoCRM ROP MCP Server
An MCP server with business tools on top of amoCRM for a sales manager: department overview, stale deals, manager comparison
Planfix MCP server
Planfix MCP Server
An MCP server for Planfix built on REST API v2.0: leads, tasks, contacts, companies, reports and custom fields via config
Planfix MCP server with prompts and resources
Planfix MCP Server
A Python Planfix MCP server: tasks, projects, contacts and reports, plus ready MCP resources and planning prompts
InSales MCP server
insales-mcp
An MCP server for the InSales online store platform: products, orders, customers and categories via the admin API
README in short
The README shows npx configs for VS Code, Claude Code, Cline and Cursor. It details launch flags, org selection values and a table of toolsets linked to tool lists. Orgs must be authorized beforehand with Salesforce CLI. General docs live in the Salesforce DX Developer Guide. Apache 2.0 licensed.