@salesforce/mcp

What it does

The Salesforce DX MCP Server exposes Salesforce org operations to Claude through a toolset architecture. Tools are organized into categories—orgs, metadata, data, and users—and you enable only the ones your workflow needs via startup flags. Under the hood it leverages Salesforce DX, so it integrates with your existing org authentication. The server is currently in beta.

Who it's for

Salesforce backend engineers and administrators automating routine org tasks through Claude: deploying metadata, querying limits or data, running tests, or managing permissions. Platform teams building AI-assisted Salesforce workflows will find this useful for reducing manual admin overhead.

Common use cases

• Deploy Apex code and custom objects to a target org via Claude prompts
• Query org configuration, user records, or data limits in natural language
• Run Apex unit tests and retrieve results for debugging without leaving the IDE
• Manage user permissions and activation states through conversational requests
• Validate org state and permission models against expected configuration

Setup pitfalls

• Salesforce DX CLI (sf or sfdx) must be installed and authenticated on the host; MCP server cannot reach your org without it
• A default target org is required—set via environment variable or configure via sf org list before startup
• Config syntax differs by MCP client: .mcp.json for Claude Code, cline_mcp_settings.json for Cline, mcp.json for Cursor; double-check your client's docs
• Tools are in beta; breaking changes may ship between releases. Use --allow-non-ga-tools to opt into experimental features