Salesforce CLI MCP Server
Salesforce org data and metadata management via Model Context Protocol tools.
Data last scanned yesterday · Reviewed 2 months ago
Overview
The Salesforce CLI MCP Server bridges the gap between LLMs and Salesforce environments. By integrating through the Model Context Protocol, it allows AI models to interact directly with Salesforce resources including orgs, metadata, user configurations, and data objects. Users configure the server by adding it to their local MCP JSON files, specifying required toolsets and target orgs.
Our verdict
This server carries a high-risk rating with a security score of 30/100, primarily due to the lack of an authentication method, meaning any user with access to the configuration can execute commands against your org. Additionally, the tool lacks read-only mode constraints, granting full write access by default. It is recommended only for isolated development or testing environments where security exposure is strictly managed.
- Zero direct dependencies reduce potential supply-chain vulnerabilities
- Active development with frequent updates and commits
- Supported by a community of 35 contributors
- Lacks authentication, allowing unauthorized command execution
- Defaults to full write access without read-only restrictions
- Maintained by the community rather than official vendor channels
Setup
{
"mcpServers": {
"salesforcecli-mcp": {
"args": [
"-y",
"monorepo-for-salesforce-mcp-server-and-providers"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| run_apex_test | Runs Apex tests in a Salesforce org. | high |
| create_aura_blueprint_draft | Creates a comprehensive Product Requirements Document (PRD) blueprint for Aura component migration. | medium |
| enhance_aura_blueprint_draft | Enhances an existing draft PRD with expert analysis and unknown resolution. | medium |
| orchestrate_aura_migration | Orchestrates the complete Aura to LWC migration workflow. | low |
| transition_prd_to_lwc | Provides migration bridge guidance for creating LWC components from Aura specifications. | medium |
| create-custom-rule | Creates a custom XPath-based PMD rule from a provided Apex code sample. | medium |
| describe_code_analyzer_rule | Gets the description of a Code Analyzer rule. | low |
| generate_xpath_prompt | Builds the prompt that guides XPath authoring from AST context. | low |
| list_code_analyzer_rules | Selects Code Analyzer rules based on a number of criteria. | low |
| query_code_analyzer_results | Queries a Code Analyzer results JSON file and returns filtered violations. | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›How do I install the Salesforce DX MCP Server?
The server is installed automatically via npx using the @salesforce/mcp package; ensure that you include the -y flag in your configuration to allow automatic installation.
›Can I use tools that are not yet generally available?
Yes, you can enable tools that are not yet generally available by including the --allow-non-ga-tools flag in your server configuration arguments.
›How do I restrict the server to specific toolsets?
You can use the --toolsets flag to specify only the categories you need, such as orgs, metadata, data, or users.
›Where can I find detailed configuration guides for different MCP clients?
The official Salesforce DX Developer Guide includes a section dedicated to server configuration, including quick start guides and examples for various MCP clients.
Alternatives
Changelog
- Fix0.30.15
2026-07-09
- Improved0.30.14
2026-06-23
- Improved0.30.13
2026-05-27
- Fixmcp-provider-metadata-enrichment@0.1.8
2026-05-27
- Improved0.30.12
2026-05-21
- Improved0.30.11
2026-05-21
- Improved0.30.10
2026-05-21
- Newmcp-provider-dx-core@0.10.0
2026-05-21
- Newmcp-provider-code-analyzer@0.9.0
2026-05-21
- Improved0.30.9
2026-05-07
Badge
Maintain this server? Add the live badge to your README.